@mindrian_os/install 1.13.0-beta.17 → 1.13.0-beta.21

package/commands/diagnostics.md

@@ -1,9 +1,12 @@
 ---
 name: diagnostics
-description: Run Wave-1 algorithmic fingerprint on the room
+description: "[Renaming to /mos:fingerprint v1.14.0] Run Wave-1 algorithmic fingerprint on the room"
+help_jtbd: "Run the 4 Wave-1 algorithms (Disruption Index, Blindspot, Novelty, Surprise). Renaming to /mos:fingerprint in v1.14.0."
 body_shape: E
 serves_jtbd: ["audit-room"]
-teaching: "When you need a quantitative read on the room, /mos:diagnostics runs the Wave-1 fingerprint: disruption, blindspot, novelty, surprise. Surfaces algorithmic signals humans miss."
+renaming_to: fingerprint
+renaming_target_version: "v1.14.0"
+teaching: "When you need a quantitative read on the room, /mos:diagnostics runs the Wave-1 fingerprint: disruption, blindspot, novelty, surprise. Renaming to /mos:fingerprint in v1.14.0 (functional behavior unchanged)."
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["HSI Semantic Surprise Analysis Assistant"]
@@ -18,7 +21,15 @@ allowed-tools:
 
 # /mos:diagnostics
 
-You are Larry. This command runs four Wave-1 algorithms against the active room's embedded artifact corpus and renders a one-screen scalar dashboard: disruption (Funk and Owen-Smith CD), coverage (Good-Turing blindspot mass), element novelty (centroid distance), and Bayesian surprise (leave-one-out cosine shift). Body shape is **Shape E (Action Report) always** -- four metric rows, one intelligence strip, one action footer.
+> Renamed. /mos:diagnostics is being renamed to /mos:fingerprint in v1.14.0 to kill the diagnose/diagnostics naming ambiguity. Both invocations work in v1.13.x; use /mos:fingerprint going forward.
+
+You are Larry. The user invoked /mos:diagnostics. Per Phase 121.5-08 Sub-plan J (LOCKED 2026-05-16) /mos:diagnostics is being RENAMED to /mos:fingerprint in v1.14.0. The functional behavior is unchanged from v1.13.0-beta.x: the 4 Wave-1 algorithms continue to run via scripts/diagnostics-command.cjs. Only the name is migrating; a future v1.14.0 plan will create commands/fingerprint.md and turn this file into a soft-alias stub matching the heal/query/organize pattern.
+
+Emit the rename note above to the user as a single cyan line (Larry voice; no em-dash; one sentence per skills/ui-system/SKILL.md Section 6) BEFORE running the diagnostics behavior below.
+
+## The diagnostics behavior (unchanged from v1.13.0-beta.x)
+
+This command runs four Wave-1 algorithms against the active room's embedded artifact corpus and renders a one-screen scalar dashboard: disruption (Funk and Owen-Smith CD), coverage (Good-Turing blindspot mass), element novelty (centroid distance), and Bayesian surprise (leave-one-out cosine shift). Body shape is **Shape E (Action Report) always** -- four metric rows, one intelligence strip, one action footer.
 
 ## When to run
 

package/commands/doctor.md

@@ -1,7 +1,8 @@
 ---
 name: doctor
-description: Diagnose and optionally repair MindrianOS install — detects install-cache drift, .room-root sentinel gaps, active-room guard silence, surface-verification gaps, ROOM.md/MINTO.md drift, UI Ruling System compliance, and statusline visibility drift
-argument-hint: "[--fix] [--cascade-rooms] [--verify-surface] [--room-md] [--ui-compliance] [--statusline-visibility] [--install-state] [--all] [--acceptance] [--pre-tag] [--light-npx] [--json]"
+description: Diagnose and optionally repair MindrianOS install — detects install-cache drift, .room-root sentinel gaps, active-room guard silence, surface-verification gaps, ROOM.md/MINTO.md drift, UI Ruling System compliance, statusline visibility drift, and Brain end-to-end smoke
+help_jtbd: "Diagnose and optionally repair an off-feeling install."
+argument-hint: "[--fix] [--cascade-rooms] [--verify-surface] [--room-md] [--ui-compliance] [--statusline-visibility] [--install-state] [--stale-first-touch] [--deprecated-usage] [--brain-smoke] [--all] [--acceptance] [--pre-tag] [--light-npx] [--json]"
 body_shape: E (Action Report)
 body_shape_detail: per-class status rows with [before → after] pattern, summary totals, F.1 Next Move selector when drift detected without --fix
 serves_jtbd: ["audit-room"]
@@ -42,6 +43,9 @@ Look at the user's invocation:
 - `/mos:doctor --room-md` → class E (ROOM.md/MINTO.md presence under .room-root subtrees)
 - `/mos:doctor --ui-compliance` → class F (UI Ruling System scan across commands/*.md and scripts/*.cjs)
 - `/mos:doctor --statusline-visibility` → class G — checks user-settings drift, plugin install integrity, and statusline-mos isolated execution
+- `/mos:doctor --stale-first-touch` → class K (Phase 121.5-05; SEED-007 absorption) — scans `data/first-touch-surfaces.json`-declared greeting surfaces (banner, splash, onboard, sessionstart, operator-update, larry-extended) for stale version literals (older than the running plugin) and U+2014 em-dash violations on surfaces flagged `em_dash_check: true`
+- `/mos:doctor --deprecated-usage` → class L (Phase 121.5-08 Sub-plan J) — scans last-7-days `~/.claude/projects/.../*.jsonl` session transcripts for `/mos:<deprecated>` patterns (heal/query/organize/hmi-status/visualize/diagnostics) and surfaces a per-command "use `/mos:<new>` instead" hint. Pure LOCAL scan; zero network, zero Brain. Also activated by `--all`.
+- `/mos:doctor --brain-smoke` → class M (Phase 127-02 BRAIN-MCP-127-08): 5-layer Brain end-to-end probe (plugin root resolver, key resolver, HTTPS schema, MCP stdio handshake, e2e brain_schema via the bundled shim). Diagnostic-only; reports the exact failing layer with fail-fast cascade. Detects 12 Phase 126 failure-mode rows in one composable test (the doctor's single Brain smoke).
 - `/mos:doctor --fix` → diagnostic + auto-recovery for any class that supports --fix (class A, B, E, G)
 - `/mos:doctor --json` → machine-readable output (for hooks / regression tests)
 

package/commands/dogfood-flush.md

@@ -0,0 +1,92 @@
+---
+description: Drain the dog-food queue into the mindrian room and regenerate ## Live (auto)
+help_jtbd: "Manually flush captured plugin edits into the mindrian dataroom."
+body_shape: E
+argument-hint: ""
+serves_jtbd: ["audit-room"]
+teaching: "When you want the plugin's own venture room to reflect your latest edits immediately, /mos:dogfood-flush drains the PostToolUse queue and regenerates the Live (auto) section in STATE.md. The automatic SessionStart drain handles the steady-state case."
+disable-model-invocation: false
+allowed-tools: Bash(node *)
+kind: utility
+frameworks: []
+produces: "~/MindrianRooms/mindrian/STATE.md"
+inputs: []
+autonomous_safe: true
+---
+
+# /mos:dogfood-flush
+
+Force-drain the dog-food queue (`~/.mindrian/dogfood-queue.jsonl`) into
+`~/MindrianRooms/mindrian/room.db` via the Phase 109 navigation chokepoint,
+then regenerate the `## Live (auto)` sentinel-bounded section in
+`~/MindrianRooms/mindrian/STATE.md` atomically with the human-authored body
+byte-preserved.
+
+This is the manual knob the user reaches for when the automatic SessionStart
+drain has not run recently -- explicit redraw, drain everything pending right now.
+
+## Behavior
+
+Two-step pipeline:
+
+1. `scripts/dogfood-emit.cjs` -- drain the queue file, batch-emit `file_changed`
+   memory_event rows via `lib/core/navigation.cjs::logMemoryEvent`. Truncate
+   the queue on success (atomic .tmp + rename).
+2. `scripts/dogfood-derive.cjs` -- read the last 10 file_changed events,
+   regenerate the `<!-- LIVE_AUTO_START -->` / `<!-- LIVE_AUTO_END -->` block
+   in STATE.md. Log a `feynman_timeline_refreshed` memory_event on success.
+
+## Output
+
+F.0 Action Report:
+
+- **emitted:** N events flushed from the queue.
+- **derived:** STATE.md `## Live (auto)` regenerated at `<iso-timestamp>`.
+- **skipped:** if the target room is missing, both phases soft-warn and exit 0
+  without crashing the parent.
+
+## Invariants
+
+- **Canon Part 8 (Graph Boundary):** zero Brain egress. The grep sweep in
+  `tests/test-dogfood-emit-derive.cjs` is the structural enforcement.
+- **Canon Part 9 (Memory Locality):** every memory_event write goes through
+  `navigation.cjs`. The Phase 109-06 pre-commit hook is the structural
+  enforcement (any direct `require('lib/core/room-db.cjs')` from
+  `dogfood-emit.cjs` / `dogfood-derive.cjs` would fail the hook).
+- **Byte-preservation (Phase 124-02 invariant, reused):** everything in
+  STATE.md outside the sentinel pair has its SHA256 preserved across
+  regeneration (Case A). The integration test
+  (`tests/test-dogfood-emit-derive.cjs`) asserts this.
+
+## Implementation
+
+```bash
+node ${CLAUDE_PLUGIN_ROOT}/scripts/dogfood-emit.cjs
+node ${CLAUDE_PLUGIN_ROOT}/scripts/dogfood-derive.cjs
+```
+
+## Examples
+
+```
+/mos:dogfood-flush
+```
+
+## Exit codes
+
+| Exit | Meaning |
+| --- | --- |
+| 0 | Success (including soft-fail paths: room.db missing, empty queue, no STATE.md) |
+
+## Cross-surface adaptation
+
+- **CLI:** full power. Slash command resolves via Claude Code's plugin hook
+  substrate and runs the two scripts through the Bash tool. F.0 report
+  renders in the terminal.
+- **Desktop:** the same slash command runs when the plugin is connected.
+  Larry may narrate the result conversationally; the underlying scripts
+  are identical.
+- **Cowork:** same as CLI. Team members see the regenerated STATE.md
+  `## Live (auto)` block through the shared `~/MindrianRooms/mindrian/`
+  snapshot on their next session-start.
+
+No surface-specific code exists anywhere in either script.

package/commands/dominant-designs.md

@@ -1,6 +1,8 @@
 ---
 name: dominant-designs
 description: Spot dominant designs with Utterback-Abernathy
+help_jtbd: "Identify the dominant designs in your market."
+body_shape: "methodology"
 serves_jtbd: ["understand-market"]
 teaching: "When you are wondering if the market has settled on a winning design, /mos:dominant-designs runs Utterback-Abernathy to spot it. Tells you whether to ride the wave or break it."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/explain-decision.md

@@ -1,5 +1,7 @@
 ---
 description: Show Navigation Engine decision trace for last turn
+help_jtbd: "See why Larry recommended what he recommended."
+body_shape: F.1
 argument-hint: "[--last N] [--session SESSIONID]"
 serves_jtbd: ["audit-room"]
 teaching: "When Larry made a recommendation and you want to know why, /mos:explain-decision shows the Navigation Engine trace for the last turn. Every recommendation has a graph path behind it."

package/commands/explore-domains.md

@@ -1,6 +1,8 @@
 ---
 name: explore-domains
 description: Map domains through IKA + Feynman decomposition
+help_jtbd: "Get the 5-lens decomposition of your problem domain."
+body_shape: "methodology"
 serves_jtbd: ["find-problem", "understand-market", "explore"]
 teaching: "When the problem could live in any of several domains, /mos:explore-domains maps the territory through IKA and Feynman decomposition. Surfaces where to look before you commit."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/explore-futures.md

@@ -1,6 +1,8 @@
 ---
 name: explore-futures
 description: Synthesize TTA + Scenario + S-Curve futures
+help_jtbd: "Branch into future scenarios from where you stand today."
+body_shape: "methodology"
 serves_jtbd: ["compare-options", "explore"]
 teaching: "When the path forward branches into multiple plausible futures, /mos:explore-futures synthesizes TTA, Scenario, and S-Curve views. Helps you choose without pretending you can predict."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/explore-trends.md

@@ -1,6 +1,8 @@
 ---
 name: explore-trends
 description: Push trends to extremes to surface future problems
+help_jtbd: "Surface the macro trends your venture is riding."
+body_shape: "methodology"
 serves_jtbd: ["understand-market", "explore"]
 teaching: "When today's trends could become tomorrow's problems, /mos:explore-trends pushes them to extremes to surface the second-order effects. The future shows up at the edges first."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/export.md

@@ -1,6 +1,7 @@
 ---
 name: export
 description: Export a Data Room view to De Stijl HTML
+help_jtbd: "Ship investor-ready PDF or Obsidian vault of your room."
 argument-hint: [hub|thesis|summary|report]
 disable-model-invocation: true
 body_shape: E (Action Report)

package/commands/feynman-timeline-refresh.md

@@ -1,5 +1,7 @@
 ---
 description: Refresh FEYNMAN.md ## Timeline (auto) section for one or all room sections
+help_jtbd: "Refresh the human-readable Timeline section in FEYNMAN.md."
+body_shape: E
 argument-hint: "[--all | --section <slug>]"
 serves_jtbd: ["validate-idea", "audit-room"]
 teaching: "When a section's FEYNMAN.md timeline feels stale, /mos:feynman-timeline-refresh rebuilds the auto-section from the memory event log. Human-authored prose stays byte-preserved."

package/commands/file-meeting.md

@@ -1,6 +1,8 @@
 ---
 name: file-meeting
 description: File a meeting transcript into the Data Room
+help_jtbd: "Turn a meeting recording into structured room intelligence."
+body_shape: E
 argument-hint: [--latest|--paste|<file>]
 serves_jtbd: ["file-meeting"]
 teaching: "When a meeting just happened, /mos:file-meeting captures the transcript and routes the intelligence into the right room sections. Meetings are where institutional knowledge actually lives."

package/commands/find-analogies.md

@@ -1,6 +1,7 @@
 ---
 name: find-analogies
 description: Find cross-domain analogies with SAPPhIRE + TRIZ
+help_jtbd: "Find cross-domain analogies from 1,427 methodology embeddings."
 body_shape: D (Comparison Matrix)
 serves_jtbd: ["connect-domains"]
 teaching: "When the answer might live in another field, /mos:find-analogies runs SAPPhIRE and TRIZ against your problem to surface cross-domain matches. Most breakthroughs are borrowed structure."

package/commands/find-bottlenecks.md

@@ -1,6 +1,8 @@
 ---
 name: find-bottlenecks
 description: Find lagging components via Reverse Salient
+help_jtbd: "Find the lagging component blocking your venture (Hughes reverse salient)."
+body_shape: "methodology"
 serves_jtbd: ["find-bottleneck"]
 teaching: "When progress feels stuck and you cannot say where, /mos:find-bottlenecks runs Reverse Salient analysis to name the lagging component. Hughes 1983, but for your venture."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/find-connections.md

@@ -1,6 +1,8 @@
 ---
 name: find-connections
 description: Find cross-domain patterns that touch your work
+help_jtbd: "Surface non-obvious connections in your room's graph."
+body_shape: "methodology"
 serves_jtbd: ["connect-domains"]
 teaching: "When you suspect your work touches a pattern in another field, /mos:find-connections traces cross-domain links through the graph. Surfaces the connections you did not know to look for."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/funding.md

@@ -1,6 +1,7 @@
 ---
 name: funding
 description: Track grant opportunities through their lifecycle
+help_jtbd: "See the grants and funding paths matching your room."
 argument-hint: [list|add|update]
 body_shape: B (Semantic Tree)
 serves_jtbd: ["prepare-pitch", "decide-pursue"]

package/commands/grade.md

@@ -1,6 +1,8 @@
 ---
 name: grade
 description: Grade problem-discovery quality (6 components)
+help_jtbd: "Get a fast grade on your room with feedback."
+body_shape: C
 serves_jtbd: ["audit-room"]
 teaching: "When you want a fast read on problem-discovery quality, /mos:grade scores the room on six components in under a minute. The lightweight cousin of /mos:deep-grade."
 # Per docs/reward-before-investment-rule.md line 64-66: show anonymized calibration distribution before requiring content. Remediation tracked as follow-up phase.

package/commands/graph.md

@@ -1,6 +1,7 @@
 ---
 name: graph
 description: Explore the knowledge graph by asking questions
+help_jtbd: "Ask your room a question; get the answer as graph paths."
 body_shape: C (Room Card)
 body_shape_detail: Query results as cards, graph stats as header
 serves_jtbd: ["audit-room", "explore"]

package/commands/hat-briefing.md

@@ -1,6 +1,7 @@
 ---
 name: hat-briefing
 description: Consolidate Six Hats briefings from hat memory
+help_jtbd: "Get a per-hat briefing from the AI team on your venture."
 body_shape: C (Dashboard Grid)
 body_shape_detail: 6-panel hat grid + synthesis strip
 serves_jtbd: ["prepare-pitch"]

package/commands/heal.md

@@ -1,11 +1,14 @@
 ---
 name: heal
-description: Heal a room's structural drift after plugin upgrade
+description: "[Deprecated] Heal a room's structural drift (use /mos:doctor --heal-room)"
+help_jtbd: "Repair drift in your room's structure (deprecated: use /mos:doctor --heal-room)."
 argument-hint: "[room-dir]"
 body_shape: E (Action Report)
-body_shape_detail: 10-step heal table mirrors recipe provenance section
 serves_jtbd: ["audit-room"]
-teaching: "When a plugin upgrade leaves the room with structural drift, /mos:heal repairs the missing ROOM.md, broken backlinks, and stale section state. Use after every major version bump."
+deprecated: true
+deprecated_redirect: "doctor --heal-room"
+deprecated_removal: "v1.14.0"
+teaching: "Deprecated alias. Use /mos:doctor --heal-room to repair structural drift; the canonical heal logic lives in doctor class E. Scheduled removal: v1.14.0."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Bash
@@ -13,185 +16,34 @@ allowed-tools:
   - Write
 ---
 
-# /mos:heal [room-dir]
+# /mos:heal
 
-You are Larry. This command repairs structural drift in a room after a plugin upgrade. It wraps the v1.11.0 room-wiring heal recipe (10 idempotent steps) and produces a typed `heal-log.json` envelope per Canon Part 4 (every choice is graph data).
+> Deprecated. /mos:heal now redirects to /mos:doctor --heal-room. Scheduled removal: v1.14.0. Use /mos:doctor --heal-room going forward.
 
-The recipe was dog-fooded on the mindrianOS room itself on 2026-04-29. Source-of-truth: `~/MindrianRooms/mindrianOS/methodology/2026-04-29-v1-11-0-room-wiring-heal-process.md`.
+You are Larry. The user invoked /mos:heal. Per D-09 (LOCKED 2026-05-16, Phase 121.5-08 Sub-plan J) /mos:heal is a soft-alias stub for the v1.13.x window. The canonical surface is /mos:doctor --heal-room.
 
-## When to invoke
+## Steps
 
-- After upgrading the plugin across a major version (v1.10.x to v1.11.x)
-- When `/mos:status` surfaces `EMPTY -- GAP` on canonical sections that should have ROOMs
-- When the on-stop invariant report shows `severity: error` violations
-- When `minto-stale.json` shows `artifacts_newer_than_minto` for many sections
-- Before generating a power demo, vault export, or first-contact viewer artifact
+1. Emit the deprecation note above to the user as a single cyan line (Larry voice; no em-dash; one sentence per skills/ui-system/SKILL.md Section 6).
 
-## Canon traceability
-
-- **Part 7 (Reuse Before Build):** wraps existing `scripts/migrate-lazygraph.cjs` + `scripts/vault-section-state-generator.cjs` + `scripts/vault-section-minto-generator.cjs` + `scripts/compute-state`. Zero net-new methodology.
-- **Part 4 (Every Choice Is Graph Data):** writes `<room>/.mindrian/heal-log.json` capturing every section touched + every transition + every result.
-- **Part 8 (Graph Boundary):** heal is LOCAL-only. Reads STATE.md / ROOM.md / MINTO.md, runs local graph rebuild, writes local heal-log. Zero Brain queries; brain-derivation-queue is read-only in v1.11.1 (drain deferred to v1.12).
-
-## Step 1: Resolve target room
-
-If the user passed an argument, treat it as the absolute or relative room directory. Otherwise heal the current working directory.
-
-```bash
-ROOM_DIR="${1:-$PWD}"
-```
-
-If `ROOM_DIR` does not exist on disk, render the 3-line error pattern from `skills/ui-system/SKILL.md` Section 7 and stop.
-
-## Step 2: Run the orchestrator
-
-Invoke the 10-step heal orchestrator. The orchestrator is pure CJS and never throws on per-step failure (every step logs a status; mega-section MINTO writes that exceed FEYNMINTO-01 budget gracefully degrade with `status='blocked_feynminto_01'`).
+2. Invoke /mos:doctor --heal-room with the user's original arguments. The doctor command's class E fix engine handles all heal-room logic verbatim. Run:
 
 ```bash
-node "${CLAUDE_PLUGIN_ROOT}/scripts/heal-command.cjs" "$ROOM_DIR"
-```
-
-Optional flags the orchestrator supports:
-
-- `--dry-run` plan only, zero mutation. Useful for previewing what heal would touch.
-- `--skip-step <N>` skip step N (1-10) on a re-run.
-- `--section <name>` restrict step 7 (MINTO regeneration) to one section.
-
-## Step 3: Read the heal-log envelope
-
-After the orchestrator returns, read `<room>/.mindrian/heal-log.json`. The envelope schema:
-
-```json
-{
-  "schema_version": "1.0",
-  "started_at": "ISO-8601",
-  "ended_at": "ISO-8601",
-  "room_dir": "/abs/path",
-  "backup_dir": ".heal-backup/<TS>",
-  "steps": [
-    { "step": "step_01_backup", "status": "ok", "duration_ms": 27, "details": { ... } },
-    ...
-  ],
-  "summary": {
-    "ok_count": 0,
-    "skipped_count": 0,
-    "blocked_count": 0,
-    "error_count": 0,
-    "exit_code": 0
-  }
-}
-```
-
-## Step 4: Render 4-zone output
-
-Follow `skills/ui-system/SKILL.md` Section 1 strictly. No reordering. No invention.
-
-### Zone 1 -- Header Panel
-
-```
--- {room name} -- heal -- {venture stage from STATE.md frontmatter} --
+node "${CLAUDE_PLUGIN_ROOT}/scripts/soft-alias-runner.cjs" --from heal --to "doctor --heal-room" --remaining-args $ARGUMENTS
 ```
 
-If no STATE.md frontmatter exists yet (heal just bootstrapped the room), use `Pre-Opportunity` as the stage. If `room name` cannot be resolved, fall back to the basename of `$ROOM_DIR`.
-
-### Zone 2 -- Content Body (Shape E: Action Report)
-
-Mirror the recipe's "What this heal touched" provenance table. One row per orchestrator step, with status glyph + per-step details.
-
-```
-[heal] action: 10-step room wiring heal
-[heal] source: scripts/heal-command.cjs (recipe 2026-04-29)
-[heal] backup: .heal-backup/<TS>/
-
-  step                              status        ms     detail
-  step_01_backup                    [check]       27ms   N files copied to .heal-backup/<TS>/
-  step_02_scaffold_sections         [check]       1ms    M sections created, K already present
-  step_03_section_seed              [check]       4ms    P sections seeded
-  step_04_lazygraph_rebuild         [check]       226ms  room.db: A artifacts, B sections, C nodes, D edges
-  step_05_backfill_room_md          [check]       3ms    Q sections backfilled, R already present
-  step_06_section_state             [check]       82ms   S sections with STATE.md
-  step_07_section_minto             [warn]        528ms  T sections OK, U blocked_feynminto_01 (mega)
-  step_08_queue_check               [check]       0ms    queue depth V, oldest enqueued YYYY-MM-DD
-  step_09_root_state                [check]       1020ms STATE.md regenerated, W bytes
-  step_10_invariant_scan            [dot]         0ms    no_report_yet (writes on next /mos:* call)
-
-summary: ok=N blocked=M skipped=K error=0 exit_code=0
-```
+The runner emits a JSON envelope: `{redirect, deprecation_note, args, ok}`. Use it to confirm the redirect target then proceed with /mos:doctor --heal-room behavior. The user sees ONE deprecation note + the doctor heal output.
 
-Glyph mapping (per `skills/ui-system/SKILL.md` Section 3):
+3. Pass through any output from /mos:doctor verbatim.
 
-- `status='ok'` or `status='ok_with_blocked'` -> `[check]` (green)
-- `status='skipped'` -> `[dot]` (gray)
-- `status` startswith `'blocked_'` -> `[warn]` (yellow)
-- `status` startswith `'error_'` -> `[x]` (red)
+## Why this is a soft-alias
 
-The status column is a single ASCII glyph; the detail column is a one-line summary extracted from `step.details`.
-
-### Zone 3 -- Intelligence Strip (conditional)
-
-Only render this zone when at least one of the following is true. Maximum 3 lines. Each indented 2 spaces.
-
-- Any step has `status` starting with `'blocked_feynminto_01'`
-  -> `[warn] section <name> exceeded FEYNMINTO-01 budget; tier-0 fallback written`
-- Any step has `status` starting with `'error_'`
-  -> `[x] step <name> errored: <reason>`
-- `step_08_queue_check.details.queue_depth > 0`
-  -> `[empty-square] brain-derivation queue holds N entries (oldest M days); drain deferred to v1.12`
-
-If none of these conditions fire, omit Zone 3 entirely.
-
-### Zone 4 -- Action Footer (NEVER omit)
-
-Three grounded next-commands. Primary marker `>` on the most relevant line, alternatives marked `>` as well per `skills/ui-system/SKILL.md` Section 1.
-
-```
-> /mos:status                review the regenerated STATE.md and per-section state
-> /mos:dashboard             open the De Stijl knowledge-graph viewer over the rebuilt room.db
-> /mos:scout                 run the next overnight intelligence sweep on the healed room
-```
-
-If any step status is `blocked_feynminto_01`, replace the third row with:
-
-```
-> /mos:open <section>/MINTO.md   review the tier-0 fallback MINTO; v1.12 will fix the budget
-```
-
-## What /mos:heal does NOT do (v1.11.1)
-
-These items are explicitly deferred to v1.12. Do not surprise the user; surface them when relevant.
-
-- **FEYNMINTO-01 budget scaling for mega-sections (BUG-1).** When a section has 40+ artifacts, the rendered source list alone consumes most of the 1500-token budget. v1.11.1 graceful-degrades with tier-0 fallback. v1.12 plan candidate: relax budget OR introduce sub-section hierarchy OR archive-folder pattern. Re-trigger condition: any monitored room with a 40+ artifact section reports inability to regenerate MINTO.
-- **brain-derivation-queue auto-drain hook (BUG-2).** The queue is read-only in heal Step 8 (reports depth + age of oldest entry). Drain hook deferred to v1.12. Re-trigger condition: next session-start hook OR /mos:* command-completion hook is being modified for unrelated reasons; bundle the drain hook in.
-- **Section auto-creation on plugin upgrade (BUG-5, recipe Open Issue 3).** When the plugin adds a new canonical section across versions, existing rooms do not auto-scaffold the new section directory on first /mos:* invocation. Heal Step 2 covers this for users running heal post-upgrade; the auto-scaffold-on-upgrade behavior remains unimplemented. Re-trigger condition: next plugin version adds a canonical section.
-
-## Voice rules
-
-- Terse, structural, confident. Per `skills/ui-system/SKILL.md` Section 6.
-- Never apologize for blocked sections; surface them as a warn glyph in Zone 3 with the v1.12 candidate named.
-- One insight per line. Never combine warning + queue depth into a single sentence.
-- NO EMOJI. Use only the 12 glyphs from the symbol vocabulary.
-- Never re-run heal automatically. The user always confirms before any second invocation.
-
-## Error handling
-
-If the orchestrator exits with code 2 (no-step-success), render the 3-line error pattern:
-
-```
-x heal completed with zero successful steps
-  Why: every step errored; check .mindrian/heal-log.json for per-step reasons
-  Fix: /mos:open .mindrian/heal-log.json
-```
-
-If the orchestrator crashes (uncaught exception, exit code != 0 and != 2), render:
-
-```
-x heal-command crashed
-  Why: <error message tail from stderr>
-  Fix: node scripts/heal-command.cjs <room-dir> --dry-run
-```
+Cluster 5 audit (2026-05-15) found four diagnostic commands with overlapping semantics: heal vs doctor, query vs graph, organize vs rooms, visualize vs dashboard. /mos:heal's behavior (10-step room wiring heal) is structurally identical to what /mos:doctor's class E does on a room subtree. Folding heal into doctor --heal-room collapses the naming-drift surface without breaking tester muscle memory.
 
-The dry-run path is the safest path to surface what heal would attempt without mutating any room state.
+Per D-09 the old command stays as a soft-alias stub for v1.13.x; removal is scheduled v1.14.0. CHANGELOG announces the rename.
 
-## Provenance
+## Cross-references
 
-This command was authored as the v1.11.1 GA closing artifact (Phase 94.1-01). The 10-step recipe was dog-fooded on the mindrianOS room itself during the 2026-04-29 wiring audit. Source: `~/MindrianRooms/mindrianOS/methodology/2026-04-29-v1-11-0-room-wiring-heal-process.md`. The orchestrator (`scripts/heal-command.cjs`) and the fixture suite (`lib/memory/heal-command.test.cjs`) ship under BSL 1.1.
+- `commands/doctor.md` -- the canonical target with the full heal logic.
+- `scripts/soft-alias-runner.cjs` -- the shared runner the 5 soft-alias stubs share.
+- Canon Part 7 (Reuse Before Build) -- consolidation rationale.