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

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "mos",
   "description": "MindrianOS -- Your AI innovation co-founder. Larry thinks with you through PWS methodology, builds your Data Room as you explore, and chains frameworks intelligently. Install and go.",
-  "version": "1.13.0-beta.16",
+  "version": "1.13.0-beta.19",
   "author": {
     "name": "Jonathan Sagir",
     "url": "https://mindrian.ai"

package/CHANGELOG.md

@@ -1,3 +1,39 @@
+## [1.13.0-beta.19] - 2026-05-19
+
+### Promoted (2026-05-19 -- v1.13.0 milestone redefinition)
+- **Phase 127 (Brain MCP Local Stdio Shim + Auto-Migration) and Phase 127.1 (Brain GraphRAG Collapse Pinecone -> Neo4j HNSW) PROMOTED from v1.13.1 INTO v1.13.0.** v1.13.0 milestone redefined from "The Closed Loop" (Hooked Fixes + Canon Part 10) to **"The Closed Loop + Brain Goes Native"**. Phase 127 targets v1.13.0-beta.20 (client-side stdio shim, ~3-5 days; Tavily-validated 2026-05-19); Phase 127.1 targets v1.13.0-beta.21 (server-side Neo4j HNSW collapse, ~3-5 days + 20-query non-regression harness >= 80% top-5 overlap). v1.13.0 final cuts after both land. Trade-off: ~2-week ship-date slip, but ONE adoption cycle for "Brain feels native end-to-end" instead of two. v1.13.1 milestone keeps Phases 128/129/130/131 but loses its architectural anchor (renaming pending: "spine repair + lens engine + research workflow", not "Brain native"). External validation in flight via Tavily research agent before /gsd:plan-phase 127 fires. See ROADMAP.md Phase 127 + 127.1 sections, both CONTEXT.md files (frontmatter `milestone:` flipped 2026-05-19), and .planning/v1.13.1-EXECUTION-PLAN.md AMENDMENT block.
+
+### Added (2026-05-17 -- 2026-05-19 endgame work bundled into this beta)
+- **Phase 120 (Breakthrough Scan Category G) shipped 2026-05-17.** 9-of-9 must-haves verified. Hooked Fix 3 (Category G) closed: variable-reward axis ships the highest-nutrition flavor (own-breakthroughs surfaced back at the navigator). 4 detectors (convergence / contradiction-resolved / cross-domain analogy / reverse-salient closed) + F.7 Breakthrough Surface selector (5 verbs: Explore deeper / Confirm / File as decision / Dismiss / Back) + session-start scanner via Phase 109 navigation.cjs chokepoint + D-13..D-15 resurfacing rules + D-19 per-detector dismissal-rate canary + D-17 4-rule voice scaffold + D-18 4-tier ethics fence (HARD_FLOOR / SOFT_BAND / NEUTRAL / GREEN) + SOFT_BAND review queue in rooms-meta.db + 5-component scoring formula + "More breakthroughs (N)" affordance + D-20 LOAD-BEARING SQL invariant (every Breakthrough has a DERIVED_FROM edge by construction; 4 structural enforcement points). 159 unit tests + 4 D-20 e2e + 13 ethics-fence + voice-audit + 3 scaffold harnesses all green. Canon Part 4 cascade vocab honored (8 types; 2026-05-16 dual-graph review rejection sealed -- no ASSOCIATION_LENS / TRANSITION_LENS). Canon Part 8 clean. Canon Part 9 chokepoint preserved (10 modules route through navigation.cjs).
+- **Phase 121 (Trajectory Telemetry) shipped 2026-05-19.** 12-of-12 must-haves verified. Reframed per Canon Part 7 from "greenfield instrumentation" to "consolidation": 4 piecemeal telemetry writers (`mva.jsonl` + `selector.jsonl` + `navigation-bypass.jsonl` + `query-efficiency.jsonl`) collapse to ONE unified `~/.mindrian/telemetry/v1.13/events-YYYY-WNN.jsonl` with `type` discriminator + frozen v1 schema (per-row `schema_version: 1` Number, 15 EVENT_TYPES) + ISO-week rotation + single emit-time-validator chokepoint (7 forbidden-pattern detectors, mirrors proven `mva-telemetry.cjs` shape) + idempotent migration (source-name-prefixed sha256 fingerprint, originals renamed `*.pre-v121.bak`) + `mva-telemetry.cjs` 170 -> 58-line shim delegating to writer with legacy dual-write (Phase 118 byte-functional compat preserved; dual-write retires v1.14.0). 9 capture points wired: selector picks (88.2 + 125), tension engagement (116), auto-explore decisions (117), breakthrough dismissed (120), MVA + Hooked re-score (inherited), empathy audit CLI, room-receipt (119), PostToolUse broad-sweep into separate `command_invocation` bucket (drowning-protected via type discriminator; 100 cmd_inv + 10 selector_pick fixture proves filter-isolation). `docs/TELEMETRY-SCHEMA.md` (364 LOC) frozen v1 spec + SEED-002 ingestion guidance (arXiv 2508.03680). Canon Part 8 adversarial audit (7 gates across 17 telemetry-touching files; zero LOCAL->BRAIN egress) + D-12 silent-observability invariant (4 gates). 19/19 test suites green.
+- **Phase 121.5 re-verify fix 2026-05-19.** `/mos:dogfood-flush` (added by Phase 120) registered in `data/help-groups.json` Infrastructure group. Restores 3 previously-failing 121.5 coherence tests. Capstone coherence invariant holds against the now-complete v1.13.0 surface. `bash tests/run-all-121.5.sh` -> 11/11 suites green.
+- **SEED-003 (Brain Silent Identity) filed 2026-05-19.** Deferred user request to eliminate the API-key step entirely on top of Phase 127's stdio shim. Three architectural options scoped (per-install silent registration / plugin attestation HMAC / anonymous tier + degraded payload).
+
+### Added
+- **`/mos:mos` state-aware router (Phase 121.5-08 Sub-plan J; D-10 LOCKED).** Closes the plugin.json declaration gap flagged in Cluster 5 audit 2026-05-15 (the command was declared but the backing file was absent). The router picks the right next surface for the navigator: no room -> `/mos:onboard`; mostly-empty room -> `/mos:status` with a "suggest next move" hint; populated room -> `/mos:suggest-next`. Backed by `lib/core/state-aware-router.cjs` (pure function, hermetic unit tests in `lib/memory/state-aware-router.test.cjs`). Meets the navigator where they are -- one entrypoint that always does the right thing rather than forcing the user to pick the right `/mos:*` surface. (`commands/mos.md` [new], `lib/core/state-aware-router.cjs` [new], `lib/memory/state-aware-router.test.cjs` [new].)
+- **Soft-alias runner + 5 soft-alias stubs (Phase 121.5-08 Sub-plan J; D-09 LOCKED).** New helper `scripts/soft-alias-runner.cjs` (`softAliasRun` pure function + `emitForLLM` CLI form) returns a JSON envelope `{redirect, deprecation_note, args, ok}` so the LLM can print a single cyan deprecation line (Larry voice, no em-dash) and then transparently invoke the canonical command. Hermetic unit tests in `lib/memory/soft-alias.test.cjs` (45 PASS). (`scripts/soft-alias-runner.cjs` [new], `lib/memory/soft-alias.test.cjs` [new].)
+- **`/mos:doctor --deprecated-usage` (class L, NEW; Phase 121.5-08 Sub-plan J; D-09 final clause).** Scans recent (last-7-days) `~/.claude/projects/.../*.jsonl` session transcripts for `/mos:<deprecated>` patterns and surfaces a per-command "use `/mos:<new>` instead" hint. Pure LOCAL scan -- zero network, zero Brain, zero telemetry egress (Canon Part 8 preserved). Also activated by `--all`. Hermetic unit tests in `lib/memory/doctor-deprecation-surface.test.cjs`. `MINDRIAN_DOCTOR_TRANSCRIPTS_DIR` env-var override for hermetic tests. (`scripts/doctor.cjs`, `commands/doctor.md`, `lib/memory/doctor-deprecation-surface.test.cjs` [new].)
+- **F.1 Next Move selectors wired on `/mos:onboard` Step 6 + `/mos:diagnose` recommendation block (Phase 121.5-08 Sub-plan J; D-12 LOCKED).** Closes Canon Part 3 violations flagged in Cluster 5 audit 2026-05-15: the recommendation surfaces previously rendered as bare prose, bypassing the Decision Gate. Both surfaces now render the canonical 3-verb F.1 vocabulary (Run Methodology / Defer / Free-Text) via AskUserQuestion; the selected verb writes to STATE.md Decisions + creates a typed edge in the local graph. (`commands/onboard.md`, `commands/diagnose.md`.)
+
+### Changed
+- **5 commands deprecate to canonical surfaces (Phase 121.5-08 Sub-plan J; D-09 LOCKED).** All old commands remain functional for v1.13.x (soft-alias stubs with deprecation notes routed through `scripts/soft-alias-runner.cjs`); removal is scheduled v1.14.0. Zero tester breakage during v1.13.x:
+  - `/mos:heal` -> `/mos:doctor --heal-room` (folds into doctor's class E fix engine)
+  - `/mos:query` -> `/mos:graph "<question>"` (terminal natural-language Q&A collapses into the graph translator)
+  - `/mos:organize` -> `/mos:rooms organize <verb>` (portfolio grouping folds under the multi-room surface)
+  - `/mos:hmi-status` -> `/mos:doctor --ui-compliance --json` (D-11 LOCKED; standalone command goes away; functionality lives in doctor class F)
+  - `/mos:visualize` -> `/mos:dashboard --mermaid` (the dashboard already renders Cytoscape; the `--mermaid` flag covers the Mermaid code-block fallback that visualize used to provide)
+- **`/mos:diagnostics` is being renamed to `/mos:fingerprint` in v1.14.0 (no functional change).** The rename kills the diagnose/diagnostics naming ambiguity. Both invocations work in v1.13.x; use `/mos:fingerprint` going forward. (`commands/diagnostics.md` frontmatter `renaming_to: fingerprint`; body prepends a Renamed note before the unchanged 4-algorithm dispatcher.)
+
+## [1.13.0-beta.17] - 2026-05-15
+
+### Fixed
+- **Step 6.6 ordering hole (Bug 1 -- Phase 126.1 hotfix, 2026-05-15).** Phase 126 beta.16 hotfix `3fc008b` moved `verify-release-clean-tree` from `applies_to: ['pre-tag', 'full']` to `['full']` because `release.sh` Step 6.6 calls `--pre-tag` AFTER Steps 3-6 intentionally bump `plugin.json` + `package.json` + `CHANGELOG.md`. That made the cut sail through, but the strict clean-tree gate no longer ran pre-tag AND Test 2 of `tests/test-doctor-acceptance-preflight-checks.cjs` was converted to SKIP rather than re-pointed. Real gap, predicted by `docs/install-cache-family-premortem.md` Section 3. Fix (Option B): added a new `pre-flight` tier to the `applies_to` enum (strict subset of `pre-tag` minus in-flight-incompatible checks); added the `--pre-flight` CLI flag to `scripts/doctor.cjs`; added Step 2.5 to `scripts/release.sh` calling `doctor --acceptance --pre-flight` BEFORE Step 3 mutates the tree (HARD ABORT, no rollback needed because nothing is yet mutated); kept the existing Step 6.6 `--pre-tag` call after Step 6 (still the right tier for post-bump checks). Restored Test 2 from SKIP to PASS under the new tier; added Test 8 asserting tier filter behavior. (`scripts/doctor.cjs`, `scripts/release.sh`, `tests/test-doctor-acceptance-preflight-checks.cjs`.)
+- **Commit B 7-place lockstep gap (Bug 2 -- Phase 126.1 hotfix, 2026-05-15).** `scripts/release.sh` Step 7.5 (Commit B, the next-pre-release advance) bumped `plugin.json` + `package.json` to `NEXT_VERSION` but left `~/mindrian-marketplace/.claude-plugin/marketplace.json` at `vN`. Per `feedback_install_minisite_lockstep.md`, the 7-place lockstep contract requires the marketplace.json `version` field to advance with the plugin repo. The bug recurred in beta.16. Fix: Step 7.5 now writes a second `node -e` block that bumps `MARKETPLACE_DIR/.claude-plugin/marketplace.json` to `NEXT_VERSION` (version field only -- `source.ref` deliberately stays at `vNEW_VERSION` pinning the marketplace commit at Commit A's tag); parallel marketplace-repo `git commit` follows with message `chore: bump marketplace.json to v$NEXT_VERSION (Commit B 7-place lockstep)`. Test H asserts the bump pattern is present in `scripts/release.sh`. (`scripts/release.sh`, `tests/test-release-bump-algebra.cjs`.)
+- **Step 9.7 npx-publish self-test sandbox bug (Bug 3 -- Phase 126.1 hotfix, 2026-05-15).** `scripts/release.sh` Step 9.7 ran `npx --yes @mindrian_os/install@<version>` from an `mktemp -d` temp dir and checked the dir was non-empty after install -- but `@mindrian_os/install` installs into `~/.claude/` (the Claude Code plugin install root), NOT into cwd, so the temp-dir check spuriously failed during the beta.16 cut. Fix (Option A): switched to a HOME-override sandbox at `~/.claude/_test-install-<sha8>/` (subpath under `~/.claude/` per scope; mirrors the Phase 123 `doctor.cjs:2336` sandbox pattern). The npx run sets `HOME=$NPX_TEST_DIR` + `USERPROFILE=$NPX_TEST_DIR` + `npm_config_cache=$NPX_TEST_DIR/.npm` so the install resolves into the sandbox subpath, never touching the operator's real `~/.claude/`. Scaffold marker check now asserts `$NPX_TEST_DIR/.claude/plugins/installed_plugins.json` exists AND is parseable JSON. `trap` cleanup guarantees the sandbox dir + the pre-snapshot file are removed even on abort. Option B (extend `~/mindrianos-install-site` npm-installer with a `--target=<dir>` flag) is the cleaner long-term fix but out of scope for this hotfix (separate repo). Test I asserts the sandbox path + HOME-override are present in `scripts/release.sh` and the legacy `mktemp -d -t mos-npx-selftest` pattern is gone. (`scripts/release.sh`, `tests/test-release-bump-algebra.cjs`.)
+
+### Changed
+- **Phase 122 `teaching:` frontmatter on `/mos:mva-brief` + `/mos:mva-option` verified clean (Phase 126.1 hotfix audit, 2026-05-15).** Per `118/deferred-items.md` lines 5-20 the two MVA helper commands lacked `teaching:` strings as of Plan 118-06. Inspection found the strings were already added between then and now (`commands/mva-brief.md` line 6: 200 chars; `commands/mva-option.md` line 6: 180 chars). All four Phase 122 invariants verified: length 50-300 chars (200 + 180), zero em-dashes (`grep -nP "[—–]"` empty), 1-2 sentences each (terminal `.`), Larry-voice with WHY lede. `node scripts/build-command-registry.cjs --check` exits 0. No edits required; verification-only commit. The pre-existing `118/deferred-items.md` "Pre-existing build-command-registry teaching-field gap" entry can be marked RESOLVED in a follow-up. (`commands/mva-brief.md`, `commands/mva-option.md`.)
+
 ## [1.13.0-beta.16] - 2026-05-14
 
 ### Added

package/commands/act.md

@@ -1,6 +1,7 @@
 ---
 name: act
 description: Run Larry's best-pick methodology for your room state
+help_jtbd: "Run the next move Larry recommends, without typing the /mos: command yourself."
 argument-hint: '[--chain] [--swarm] [--dry-run]'
 body_shape: E (Action Report)
 serves_jtbd: ["plan-execution"]

package/commands/admin.md

@@ -1,6 +1,7 @@
 ---
 name: admin
 description: Manage Brain API keys from the admin panel
+help_jtbd: "Inspect plugin internals when you suspect something is off."
 argument-hint: [subcommand]
 body_shape: A (Mondrian Board)
 serves_jtbd: ["audit-room"]

package/commands/analyze-needs.md

@@ -1,6 +1,8 @@
 ---
 name: analyze-needs
 description: Score customer jobs with importance and satisfaction
+help_jtbd: "Surface user needs that change the problem statement."
+body_shape: "methodology"
 serves_jtbd: ["find-problem"]
 teaching: "When you need to know which customer jobs matter most, /mos:analyze-needs scores them by importance versus satisfaction. Best after you have a customer segment defined."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/analyze-systems.md

@@ -1,6 +1,8 @@
 ---
 name: analyze-systems
 description: Decompose a system into layers and leverage points
+help_jtbd: "See how subsystems connect, where they break, where they leverage each other."
+body_shape: "methodology"
 serves_jtbd: ["find-bottleneck"]
 teaching: "When you need to find where leverage lives in a complex system, /mos:analyze-systems decomposes it into layers and surfaces the leverage points. Best when symptoms keep recurring."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/analyze-timing.md

@@ -1,6 +1,8 @@
 ---
 name: analyze-timing
 description: Place a technology on the S-Curve timing clock
+help_jtbd: "Find the timing window your venture sits inside."
+body_shape: "methodology"
 serves_jtbd: ["understand-market"]
 teaching: "When you need to know if your technology is too early, too late, or right on time, /mos:analyze-timing places it on the S-Curve. Best before you commit to a launch window."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/auto-explore.md

@@ -1,5 +1,7 @@
 ---
 description: "Manually trigger auto-explore on a specific file (Desktop fallback when PostToolUse hook does not fire per RESEARCH 4.8)"
+help_jtbd: "Let Larry decompose your domain before you even ask."
+body_shape: "methodology"
 argument-hint: "<file_path>"
 serves_jtbd: ["find-problem", "understand-market", "explore"]
 teaching: "In the moment a new artifact lands, /mos:auto-explore kicks off the same domain decomposition the PostToolUse hook would run. Use it on Desktop when the hook does not fire."

package/commands/beautiful-question.md

@@ -1,6 +1,8 @@
 ---
 name: beautiful-question
 description: Reframe a challenge as Why / What-if / How
+help_jtbd: "Reformulate the problem before solving the wrong one."
+body_shape: "methodology"
 serves_jtbd: ["find-problem", "explore"]
 teaching: "When the framing feels stuck, /mos:beautiful-question reshapes the challenge as Why / What-if / How. The right question unlocks more progress than a better answer."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/brain-derive.md

@@ -1,5 +1,7 @@
 ---
 description: Derive BRAIN.md for section(s) now
+help_jtbd: "Pull the Brain's framework recommendations for your current section."
+body_shape: E
 argument-hint: "[section] [--all] [--cross-room] [--dry-run]"
 serves_jtbd: ["audit-room"]
 teaching: "When a room section drifts from its BRAIN.md derivation, /mos:brain-derive rebuilds the per-section Brain context now. Run after large filings or before a decision gate."

package/commands/build-knowledge.md

@@ -1,6 +1,8 @@
 ---
 name: build-knowledge
 description: Climb Ackoff's DIKW pyramid across the room
+help_jtbd: "Turn your room into a knowledge graph you can query."
+body_shape: "methodology"
 serves_jtbd: ["explore"]
 teaching: "When you have data but not yet wisdom, /mos:build-knowledge climbs Ackoff's DIKW pyramid across the room. Surfaces what you know, what you can decide, and what is still raw."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/build-thesis.md

@@ -1,6 +1,8 @@
 ---
 name: build-thesis
 description: Run the Ten-Questions investment thesis gate
+help_jtbd: "Compose the investment-grade thesis from your room's evidence."
+body_shape: "methodology"
 serves_jtbd: ["decide-pursue", "prepare-pitch"]
 teaching: "When you need to know if this venture is worth pursuing, /mos:build-thesis runs the Ten-Questions investment thesis gate. The output is a defensible go / no-go with reasons."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/causal.md

@@ -1,6 +1,8 @@
 ---
 name: causal
 description: Trace causal edges in the room's graph
+help_jtbd: "Trace cause-and-effect chains across your room's claims."
+body_shape: "methodology"
 argument-hint: [extract|trace|predict]
 serves_jtbd: ["find-problem", "find-bottleneck"]
 teaching: "When you suspect the visible problem is downstream of something else, /mos:causal traces causal edges in the room's graph. Surfaces the upstream causes worth fixing."

package/commands/challenge-assumptions.md

@@ -1,6 +1,8 @@
 ---
 name: challenge-assumptions
 description: Stress-test assumptions with Devil's Advocate
+help_jtbd: "Stress-test the assumptions your room is built on."
+body_shape: "methodology"
 serves_jtbd: ["validate-idea", "surface-contradiction"]
 teaching: "When an idea feels too clean, /mos:challenge-assumptions runs Devil's Advocate against the load-bearing claims. Catches the assumptions you stopped questioning."
 allowed-tools:

package/commands/compare-ventures.md

@@ -1,6 +1,8 @@
 ---
 name: compare-ventures
 description: Compare against ventures that tried this before
+help_jtbd: "Set two or more ventures side-by-side, scored."
+body_shape: "methodology"
 serves_jtbd: ["compare-options"]
 teaching: "When you are weighing your approach against ventures that tried this before, /mos:compare-ventures lines them up on the dimensions that matter. Saves you from re-learning their lessons."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/dashboard.md

@@ -1,7 +1,8 @@
 ---
 name: dashboard
 description: Open the Data Room dashboard (live or snapshot)
-body_shape: raw
+help_jtbd: "Open your room as a browser dashboard, De Stijl grid + graph."
+body_shape: E
 serves_jtbd: ["audit-room", "prepare-pitch"]
 teaching: "When you need to see the whole room at a glance, /mos:dashboard opens the live or snapshot view in De Stijl layout. The fastest way to read room health before a meeting."
 ui_reference: skills/ui-system/SKILL.md

package/commands/deep-grade.md

@@ -1,6 +1,8 @@
 ---
 name: deep-grade
 description: Grade a venture against 100+ calibrated projects
+help_jtbd: "Get the rigorous grading pass (Brain-enriched, 100+ student calibration)."
+body_shape: C
 serves_jtbd: ["audit-room", "compare-options"]
 teaching: "When you need a calibrated grade on the room's quality, /mos:deep-grade scores it against 100+ real student projects. Best after at least three sections are populated."
 # --- Phase 122 workflow-layer frontmatter ---

package/commands/diagnose.md

@@ -1,6 +1,8 @@
 ---
 name: diagnose
 description: Classify problem type against the PWS matrix
+help_jtbd: "See where your room is weakest and what to do next."
+body_shape: A
 serves_jtbd: ["decide-pursue"]
 teaching: "When you cannot tell if this is an Ill-Defined or Well-Defined Problem, /mos:diagnose classifies it against the PWS matrix. Knowing the problem type picks the right methodology."
 # --- Phase 122 workflow-layer frontmatter ---
@@ -56,4 +58,22 @@ Move faster than other commands. The user came here because they are stuck on WH
 ## When Complete
 
 Create the artifact using the template from the reference file.
-Offer to route them directly: "Want me to start /mos:[top recommendation] right now?"
+
+## Recommendation (Shape F.1 Next Move per Canon Part 3)
+
+Render the recommendation as a Shape F.1 selector per `skills/ui-system/SKILL.md` Section 2. Do NOT render the recommendation as bare prose -- the F.1 selector IS the Canon Part 3 Decision Gate. Rendering recommendations as prose is the canon violation Cluster 5 audit (2026-05-15) flagged.
+
+```
+[diagnose] -- NEXT MOVE
+LOCAL / BRAIN / SIGNAL
+
+Choose next move:
+
+  1. Run Methodology  -- the specific methodology for the weakest section
+  2. Defer            -- queue for milestone audit
+  3. Free-Text        -- tell Larry what you want
+```
+
+Use AskUserQuestion to surface the selector. The selected verb writes to STATE.md Decisions section AND creates a typed edge in the local graph: `(navigator) -[CHOSE {verb, reason}]-> (current-artifact)`. The 3-verb F.1 vocabulary (Run Methodology / Defer / Free-Text) is the canonical minimum per Canon Part 3; when Brain is reachable and confidence >= 0.7 the "Run Methodology" option may be marked RECOMMENDED (Phase 88.2 invariant).
+
+Phase 121.5-08 Sub-plan J D-12 LOCKED: the recommendation surface on /mos:diagnose MUST render an F.1 selector, not bare prose. Closes the Canon Part 3 violation from the Cluster 5 audit.

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]"
+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] [--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,8 @@ 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 --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,9 +1,13 @@
 ---
 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."
+# Per docs/reward-before-investment-rule.md line 60-62: surface first-paragraph extraction preview before full transcript ask. Remediation tracked as follow-up phase.
+interactive_first_reward: paragraph_preview
 allowed-tools:
   - Read
   - Write

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,8 +1,12 @@
 ---
 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.
+interactive_first_reward: calibration_distribution_preview
 # --- Phase 122 workflow-layer frontmatter ---
 kind: methodology
 frameworks: ["PWS Triple Validation Compass"]

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"]