Make /health the single health door (3 modes)

skills/health/health.md

@@ -1,18 +1,33 @@
-# /health — get the organism to green (via the Brain Health Agent)
+# /health — the single door to the organism's health
 
-Route health and readiness through PyAutoBrain's **Health conductor** — the
-organism's clinician. It runs the loop with you: assess (via the read-only vitals
-faculty → Heart) → triage → dispatch a validation leg → re-judge, until Heart
-reports GREEN.
+The **one** health command. The Brain is the door; the procedures live in Heart.
+You type `/health` (or a mode) and it routes — never invoke the sub-tools by name.
 
 Shared routing context: `PyAutoBrain/skills/COMMANDS.md`.
 
+## Modes
+
+| Invocation | What it does | Leg it drives |
+|------------|--------------|---------------|
+| `/health` | The Brain **Health conductor** loop with you: assess (vitals → Heart) → triage → dispatch a validation leg → re-judge, until GREEN. | `bin/pyauto-brain health` |
+| `/health check` | One-shot **green-light sweep**: sync each repo's `main`, run library pytest + workspace smoke, report a pass/fail matrix. | `PyAutoHeart/skills/health_sweep/reference.md` |
+| `/health status` | **Active-work dashboard**: what's in flight across the repos (reads `active.md` / `planned.md` / `complete.md`), conflicts, idle repos. | `PyAutoHeart/skills/pyauto-status/reference.md` |
+
 ## Do
 
-- Run `bin/pyauto-brain health` and drive the loop conversationally with the user.
-- Use the faster sweeps as **legs** of the loop, not replacements: `/health_check`
-  (quick green-light sweep) and `/pyauto-status` (dashboard read).
-- Adopt Heart's verdict **verbatim** via the vitals faculty; never re-derive it.
+- **Bare `/health`** → run `bin/pyauto-brain health` and drive the loop
+  conversationally. Adopt Heart's verdict **verbatim** via the vitals faculty;
+  never re-derive it.
+- **`/health check`** → follow the sweep procedure in
+  `PyAutoHeart/skills/health_sweep/reference.md` (read-mostly test/smoke sweep;
+  supports `--no-sync`).
+- **`/health status`** → follow the dashboard procedure in
+  `PyAutoHeart/skills/pyauto-status/reference.md`.
+
+`/health` is the **only** health command. The former `/health_check` and
+`/pyauto-status` are retired as top-level commands and live on as the `check` and
+`status` legs above — the door is the Brain, the procedures are Heart's.
 
-This is the human front door for "let's get the organism healthy"; the individual
-sweeps sit beneath it.
+Not folded in: `/pyauto-status-full` (the release-run report — a separate axis;
+flagged for a later pass) and the shell `pyauto-status` function (unrelated
+cross-repo sync tooling).

skills/start_dev/reference.md

@@ -53,7 +53,7 @@ are created.
 A "conflict" means another `active.md` entry already claims one of the target
 repos via its `worktree:` field. Tasks editing different repos run in parallel;
 two tasks wanting the same repo must serialise. After a blocking task ships,
-`/pyauto-status` shows the queued task as ready, then `/start_library` or
+`/health status` shows the queued task as ready, then `/start_library` or
 `/start_workspace` begins it.
 
 Legacy check: if a target repo's **main checkout** is on a feature branch not