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

package/commands/query.md

@@ -1,9 +1,14 @@
 ---
 name: query
-description: Query the knowledge graph in natural language
-argument-hint: [question]
+description: "[Deprecated] Query the knowledge graph in natural language (use /mos:graph)"
+help_jtbd: "Ask your room any question; get the answer as graph paths (deprecated: use /mos:graph)."
+body_shape: D
+argument-hint: "[question]"
 serves_jtbd: ["audit-room", "explore"]
-teaching: "When you need to ask the knowledge graph something specific, /mos:query translates natural language into the right traversal and returns the answer with its graph path."
+deprecated: true
+deprecated_redirect: "graph"
+deprecated_removal: "v1.14.0"
+teaching: "Deprecated alias. Use /mos:graph to ask natural-language questions of the knowledge graph; query and graph share the same translator. Scheduled removal: v1.14.0."
 allowed-tools:
   - Read
   - Bash
@@ -11,115 +16,32 @@ allowed-tools:
 
 # /mos:query
 
-You are Larry. This command lets users ask natural language questions about relationships between their room artifacts. You translate questions to SQL, execute against the room graph (SQLite), and return formatted insights.
+> Deprecated. /mos:query now redirects to /mos:graph. Scheduled removal: v1.14.0. Use /mos:graph going forward.
 
-## Usage
+You are Larry. The user invoked /mos:query. Per D-09 (LOCKED 2026-05-16, Phase 121.5-08 Sub-plan J) /mos:query is a soft-alias stub for the v1.13.x window. The canonical surface is /mos:graph.
 
-```
-/mos:query <natural language question>
-```
-
-## Examples
-
-- `/mos:query What contradicts my pricing assumption?`
-- `/mos:query Which sections are most connected?`
-- `/mos:query What informs my solution design?`
-- `/mos:query Show all convergent themes across sections`
-- `/mos:query What artifacts are in market-analysis?`
-- `/mos:query Find all cross-section relationships`
-
-## How It Works
-
-1. **Parse the question** -- understand what the user is asking about (relationships, sections, artifacts, contradictions, themes).
-2. **Load the graph schema** -- read `docs/lazygraph-schema.md` for node types, edge types, and SQL patterns.
-3. **Generate SQL** -- translate the natural language question into a SQL query against the nodes/edges tables.
-4. **Execute the query** -- use `lazygraph-ops.cjs` functions:
-   ```javascript
-   const { openGraph, queryGraph, closeGraph } = require('./lib/core/lazygraph-ops.cjs');
-   const { db, conn } = await openGraph('room');
-   const results = await queryGraph(conn, sqlQuery);
-   ```
-5. **Format results** -- present findings as Larry-style insights, not raw data tables. Explain what the relationships mean for the venture.
+## Steps
 
-## Step 1: Check for Room and Graph
+1. Emit the deprecation note above as a single cyan line (Larry voice; no em-dash; one sentence per skills/ui-system/SKILL.md Section 6).
 
-If no `room/` directory exists:
-> "No Data Room yet. Run `/mos:new-project` to get started, then file some artifacts before querying."
+2. Invoke /mos:graph with the user's original arguments (the natural-language question). Run:
 
-STOP.
-
-If the room exists but has no `.mindrian/room.db` file, auto-initialize by running a graph rebuild:
-
-```javascript
-const { openGraph, rebuildGraph } = require('./lib/core/lazygraph-ops.cjs');
-const { db, conn } = await openGraph('room');
-await rebuildGraph(conn, 'room');
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/soft-alias-runner.cjs" --from query --to "graph" --remaining-args $ARGUMENTS
 ```
 
-> "I just built your knowledge graph for the first time. Let me answer your question..."
-
-## Step 2: Generate and Execute SQL
-
-Read `docs/lazygraph-schema.md` for the full schema reference and example query patterns.
-
-**Translation guidelines:**
-- "What contradicts..." -> `SELECT source, target FROM edges WHERE type = 'CONTRADICTS'`
-- "What informs..." -> `SELECT source, target FROM edges WHERE type = 'INFORMS'`
-- "What enables..." -> `SELECT source, target FROM edges WHERE type = 'ENABLES'`
-- "Which sections..." -> `SELECT target, COUNT(*) FROM edges WHERE type = 'BELONGS_TO' GROUP BY target ORDER BY COUNT(*) DESC`
-- "Show connections..." -> `SELECT * FROM edges WHERE source = ? OR target = ?`
-- "How connected is..." -> `SELECT COUNT(*) FROM edges WHERE source = ? OR target = ?`
-
-**SQLite notes:**
-- Use json_extract(properties, '$.field') to access JSON properties on nodes and edges
-- Standard SQL syntax -- no graph-specific extensions needed
-- All node properties stored as JSON in the properties column
-
-## Step 3: Format Results as Insights
-
-Never return raw query output. Always interpret results in Larry's voice.
-
-**For contradictions:**
-> "I found 2 contradictions touching your pricing model. Your market-analysis/competitor-review says premium pricing is sustainable, but your financial-model/unit-economics suggests price sensitivity. Worth reconciling -- these two sections are pulling in different directions."
-
-**For informational queries:**
-> "3 artifacts inform your solution design: your problem-definition/core-problem (the foundation), market-analysis/customer-interviews (real voices), and competitive-analysis/gap-analysis (where you fit). That's a solid chain of reasoning."
-
-**For empty results:**
-> "No results for that query. This could mean the relationship hasn't been captured yet. Try filing more artifacts with [[cross-references]] to build the graph, or rephrase your question."
-
-**For statistics:**
-> "Your knowledge graph has 12 artifacts across 5 sections, with 8 INFORMS edges and 2 CONTRADICTS. The market-analysis section is your most connected -- 4 artifacts referencing other sections."
-
-## Requirements
-
-- Room must have artifacts filed. Run `/mos:room` first to check room status.
-- First query auto-initializes the graph if `.mindrian/room.db` does not exist.
-- Cross-references between sections require `[[wikilinks]]` in artifact content.
-- ENABLES and INVALIDATES edges require explicit frontmatter markers (`enables:` and `invalidates:` fields).
-
-## Graph Schema Reference
-
-See `docs/lazygraph-schema.md` for the complete schema including:
-- All node types and properties
-- All relationship types with directions
-- Example SQL query patterns
-- SQLite query notes
+The runner emits `{redirect, deprecation_note, args, ok}`. Use the redirect to confirm the target, then proceed with /mos:graph behavior. The user sees ONE deprecation note + the graph traversal output.
 
-## Tier 2: Semantic Search (Optional)
+3. Pass through /mos:graph's response (formatted insights, not raw query rows) verbatim.
 
-When Pinecone is configured (`PINECONE_API_KEY` and `PINECONE_INDEX` environment variables set), queries can also leverage semantic similarity search -- finding related artifacts not just by structural links but by meaning.
+## Why this is a soft-alias
 
-This enables questions like:
-- "What else discusses customer acquisition costs?" (semantic match, no wikilink needed)
-- "Find artifacts similar to my pricing model" (embedding similarity)
+Cluster 5 audit (2026-05-15) found that /mos:query and /mos:graph both translated natural language to SQL/Cypher against room.db. Two commands, identical translator, different names. Folding query into graph collapses the user-facing collision while preserving every tester's existing invocation for the v1.13.x window.
 
-Tier 2 is optional. All structural queries work without Pinecone.
+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.
 
-## Voice Rules
+## Cross-references
 
-- Larry's voice throughout. Interpret graph results, don't just dump data.
-- Frame contradictions as opportunities for clarity, not problems.
-- Frame INFORMS chains as reasoning strength.
-- Always suggest a next action: "Want me to dig deeper into that contradiction?" or "Should I check what else informs this section?"
-- If the graph is sparse, encourage more cross-referencing: "Your graph would be richer with more [[wikilinks]] between sections."
+- `commands/graph.md` -- the canonical target with the full graph query translator.
+- `scripts/soft-alias-runner.cjs` -- the shared runner.
+- Canon Part 7 (Reuse Before Build) -- consolidation rationale.

package/commands/radar.md

@@ -1,6 +1,8 @@
 ---
 name: radar
 description: Track Claude capabilities that may help MindrianOS
+help_jtbd: "Get a radar view of where your room is strong + weak."
+body_shape: A
 serves_jtbd: ["understand-market"]
 teaching: "When new Claude capabilities ship that might change what MindrianOS can do, /mos:radar tracks them so you do not have to. Capability awareness as a habit, not a one-time scan."
 allowed-tools:

package/commands/reanalyze.md

@@ -1,6 +1,7 @@
 ---
 name: reanalyze
 description: Re-analyze filed meetings for new patterns
+help_jtbd: "Re-run analysis on a single artifact or section."
 body_shape: E (Action Report)
 body_shape_detail: Before/after delta showing new insights discovered
 serves_jtbd: ["file-meeting"]

package/commands/research.md

@@ -1,6 +1,8 @@
 ---
 name: research
 description: Research the web and cross-reference with Brain
+help_jtbd: "Spawn a research sub-agent for a specific question."
+body_shape: C
 argument-hint: [topic]
 serves_jtbd: ["explore", "understand-market"]
 teaching: "When you need fresh evidence from the web cross-referenced with the Brain methodology graph, /mos:research runs the dual-source pull. Public signal plus calibrated framework."

package/commands/room.md

@@ -1,7 +1,9 @@
 ---
 name: room
 description: View, launch, or navigate the Data Room
+help_jtbd: "Open your current room's view in this terminal."
 argument-hint: [overview|<section>]
+body_shape: C
 body_shape_overview: B (Semantic Tree)
 body_shape_section: C (Room Card)
 serves_jtbd: ["audit-room"]

package/commands/rooms.md

@@ -1,6 +1,7 @@
 ---
 name: rooms
 description: List, switch, or archive project rooms
+help_jtbd: "List, switch, archive, or organize rooms in ~/MindrianRooms/."
 argument-hint: [list|switch|archive|park]
 body_shape: B (Semantic Tree)
 serves_jtbd: ["audit-room"]

package/commands/root-cause.md

@@ -1,6 +1,8 @@
 ---
 name: root-cause
 description: Trace root cause via 5-Whys, Fishbone, Fault Tree
+help_jtbd: "Trace the root cause of a symptom in your venture."
+body_shape: "methodology"
 serves_jtbd: ["find-problem"]
 teaching: "When the symptom keeps coming back, /mos:root-cause traces it via 5-Whys, Fishbone, and Fault Tree. Treats the cause, not the recurrence."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/rs-experts.md

@@ -1,6 +1,7 @@
 ---
 name: rs-experts
 description: Resolve the expert network for a topic via Aura Cypher MATCH
+help_jtbd: "Surface the expert profiles for a reverse salient."
 body_shape: D (Comparison Matrix)
 serves_jtbd: ["find-bottleneck", "connect-domains"]
 teaching: "When you need to know who in the world is working on a reverse salient you found, /mos:rs-experts resolves the expert network via Brain Cypher MATCH. Routes you to the people who already know."

package/commands/rs-explain.md

@@ -1,6 +1,7 @@
 ---
 name: rs-explain
 description: Bidirectional NL-Graph entry point. NL question to graph queries to Larry-voiced explanation.
+help_jtbd: "Explain a reverse salient finding in plain language."
 body_shape: E (Action Report)
 serves_jtbd: ["find-bottleneck"]
 teaching: "When you have a question about a Reverse Salient discovery, /mos:rs-explain takes natural language in and returns a Larry-voiced explanation grounded in the graph. Bidirectional NL to graph and back."

package/commands/rs-fetch.md

@@ -1,6 +1,7 @@
 ---
 name: rs-fetch
 description: Run the full Reverse Salient discovery pipeline for a topic
+help_jtbd: "Fetch the latest reverse salient analysis for your room."
 body_shape: E (Action Report)
 serves_jtbd: ["find-bottleneck", "surface-contradiction"]
 teaching: "When you need the full Reverse Salient pipeline run on a topic, /mos:rs-fetch executes the discovery end-to-end: corpus, math, cross-domain match, thesis. The complete sweep, not a sample."

package/commands/rs-thesis.md

@@ -1,6 +1,7 @@
 ---
 name: rs-thesis
 description: Read the thesis for a prior Reverse Salient discovery
+help_jtbd: "Compose the thesis statement from your reverse salient findings."
 body_shape: E (Action Report)
 serves_jtbd: ["find-bottleneck"]
 teaching: "When you ran a Reverse Salient discovery earlier and want the thesis read back, /mos:rs-thesis surfaces the analytic conclusion in plain language. Best for revisiting old findings before a meeting."

package/commands/scenario-plan.md

@@ -1,6 +1,8 @@
 ---
 name: scenario-plan
 description: Build a 2x2 scenario matrix of plausible futures
+help_jtbd: "Branch into scenarios and compare outcomes."
+body_shape: "methodology"
 serves_jtbd: ["compare-options", "plan-execution"]
 teaching: "When the future could go two different ways on two key uncertainties, /mos:scenario-plan builds the 2x2 matrix and names each quadrant. Forces you to plan for the world you do not expect."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/scheduled-tasks.md

@@ -1,6 +1,7 @@
 ---
 name: scheduled-tasks
 description: Define Cowork scheduled tasks for the room
+help_jtbd: "View and manage scheduled background sweeps."
 body_shape: E (Action Report)
 serves_jtbd: ["plan-execution"]
 teaching: "When you want Cowork to run something on a schedule against this room, /mos:scheduled-tasks defines the recurring job. Best for nightly grant sweeps or weekly meeting digests."

package/commands/score-innovation.md

@@ -1,6 +1,8 @@
 ---
 name: score-innovation
 description: Score cross-domain innovation via HSI
+help_jtbd: "Score the innovation potential of your venture."
+body_shape: "methodology"
 serves_jtbd: ["compare-options", "validate-idea"]
 teaching: "When you are choosing between cross-domain innovation candidates, /mos:score-innovation runs HSI scoring to rank them by semantic surprise. The math reveals which idea is actually novel."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/scout.md

@@ -1,6 +1,7 @@
 ---
 name: scout
 description: Run sentinel scans across the room
+help_jtbd: "Scout the competitive landscape for a specific axis."
 body_shape: E (Action Report)
 serves_jtbd: ["explore", "understand-market"]
 teaching: "When you want background scans running across the room without driving them yourself, /mos:scout fires the sentinel checks. The proactive layer, not the reactive one."

package/commands/setup.md

@@ -1,6 +1,8 @@
 ---
 name: setup
 description: Configure optional integrations (Brain, Velma)
+help_jtbd: "Add optional integrations: graph, Brain, MCP servers."
+body_shape: E
 argument-hint: [brain|velma|graph]
 serves_jtbd: ["explore"]
 teaching: "When you want to wire optional integrations like Brain or Velma, /mos:setup walks you through configuration. MindrianOS works without them; they make it work harder."

package/commands/snapshot.md

@@ -1,6 +1,8 @@
 ---
 name: snapshot
 description: Package a Data Room snapshot for sharing
+help_jtbd: "Capture a snapshot of your room at this moment."
+body_shape: E
 argument-hint: '[<room-path>] [--open]'
 serves_jtbd: ["prepare-pitch", "audit-room"]
 teaching: "When you need a frozen Data Room artifact to share with someone outside the team, /mos:snapshot packages everything into a portable bundle. Read-only by design."

package/commands/speakers.md

@@ -1,6 +1,7 @@
 ---
 name: speakers
 description: Show who spoke in your meetings and their roles
+help_jtbd: "Surface speaker profiles from filed meetings."
 body_shape: C (Room Card)
 body_shape_detail: Each speaker as a card with role, expertise, meeting count
 serves_jtbd: ["file-meeting"]

package/commands/splash.md

@@ -1,7 +1,8 @@
 ---
 name: splash
 description: Display the MindrianOS Mondrian banner
-body_shape: raw
+help_jtbd: "See the MindrianOS welcome panel + version."
+body_shape: E
 serves_jtbd: ["explore"]
 teaching: "When you want the MindrianOS Mondrian banner, /mos:splash displays it. Mostly decorative; useful for screenshots and demo openings."
 allowed-tools:
@@ -14,12 +15,14 @@ Display the MindrianOS De Stijl Mondrian banner + the owned-emotion tagline (D-0
 
 ## What to do
 
-Run the banner script. It auto-reads the version from plugin.json -- no arguments needed:
+Run the banner script. It auto-reads the version from plugin.json -- no arguments needed. The banner now stamps the running version of record at the top per Phase 121.5-05 Sub-plan F (SEED-007 absorption); ensure the response shows the banner output verbatim so the user sees "MindrianOS v<version>" without typing `claude plugin list`:
 
 ```bash
 bash "${CLAUDE_PLUGIN_ROOT}/scripts/banner"
 ```
 
+The first line of the banner output is the canonical version stamp -- format `MindrianOS v<version>`, sourced from `${CLAUDE_PLUGIN_ROOT}/lib/core/first-touch-version-stamper.cjs` (`stampVersion('splash')` returns the long form `MindrianOS v<version> -- conversation as the product surface` if you need to echo the stamp in prose).
+
 After the banner renders, print the owned-emotion tagline on its own line, verbatim (this is `lib/copy/115-spec-strings.cjs` SPLASH_COPY -- do NOT paraphrase per Pitfall 1):
 
 > Stuck on a decision you can't name? Let's find the shape of it.

package/commands/status.md

@@ -1,6 +1,7 @@
 ---
 name: status
 description: Show governing thought per section + health glyphs
+help_jtbd: "See your room's section-by-section status at a glance."
 argument-hint: "[section] [--stale-only]"
 body_shape: E (Action Report)
 serves_jtbd: ["audit-room", "explore"]

package/commands/structure-argument.md

@@ -1,6 +1,8 @@
 ---
 name: structure-argument
 description: Structure an argument with Minto + SCQA + MECE
+help_jtbd: "Build a Minto-Pyramid argument from your room's evidence."
+body_shape: "methodology"
 serves_jtbd: ["validate-idea", "explore"]
 teaching: "When an argument is muddled and you cannot say why, /mos:structure-argument restructures it with Minto pyramid, SCQA, and MECE. The right structure usually surfaces the missing premise."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/suggest-next.md

@@ -1,6 +1,8 @@
 ---
 name: suggest-next
 description: Suggest the next move using the room graph
+help_jtbd: "Get the next move Larry recommends, ranked."
+body_shape: B
 serves_jtbd: ["plan-execution", "explore"]
 teaching: "When you finish a step and want Larry to recommend the next move, /mos:suggest-next reads the room graph and proposes 3-5 options with reasons. The Navigation Engine made visible."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/systems-thinking.md

@@ -1,6 +1,8 @@
 ---
 name: systems-thinking
 description: Map feedback loops, stocks, and flows
+help_jtbd: "Apply systems-thinking lenses to a problem."
+body_shape: "methodology"
 serves_jtbd: ["find-bottleneck"]
 teaching: "When the dynamics matter more than the parts, /mos:systems-thinking maps feedback loops, stocks, and flows. Surfaces where the leverage actually lives in the system."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/think-hats.md

@@ -1,6 +1,8 @@
 ---
 name: think-hats
 description: Rotate through De Bono's Six Thinking Hats
+help_jtbd: "Get a six-thinking-hats pass from the AI team."
+body_shape: "methodology"
 serves_jtbd: ["explore", "compare-options"]
 teaching: "When the team keeps wearing the same hat and missing perspectives, /mos:think-hats rotates them through de Bono's six. The discomfort is the point; that is where the new thought lives."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/update.md

@@ -1,6 +1,8 @@
 ---
 name: update
 description: Check for MindrianOS updates and install via Claude Code's native plugin loader
+help_jtbd: "Update the plugin to the latest version."
+body_shape: E
 argument-hint: [check|reapply|force]
 serves_jtbd: ["audit-room"]
 teaching: "When you suspect MindrianOS has a newer version waiting, /mos:update checks and installs via Claude Code's native plugin loader. Stale plugins quietly diverge from the docs."

package/commands/user-needs.md

@@ -1,6 +1,8 @@
 ---
 name: user-needs
 description: Map user needs with importance vs satisfaction
+help_jtbd: "Map user needs against your value proposition."
+body_shape: "methodology"
 serves_jtbd: ["find-problem"]
 teaching: "When you need to map what users actually want versus what they say they want, /mos:user-needs plots importance against satisfaction. The gap is where the opportunity lives."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/validate.md

@@ -1,6 +1,8 @@
 ---
 name: validate
 description: Validate ideas via importance-satisfaction scoring
+help_jtbd: "Validate a specific claim or hypothesis against evidence."
+body_shape: C
 serves_jtbd: ["validate-idea"]
 teaching: "When an idea needs a real test before more investment, /mos:validate runs importance-satisfaction scoring against the customer segment. Validation is a measurement, not a feeling."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/value-proposition.md

@@ -1,6 +1,8 @@
 ---
 name: validate-proposition
 description: Score your value proposition against 3 VP gates
+help_jtbd: "Compose the value proposition canvas for your room."
+body_shape: "methodology"
 serves_jtbd: ["validate-idea", "prepare-pitch"]
 teaching: "When you have a value proposition but no proof it holds, /mos:validate-proposition scores it against the three PWS VP gates with sequential math. A clean gate failure beats a vague pass."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/vault.md

@@ -1,8 +1,10 @@
 ---
 name: vault
 description: Export the Data Room as an Obsidian vault
+help_jtbd: "Export your room as an Obsidian vault."
 argument-hint: '[<room-name>] [--path <dir>]'
 disable-model-invocation: true
+body_shape: E
 body_shape_overview: E (Mini Report)
 serves_jtbd: ["prepare-pitch"]
 teaching: "When you want the Data Room available in Obsidian for offline reading, /mos:vault exports it as a nested vault with wikilinks intact. Graph view comes free."

package/commands/visualize.md

@@ -1,10 +1,14 @@
 ---
 name: visualize
-description: Open room diagrams in the browser
-argument-hint: [structure|graph|chart]
+description: "[Deprecated] Open room diagrams in the browser (use /mos:dashboard --mermaid)"
+help_jtbd: "Generate visualizations of your room's graph (deprecated: use /mos:dashboard --mermaid)."
+argument-hint: "[structure|graph|chart]"
 body_shape: D (Document View)
 serves_jtbd: ["audit-room", "prepare-pitch"]
-teaching: "When you want to see the room as diagrams in a browser, /mos:visualize opens the visual layer. Best when a stakeholder needs the picture, not the prose."
+deprecated: true
+deprecated_redirect: "dashboard --mermaid"
+deprecated_removal: "v1.14.0"
+teaching: "Deprecated alias. Use /mos:dashboard --mermaid to open the De Stijl knowledge-graph viewer with Mermaid output; visualize folds into the dashboard surface. Scheduled removal: v1.14.0."
 ui_reference: skills/ui-system/SKILL.md
 allowed-tools:
   - Bash
@@ -13,41 +17,32 @@ allowed-tools:
 
 # /mos:visualize
 
-Open rich visual diagrams in the browser. Falls back to Mermaid code blocks in text output.
+> Deprecated. /mos:visualize now redirects to /mos:dashboard --mermaid. Scheduled removal: v1.14.0. Use /mos:dashboard --mermaid going forward.
 
-## Sub-commands
+You are Larry. The user invoked /mos:visualize. Per D-09 + the Phase 121.5-08 planner decision (LOCKED 2026-05-16, Sub-plan J) /mos:visualize is a soft-alias stub for the v1.13.x window. The canonical surface is /mos:dashboard --mermaid.
 
-- `/mos:visualize room` -- Room structure flowchart (sections, stages, cross-references)
-- `/mos:visualize graph` -- Knowledge graph view (LazyGraph nodes and edges)
-- `/mos:visualize chain` -- Latest methodology chain flowchart
-- `/mos:visualize timeline` -- Meeting timeline (Gantt-style)
+## Steps
 
-## Usage
+1. Emit the deprecation note above as a single cyan line (Larry voice; no em-dash; one sentence per skills/ui-system/SKILL.md Section 6).
 
-Larry runs `scripts/render-viz <subcommand>` to generate and open the diagram.
-If browser is unavailable, outputs Mermaid code block that renders in GitHub/Obsidian.
+2. Invoke /mos:dashboard --mermaid with the user's original arguments. Run:
 
-## Examples
+```bash
+node "${CLAUDE_PLUGIN_ROOT}/scripts/soft-alias-runner.cjs" --from visualize --to "dashboard --mermaid" --remaining-args $ARGUMENTS
+```
 
-User: "Show me the room structure as a diagram"
-Larry: Runs `/mos:visualize room` -- opens browser with interactive Mermaid flowchart
+The runner emits `{redirect, deprecation_note, args, ok}`. Use the redirect to confirm the target, then proceed with /mos:dashboard --mermaid behavior. The user sees ONE deprecation note + the dashboard render (browser open OR Mermaid code block fallback).
 
-User: "What does my knowledge graph look like?"
-Larry: Runs `/mos:visualize graph` -- opens browser with force-directed graph view
+3. Pass through dashboard's output verbatim. The dashboard already renders the room as Cytoscape; the --mermaid flag adds the Mermaid code-block fallback that /mos:visualize used to provide.
 
-User: "Show the methodology chain for problem-definition"
-Larry: Runs `/mos:visualize chain` -- opens flowchart of diagnose -> framework -> apply -> file -> cross-ref -> graph-update
+## Why this is a soft-alias
 
-## Output Formats
+Cluster 5 audit (2026-05-15) flagged that /mos:visualize and /mos:dashboard both rendered the room's graph. The dashboard already opens the Cytoscape viewer; visualize's Mermaid output is one render mode of the same underlying graph. Folding visualize into /mos:dashboard --mermaid collapses the surface area while preserving every render mode (room structure, knowledge graph, methodology chain, meeting timeline).
 
-| Surface | Output |
-|---------|--------|
-| CLI | Browser opens with De Stijl themed HTML + Mermaid syntax to stdout |
-| Desktop | Mermaid code block returned (copy-pasteable, renders in Obsidian/GitHub) |
-| Cowork | Mermaid code block in shared context (renders for all participants) |
+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.
 
-## Related
+## Cross-references
 
-- `/mos:room` -- Room state and section listing
-- `/mos:query` -- LazyGraph Cypher queries
-- `scripts/serve-dashboard` -- Full D3.js interactive dashboard
+- `commands/dashboard.md` -- the canonical target with --mermaid as a render flag.
+- `scripts/soft-alias-runner.cjs` -- the shared runner.
+- Canon Part 7 (Reuse Before Build) -- consolidation rationale.

package/commands/whitespace.md

@@ -1,7 +1,8 @@
 ---
 name: whitespace
 description: Detect whitespace gaps in the room's coverage
-body_shape: varies
+help_jtbd: "Map the whitespace zones in your domain."
+body_shape: "methodology"
 serves_jtbd: ["connect-domains", "find-problem"]
 teaching: "When you suspect a gap exists in the room's coverage of a domain, /mos:whitespace runs HSI scoring across the artifact corpus to find under-explored zones. Best after the room has 20+ entries."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/wiki.md

@@ -1,6 +1,7 @@
 ---
 name: wiki
 description: Open the Data Room wiki of room sections
+help_jtbd: "Open your room as a localhost wiki, hyperlinks via graph."
 body_shape: D (Document View)
 serves_jtbd: ["audit-room", "prepare-pitch"]
 teaching: "When you want to read the Data Room as linked wiki pages, /mos:wiki opens the wiki view. Section by section, with cross-references rendered as hyperlinks."