@mindrian_os/cli 2.0.0-beta.3 → 2.0.0-beta.33

package/.claude-plugin/plugin.json

@@ -0,0 +1,21 @@
+{
+  "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": "2.0.0-beta.33",
+  "author": {
+    "name": "Jonathan Sagir",
+    "url": "https://mindrian-os.com"
+  },
+  "homepage": "https://mindrian-os.com",
+  "repository": "https://github.com/jsagir/mindrian-os-plugin",
+  "license": "BSL-1.1",
+  "keywords": [
+    "innovation",
+    "pws",
+    "venture",
+    "methodology",
+    "data-room",
+    "thinking-partner",
+    "larry"
+  ]
+}

package/.mcp.json

@@ -0,0 +1,14 @@
+{
+  "mcpServers": {
+    "mindrian-os": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/bin/mindrian-mcp-server.cjs"],
+      "alwaysLoad": true
+    },
+    "mindrian-brain": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/bin/mindrian-brain-mcp-client.cjs"],
+      "alwaysLoad": true
+    }
+  }
+}

package/CHANGELOG.md

@@ -1,3 +1,500 @@
+## [2.0.0-beta.33] - 2026-09-10
+
+### Fixed - Theo answers Larry end to end (quick task 260910-hni)
+
+- `brain_ask` through the plugin no longer returns an empty DirectiveEnvelope on every Theo answer.
+  `lib/core/brain-client.cjs` `ask()` now composes `directive.guided.framework`, `next_gate.options`
+  (ranked framework chain with the `/mos:` commands Theo links to each framework) and a new additive
+  `grounding` field (Theo's ranked book rows: chapterId, section, score, snippet) from Theo's
+  `structured_rows` + `recommend_chain`. The question's own words are never echoed back (Canon Part 8).
+  Incumbent-shaped responses pass through byte-unchanged. Live e2e through the MCP shim: framework
+  Design Thinking, 4 chain options, 8 grounding rows.
+- `askOp()` accepts Theo's op-mode shape (`rows` + `coverage`); it had been degrading every curated op to
+  zero rows because Theo never sends a `count` key.
+- `lib/mcp/brain-router.cjs` routes `/mos:act` chains from the commands Theo attaches to each framework,
+  so Tier 3 is graph-grounded again instead of silently falling to the local heuristic.
+- `lib/core/part8-egress-guard.cjs` recognizes the `recommend_chain` payload shape (rung enum +
+  step budget) as a known safe shape. `tests/run-all-339.sh` now counts a `.cjs` leg that prints SKIP
+  as skipped, not passed.
+- Larry's thin-grounding clause (`skills/larry-personality/SKILL.md`) keys on an empty `grounding.rows`
+  instead of the retired "empty signals set" wording.
+
+### Removed - Canon Part 8 (quick task 260910-h32)
+
+- `scripts/sync-rooms-brain` and its three detached spawns (`scripts/session-start`, twice in
+  `scripts/room-registry`). It string-interpolated every room's name, venture, stage, status and path
+  into `brain_write` Cypher and sent it to the Brain origin on every SessionStart (observed: 1,498
+  POSTs, 55 rooms, Authorization header on each). Room state already lives in local SQLite via
+  `sync-rooms-graph`. A default-deny census test (`tests/test-quick-260910-h32-no-brain-write-from-scripts.cjs`,
+  registered in `run-all-257.sh`) keeps it from coming back.
+
+## [2.0.0-beta.31] - 2026-09-10
+
+### Changed - install and update overhaul, Phase 341 waves 1-5 (SEED teardown 2026-09-09)
+
+- The plugin is now delivered as an npm artifact, not a git checkout. `package.json` `files` is the
+  runtime tree only (24 entries with `!` negations; `docs/`, `dist/`, `.planning/`, `tests/`, and
+  `lib/wiki/editor-src` no longer ship); `npm pack --dry-run` measures about 1,830 entries / 29 MB
+  unpacked against the 755 MB / 16,597-file tag it replaces (341-04-SUMMARY.md).
+- `@huggingface/transformers` and its onnxruntime/sharp stack (380 MB of native binaries for every
+  platform) left `dependencies`. Eureka's embedding model is now an explicit one-time opt-in:
+  `/mos:eureka enable` (mirrored by `doctor --fix eureka`) installs it platform-scoped into
+  `~/.mindrian/eureka-deps/`, shared across plugin versions; `lib/core/eureka-deps-resolver.cjs` is the
+  single resolution authority and never throws (341-02).
+- `npm-shrinkwrap.json` ships inside the tarball so the Claude Code loader's own
+  `npm ci --ignore-scripts` restores the 29 MB pure-JS runtime set per machine (all five sqlite-vec
+  platform packages resolve locally). `bundleDependencies` was rejected by measurement: it packs only
+  the publish host's platform package.
+- Doctor class S is honest on a slim install: five layers, `capability reachable` is the blocker and
+  `model_installed` an advisory carrying the exact enable command; the un-awaited `isModelCached`
+  (formerly class-s-eureka-smoke.cjs:180) is fixed and trapped by a regression test; every consumer
+  degrades through one `ENCODER_UNAVAILABLE_HINT`; a tripwire pins that Eureka, critic included, has no
+  Brain/Theo reach (341-03).
+- Release ceremony: Step 6.7's node_modules vendoring is gone (its slot now generates the shrinkwrap
+  behind `scripts/release-lib/shrinkwrap-gate.sh`); Step 4 writes an exact npm `source.version` pin
+  to the marketplace (git `ref`/`url` retired); Step 9.5's blanket `node_modules/` grep became the
+  payload assertion; doctor's `version-of-record-published` compares `source.version` (legacy git shape
+  still accepted during the transition) (341-05).
+- Two harness policies on the pre-tag rung, Phase 298 shape: `release-payload-ceiling` (blocking,
+  entryCount <= 20000 and unpackedSize <= 268435456 from `npm pack --dry-run --json`) and
+  `registry-drift` (logged; a command that silently vanishes from the registry is surfaced) (341-04).
+- New phase aggregator `tests/run-all-341.sh` with an EXPECTED-RED lane (`run_red_until`): a
+  tripwire that passes while its artifact is still absent is a FAIL, not a pass (341-01).
+
+### Fixed
+
+- `tests/test-release-bump-tag-and-publish-gates.cjs` cases 10/11: `\Z` is not a JavaScript
+  regex end-of-string anchor (it matched a literal "Z"), which truncated the Step 9.7 block and hid its
+  `exit 1`. The documented "package-name drift" was not the cause. Phase 310's two SKIPs are now one.
+- `/mos:eureka help` with no room bound fell into "unknown subcommand" instead of printing usage.
+
+
+## [2.0.0-beta.29] - 2026-09-09
+
+### Added
+- **Phase 298 (SEED-032): Harness-as-Code.** MindrianOS declares and machine-enforces its own
+  agent harness for the first time. `data/harness-policies/` is the closed, versioned schema:
+  eleven slice-1 policies (five gates, four voice rules, the memory-write declaration, the
+  Larry contract-parity declaration), each carrying an enforcement rung (`declared` / `logged`
+  / `blocking`) read from disk, never hardcoded. `scripts/run-harness.cjs` is the one idempotent
+  policy runner: a tiered `--check`, a `--room <dir>` convergence scan (proven idempotent twice
+  in a row against a committed fixture, byte-identical output, zero writes), and a `--policy
+  <id>` promotion review that prints one evaluator's verdict and never recomputes it.
+  `scripts/build-harness-manifest.cjs` goes to manifest v2 (three additive keys -- `policies`,
+  `larry_surfaces`, `fixture_ref` -- `maps` stays exactly three) and now runs the Larry
+  contract-parity checks inline, so `--check` fails closed the moment any of Larry's three
+  speaking surfaces drops a core-contract phrase or the Desktop wire exceeds its 1,950-byte
+  budget. `node scripts/doctor.cjs --acceptance` gained a `harness-policies` blocker that spawns
+  the runner, wiring the whole harness into the release train's own gate. The pre-commit drift
+  guard now fires on any edit under `data/harness-policies/` or `data/harness-fixtures/`, so the
+  manifest's own digest cannot silently rot. Two long-red manifest-cluster tests were repaired
+  (repointed at the file that actually carries the guard after Phase 235-01's rewrite) rather
+  than left recorded as known-broken. 15 plans, 6 waves, goal-backward verified.
+- **Admin-only commands stop leaking into recommendations (SEED-052).** The Brain
+  recommendation scorer (`lib/workflow/f-selector-ranker.cjs`) now reads each command's
+  `visibility` field (mirrored into `data/command-registry.json` by the generator) and filters
+  out `visibility: admin` candidates for a non-admin navigator, fail-closed by default. Closes a
+  live, reproduced leak: `/mos:admin` was ranking as the #2 recommendation for every navigator,
+  admin or not, before this fix.
+- **Skill-optimization smoke calibration reconciliation (SEED-061).** `scripts/skillopt-funnel.cjs`
+  gained a deterministic, exact-match reconciliation pass over `enumerateQueries`'s full-roster
+  output: a `should_not_trigger` negative labeled `expected_skill: null` that exactly collides
+  with a real positive elsewhere in the roster is corrected before the flag rule scores it,
+  closing a disclosed false-alarm class from Phase 230's smoke calibration (`230-07-CALIBRATION.md`).
+  The fix also closes a resume-path staleness hole: a resumed funnel run now re-applies the
+  reconciled label instead of reading a stale persisted verdict. Zero live model calls anywhere
+  in the fix or its tests.
+- **`scripts/release.sh` Step 5.5 stops crying wolf on a good push (SEED-051).** The tag-push
+  verification gate now checks an independent `git ls-remote` on `origin/main`'s SHA before
+  deciding whether a still-not-visible tag is a real failure or just GitHub replication lag.
+  When the push demonstrably landed, a slow tag now prints a warning and the ceremony continues
+  through the acceptance/marketplace/post-verify steps; when it did not land, the original hard
+  abort is preserved. The abort-vs-warn decision lives in a new, independently testable library,
+  `scripts/release-lib/verify-tag-push.sh`. Reproduces and fixes the exact false alarm hit on
+  the v1.15.0 release ceremony (2026-07-02).
+
+### Changed
+- Twelve stale-duplicate roadmap phase stubs (283, 297, 299, 300, 302, 304, 305, 306, 309, 312,
+  325, 326) closed as `ABSORBED BY PHASE <N>`, each citing the specific already-shipped phase
+  and code evidence, after tracing that their seeds' own required capabilities were already
+  live -- no renumbering, no plans lost, roadmap now tells the truth about what still needs
+  building. Two further clusters fused (319 absorbs 320-322/324 into one Host Runtime Decision
+  Record; 333 absorbs 334 into one Room-as-GraphRAG walk-test-then-build phase).
+
+## [2.0.0-beta.27] - 2026-09-07
+
+### Added
+- Larry recognizes Theo by name on all three surfaces. `agents/larry-extended.md` gained
+  `## If asked about Theo by name` (Theo is MindrianOS's own teaching-graph backend behind every
+  `brain_*` call; a direct by-name question gets an honest brief answer, never volunteered), with a
+  narrow inline carve-out on the Never-Do "mention databases or architecture" rule (quick
+  260907-i8j). The Desktop/Cowork MCP wire, `lib/mcp/runtime-instructions.cjs`, gained a THEO
+  clause inside the 1,950-byte served budget (1888 -> 1944 bytes) with the Canon Part 8 BOUNDARIES
+  paragraph byte-identical and still the tail (quick 260907-m2j). No endpoint, host, or wiring
+  detail is disclosed on any surface.
+- `### Honest about thin grounding` in `skills/larry-personality/SKILL.md`: on any thin `brain_*`
+  signal (an empty DirectiveEnvelope `signals` set, a zero or ambiguous `normalize_framework_name`
+  match, a low `orchestration_readiness` score) one capability-honesty clause rides inside the
+  answer Larry is already giving, naming no backend noun. Finishes wiring Decision #8, "Honest
+  refusal everywhere", into Larry's voice (quick 260907-i8j).
+- `lib/core/repo-version.cjs`: the one canonical answer to "what version is this repo" (module +
+  CLI), refusing with a named error instead of guessing when resolved from a `.claude/worktrees/*`
+  checkout (quick 260906-t3s).
+- `scripts/check-worktree-hygiene.cjs` plus a `worktree-hygiene` blocker in `doctor --acceptance`:
+  diffs `.claude/worktrees/*` on disk against `git worktree list`, classifies every unregistered
+  checkout (`live-gitdir` / `safe-orphan` / `review`) by hashing its files against the object
+  database, and is the only governed delete path (`--prune --confirm`; `review` is never
+  auto-deleted). 18 hermetic tests (quick 260906-t3s).
+- `docs/CANON-PHASE-MAP.md` `## Amendment cascade rule`: every canon amendment discovers the
+  version-pinning tests by an escaped-regex-aware grep instead of a hand-named list, and bumps
+  `Date:` together with `Version:` (quick 260907-m2l).
+- `docs/autopsies/2026-09-06-worktree-version-contamination-incident.md`, cross-referenced from
+  CLAUDE.md's WORKSPACE GUARD (quick 260906-t3s).
+
+### Fixed
+- Canon version floors: `test-205-elevation-doctrine-floor` (pinned 1.24) and
+  `test-cirs-render-coverage-floor` (pinned 1.16) cascaded to the live v1.27;
+  `test-bono-verdict` and `test-canon-part-9-ratification` redesigned from live-header equality
+  (structurally doomed the moment a later entry ships) to append-only provenance plus a monotonic
+  floor; the `run-all-340.sh` quarantine on part-9-ratification lifted; `docs/MINDRIAN-CANON.md`
+  `Date:` restored to 2026-09-05, the v1.27 commit date, after Phase 340's three bumps dropped it
+  (quick 260907-m2l).
+- Four stale lines in `agents/larry-extended.md` (em-dash wording under a hyphens-only rule, a
+  hardcoded sensor count now read from the registry, a nonexistent `lib/memory/user-md-persona.cjs`
+  path corrected to `lib/core/user-md-ops.cjs`, a moved dual-path registration note) and a
+  memory-layer contradiction in `skills/larry-personality/SKILL.md` (quick 260907-m2j).
+
+### Removed
+- `lib/mcp/larry-server-instructions.md`: an orphan loaded by nothing at runtime that named nine
+  tools which do not exist and opened with the exact first-contact string `test-143.2` forbids.
+  Its one live rule, the BCH-03 two-pass turn-ordering doctrine, relocated verbatim into
+  `skills/larry-personality/SKILL.md`; `tests/test-bch-01-ownership.cjs` repointed at it
+  (quick 260907-m2j).
+
+## [2.0.0-beta.25] - 2026-09-06
+
+### Added
+- 
+
+## [2.0.0-beta.23] - 2026-09-06
+
+### Added
+- 
+
+## [2.0.0-beta.21] - 2026-09-04
+
+### Fixed
+- `room_search` no longer skips every non-`.md` file in a room. `lib/mcp/tools/room.cjs`'s
+  file walk widened its allowlist to `.html` and `.htm` (grounded in the repo's own canonical
+  artifact extension list, `graph-backfill.cjs`'s `ARTIFACT_EXT`), so search now finds content
+  inside HTML briefs, rubrics, and decks that a room's own tools already generate. A new
+  dependency-free, line-preserving text pass strips markup before matching, so `<script>`,
+  `<style>`, and comment regions cannot produce a false hit, and the reported line number stays
+  correct against the source file. 22-check regression suite added
+  (`tests/test-room-search-html-blindness.cjs`).
+- Filed, not fixed in this cut: the same root cause (a docblock in
+  `lib/core/doc-text-extractor.cjs` incorrectly claims the `cheerio` HTML parser is available;
+  it is in neither `package.json` nor `node_modules`) means `.html` room artifacts still
+  contribute no text to graph derivation, candidate production, or LazyGraph. Adding `cheerio`
+  is a dependency and release decision, tracked at
+  `.planning/debug/html-artifacts-invisible-to-graph-derivation.md`.
+
+## [2.0.0-beta.19] - 2026-09-04
+
+### Changed
+- **The flip.** `lib/core/brain-client.cjs` line 24's default origin moves from the incumbent
+  Brain to `https://theo-mcp.onrender.com`, a BARE origin (no path, no trailing slash). For a
+  user: Larry's methodology now comes from Theo, and nothing about how you use MindrianOS
+  changes. Rollback stays one line: revert line 24 in a patch release, or set
+  `MINDRIAN_BRAIN_URL` on one install. Both paths are valid only while the previous service is
+  still running. The previous service is SUSPENDED after a soak window, never deleted, compute
+  suspended before data.
+- Doctor's class M layer 6 store-identity check is now complete across both cuts. The
+  dual-shape `brain_stats` read shipped in the PREP cut (safe against both Brains). This cut
+  moves the two values that had to move WITH the origin: the canon endpoint (`CANON_BRAIN_URL`)
+  and the per-origin node floor (`CANON_NODE_FLOOR = 29000` for the incumbent,
+  `THEO_NODE_FLOOR = 1000` for Theo). The floor keys on the resolved origin, so a
+  `MINDRIAN_BRAIN_URL` rollback restores the incumbent's floor in the same motion.
+- The `test-245` tripwire (`tests/test-245-skill-frontmatter-inert-keys.cjs`) and `CLAUDE.md`
+  moved together with line 24, in the same commit, per the pairing that tripwire exists to
+  enforce.
+
+### Known, expected behavior after the flip
+- `/mos:leadership` and due-diligence consults answer thinner through Theo until the 30
+  uncovered names are ingested (Theo holds the `/mos:leadership` command node with zero
+  framework links); this is an honest-empty coverage block, not an error. Covered: 228 of 258,
+  88.4%. Uncovered: 30 of 258. The 30 names bind Theo's decommission task, not this flip.
+- `brain_write` always refuses with `WRITE_PATH_DISABLED`: canon writes go through Theo's own
+  governed payload path, and this is not a tier a better key opens.
+- A count-store query plan may draw `PLAN_REJECTED`; answer it by adding a property filter, not
+  by concluding the tool is broken.
+- `scripts/probe-brain-contract.cjs` legs invert as expected, documented not broken: legs a and
+  d port cleanly; leg b inverts because Theo SERVES `text2cypher` (the expected 403 does not
+  arrive) and `brain_ask_anything` still draws an unknown-tool error, but for a different reason
+  (Theo has no allowlist gate at all); leg c partially inverts because `BoundedReadRefusal` is
+  incumbent-authored text while Theo's refusals are typed codes; leg e inverts entirely because
+  it asserts Memgraph index names Theo's Aura instance does not have.
+- The enrichment queue will capture on nearly every `orchestration_readiness` call during soak.
+  That is canon thinness correctly measured, bounded and deduped by framework name, not a leak.
+
+## [2.0.0-beta.17] - 2026-09-04
+
+### Added
+- `scripts/check-tool-honesty.cjs`: a standing, advisory MCP tool-honesty gate that
+  statically scans every `server.tool()` registration and command branch across
+  `lib/mcp/tool-router.cjs`, `lib/mcp/tools/*.cjs` and `lib/mcp/contract-version.cjs`
+  for a description-vs-behavior mismatch (a tool description claiming it writes/files/
+  persists something its handler never actually reaches a write primitive for) - the
+  broader sweep `.planning/debug/meeting-file-meeting-false-success.md`'s Non-Code
+  Follow-ups section named as unscoped work once the `meeting` tool itself was fixed
+  (quick 260903-kwl). Wired advisory (`--check` WARNs and exits 0, `--strict` restores
+  hard-fail, `--report` prints the full per-branch table) at pre-commit (path-scoped to
+  the MCP tool surface), `doctor --acceptance` (new `tool-honesty` coverage-gate entry),
+  and `release.sh` (outside the SHAPE-GATE sentinel pair) - the same advisory-on-
+  introduction posture `check-shape-declaration.cjs` established at Phase 210. First live
+  run against the current tree (36 tools, 130 command branches scanned): 1 HIGH RISK
+  finding, 8 MEDIUM, 1 UNKNOWN, 0 fixed by this change. Every finding is untriaged;
+  human review is the named next step before any finding is fixed or the gate is
+  hardened to `--strict`.
+
+### Fixed
+- The `meeting` MCP tool's `file-meeting` command returned a completion-shaped response
+  ("## File Meeting", room state, a filing-protocol section, the echoed transcript, a
+  "Meeting filed" footer) while writing nothing - no `writeClaimNode`, no `artifact_file`
+  call, no room.db mutation anywhere in the handler. Worse, the one thing the branch did
+  try to do (hand back `references/meeting/filing-protocol.md`) also returned nothing
+  usable, because that reference file did not exist on disk and the branch silently
+  dropped the section on a missed read. Fixed: an honest tool description naming
+  `artifact_file` as the real write path and `/mos:file-meeting` as the fuller CLI path;
+  a leading, machine-checkable `**filed: false**` marker on all three meeting branches
+  (`file-meeting`, `pipeline`, `speakers`); an explicit missing-reference signal instead
+  of silent omission; and a real `references/meeting/filing-protocol.md` carrying the
+  Phase 150.8 Claimify four-pass protocol in surface-neutral form, pinned by
+  `tests/test-kwl-meeting-mcp-honesty.cjs` (registered in `tests/run-all-266.sh`).
+  What did NOT change: the MCP surface still does not call `writeClaimNode` itself, and
+  the Tri-Polar parity gap this defect surfaced - the CLI (`/mos:file-meeting`) has had
+  real DIKW-typed meeting filing since 2026-06-12, Desktop and Cowork never have - remains
+  open, tracked in `.planning/debug/meeting-file-meeting-false-success.md`.
+- Bare `scripts/<name>` invocations (`bash scripts/foo`, `node scripts/foo.cjs`) are now
+  anchored with `CLAUDE_PLUGIN_ROOT` (or the fail-closed `MINDRIAN_OS_ROOT` form for
+  hand-authored skills), so a Bash tool invocation resolves against the plugin install
+  directory instead of the user's own session cwd. The real security finding, not just a
+  reliability improvement: a bare invocation previously executed whatever file happened to
+  exist at that relative path inside the user's own Data Room -- a local code-execution
+  shadowing vector, not only a portability bug, since a same-named file at `scripts/<name>`
+  in a user's room would silently substitute for the plugin's own script. Phase 274 (the
+  sibling of Phase 271's `references/` citation fix, and the fourth pass at this disease
+  class in this repo): 30 command-surface sites, 3 hand-authored skill sites, and 1 agent
+  site anchored; a fresh full-tree scan confirms zero unanchored sites remain (`sites=156
+  anchored=154 allowlisted=2 violations=0`, script tier). `scripts/verify-release` gains
+  gate 10f, cloning gate 10c's exact fail-closed shape, so this class cannot silently
+  return in a future command.
+- **MCP tool honesty, close of the triage phase (Phase 276).** The `check-tool-honesty.cjs`
+  gate's own `switch (command)` branch splitter was dead code (a masked-text regex
+  swallowed every case label), so `room_state`/`room_content`/`room_graph` were graded
+  against their whole handler body instead of per command; fixing the one-line bug took the
+  live sweep from 10 findings to a corrected 24 (5 HIGH RISK, 18 MEDIUM, 1 UNKNOWN) with
+  discovery totals unchanged (36 tools / 130 branches both before and after). Every one of
+  those 24 now carries a written disposition in a checked-in ledger a test diffs against the
+  live scan in both directions; global HIGH RISK is 0. Corrected the `orchestration`,
+  `export`, `room_content`, `gate_render` and `graph_write` descriptions so none claims a
+  write, a render, or a persisted mint its handler cannot perform, and removed every false
+  completion assertion ("Snapshot generated", "Dashboard generated", "Export complete",
+  "Scout intelligence gathered"). Propagated the Node >=22.16.0 busy-timeout option to every
+  room.db (and sibling-db) opener that can genuinely contend (proven under a held write lock:
+  elapsed time moved from ~0.3ms instant failure to a genuine ~5s bounded wait), and
+  `spine-events.cjs` now reports typed `room_db_busy`/`room_db_broken` reasons instead of
+  claiming there is no database about one it just proved exists. Shipped a new `claim_write`
+  MCP tool (the first Desktop/Cowork-reachable real DIKW claim write) and wired the `meeting`
+  tool's `file-meeting` command through the governed `gate_render`/`gate_answer` confirmation
+  gate, with promotion to `confirmed` proven against `room.db` independently of the tool's own
+  response text. Full record: `.planning/phases/276-mcp-tool-honesty-triage-and-close-the-
+  check-tool-honesty-cjs/`.
+- **The phase's one true silent failure: a Theo readiness miss vanishing with nothing written
+  anywhere (Phase 339, plan 339-05, D-03 consumer 3).** `lib/core/enrichment-queue.cjs`'s
+  `captureReadinessMiss` gains two additive capture arms recognizing Theo's own
+  `orchestration_readiness` payload shapes, a scored RESOLVED miss and a REFUSAL miss, each
+  guarded so an incumbent-shaped payload cannot reach either new branch;
+  `tests/test-339-enrichment-theo-shapes.cjs` went from 3 of 7 fixtures green to 7 of 7.
+  Operational expectation for the soak window, named so nobody reads it as a leak: post-flip
+  nearly every `orchestration_readiness` call will capture, because Theo's own header reports
+  148 of 149 Frameworks with zero technique linkage, the queue is bounded (`SOFT_CAP`/
+  `HARD_CAP`) and deduped by framework name, and that is canon thinness correctly measured,
+  not a defect. What did NOT change: the incumbent's own two capture shapes (`grounded`,
+  `readiness_score`) are untouched, proven by `tests/test-249-enrichment-queue.cjs` staying
+  13 of 13 green.
+
+### Changed
+- **RS pipeline spine-wiring + expert-graph reconciliation (Phase 296, SEED-030).** `lib/core/rs_cache.py`'s remote `rs-external` Pinecone index/namespace path (one namespace per topic, 1024-dim `multilingual-e5-large` integrated embeddings) is retired and replaced by a per-room local sidecar cache at `<room>/research/<topic-slug>/.rs-signal-cache/{vectors.jsonl,manifest.json}`, embedded through the one shipped local encoder (`embedding-spine.cjs::embedTexts`) via the new `scripts/rs-vector-bridge.cjs` JSON-stdio bridge (the D-02 answer). `scripts/rs-engine.py` Mode B/C, `lib/core/rs_hybrid.py`, `lib/core/rs-pinecone-bridge.cjs` and `lib/core/rs-differential-scorer.cjs` all thread an explicit room scope end to end.
+  - **SEED-029 F8 consequence:** the signal corpus is now per room, so a topic cached in one room is never served into another. This is a real Cowork behavior change, named rather than buried: two rooms working the same topic now each fetch and embed once, independently, rather than sharing one cache entry -- a real duplicated-work cost paid to close a cross-room data-bleed bug.
+  - **Dimensional consequence:** the external/hybrid corpus now lives in the same 384-dimensional local encoder space as every other vector in the room, so the 384-vs-1024-dim mixed-space cosine hazard documented in `scripts/rs-engine.py` and `lib/core/rs-engine.cjs` is removed by construction rather than guarded at runtime (`tests/296-dim-invariant.sh` now asserts, no longer SKIPs).
+  - **`rs-experts` degrade split:** the old Tier-0 message conflated three distinct causes (no transport ships / transport unreachable / topic genuinely has zero experts) into one hand-rolled string, with the third case -- a correct answer -- mis-dressed as a fault. Now routes through the already-shipped `lib/core/refusal-messaging.cjs` (`REFUSAL_KINDS.unreachable`), producing three pairwise-distinguishable outcomes; a genuinely empty expert list renders as a success, not a refusal.
+  - **Deliberately NOT done, and why:** `PINECONE_API_KEY` and the `pinecone` package stay (D-06) -- still load-bearing for `scripts/compute-hsi.py` Tier 2 and `lib/core/pinecone-inference.cjs` (Phase 272, out of scope here); `scripts/auto-explore-fire.cjs`'s direct `rs-engine.py --mode hybrid` spawn was not moved onto the `rs-backend-dispatch.cjs` chokepoint, only named in source and fenced by an argv-contract test (Phase 272-10 remains its own open item); `scripts/rs-engine.py` and `lib/core/rs_corpus.py` stay Python (D-04, Phase 283 is the eventual home for eliminating that runtime).
+  - **Three corrected premises**, recorded so the record is not lost: `embedding-spine.cjs` never wrote to `room.db` (F-1, `vector-store.cjs` owns persistence); RS internal and cross-room modes were already Pinecone-free before this phase (F-3); `rs-experts` has had no remote Brain-Cypher coupling since 2026-05-22 (F-6) -- the seed's original Option A/B Aura framing did not apply.
+  - **Phase 228** is this same seed's orphaned earlier registration in the closed v1.15.0 milestone (directory holds only a `.gitkeep`, no CONTEXT/RESEARCH/PLAN/SUMMARY ever landed); Phase 296 is its live successor in v2.1.0.
+  - `tests/296-pinecone-residue.sh` is the two-sided boundary gate for this change: it asserts PRESENCE of the surfaces D-06 kept (`requirements-hsi.txt`'s `pinecone` declaration, `compute-hsi.py`'s `PINECONE_API_KEY` read, `pinecone-inference.cjs`'s `api.pinecone.io` egress) and ABSENCE of the retired surface, since an over-eager cleanup silently breaking `compute-hsi.py` Tier 2 was judged the likelier failure mode here, not a missed removal.
+- **Usher-division doctrine corrected (navigator-directed, 2026-08-28).** `skills/larry-personality/SKILL.md`'s Hierarchical Navigator section previously divided authority by step ownership: the tool owned Usher steps 1-2, the human owned steps 3-4, and Larry "NEVER crosses into step 3." Product evidence falsified that rule -- in December 2025 Mindrian produced a non-obvious cross-framework synthesis (how McKinsey's Seven Steps, Usher's own cumulative-synthesis model, and Abbie's three pathways relate) that the navigator had not already seen, which the old text would have forbidden it from ever producing. The division is now per-step and shared at generation: step 1 either party may surface an incomplete pattern; step 2 is Mindrian's strongest lane; step 3 either the human or Mindrian may generate a candidate synthesis; **step 4 the navigator retains final authority**, with Mindrian helping challenge, test and refine. Human-in-Command is preserved and made more explicit, not weakened -- only the flat step-3 prohibition changed. The navigator's framing: "Insight generation is not insight authority." New pull-quote replaces the old Aronhime line: "Mindrian may propose the leap. The navigator decides whether the leap is real." `tests/test-posture-ids-drift.cjs` re-pinned to the new quote in the same commit; its exactly-three posture-id assertion (`push_forward` / `hold` / `pull_back`) and the "restraint is the product working correctly" pin are byte-untouched, since this correction concerns the step-3 authority split and not the posture-dial mechanism. The Phase 141 CHANGELOG entry that records the original doctrine is deliberately left as-is; history is not retconned.
+- **The Brain problem-type alias table is now origin-selected (Phase 339, plan 339-04,
+  FLIP-02, D-03 consumer 1).** `lib/core/brain-client.cjs`'s single
+  `BRAIN_PROBLEM_TYPE_ALIASES` table is replaced by two frozen tables,
+  `BRAIN_PROBLEM_TYPE_ALIASES_INCUMBENT` and `BRAIN_PROBLEM_TYPE_ALIASES_THEO`, selected by
+  a new `_brainProblemTypeAliases()` function reading the resolved origin against a new
+  exported `THEO_ORIGINS` set, so a future `MINDRIAN_BRAIN_URL` change moves vocabulary and
+  URL together instead of the two drifting apart. What did NOT change: today's wire traffic
+  is byte-identical, because the incumbent origin still selects the incumbent table
+  (`tests/test-254-normalize-roundtrip-probe.cjs` Arms 4-5 green).
+- **The `brain_schema` memo is now keyed by origin, as defense in depth (Phase 339, plan
+  339-04, FLIP-05, D-13 as corrected).** The original D-13 ask was a flush mechanism;
+  research corrected the premise, recorded here plainly: no flush exists to perform, because
+  `BRAIN_URL` is a module-scope const resolved once at require time and the memo is
+  process-local, so no running process can ever observe an origin change during its own
+  lifetime. The origin-keyed guard ships anyway, becoming load-bearing the day anything
+  makes the origin mutable per process. What did NOT change: the 30-minute cache TTL and
+  the existing sentinel guard are untouched; `tests/test-339-schema-memo-origin-keyed.cjs`
+  (all 7 arms) is green.
+- **A fourth silent-degrade consumer, now disclosed rather than shipped unnamed (Phase 339,
+  plan 339-05, D-03b).** `lib/mcp/brain-router.cjs`'s Tier-3 `brainRoute()` previously fell
+  back to the Tier-2 local heuristic with no trace whenever a Brain response arrived without
+  a usable `next_gate`. `recommend()` now attaches an additive `brain_router_note:
+  'answered_no_next_gate'` field when that happens, carried through a module-scope variable
+  that never changes `brainRoute()`'s own return contract. What did NOT change: an
+  incumbent-shaped payload with `next_gate` present produces a byte-identical return object,
+  with no new field.
+- **The update path is now named in the `unreachable` and `no_key` refusal copy, from a
+  single frozen source (Phase 339, plan 339-06, FLIP-04, D-08).** `lib/core/update-path.cjs`
+  is the one place the two-command update path (`/plugin marketplace update`, then
+  `claude plugin update mos@mindrian-marketplace`) is spelled out; both refusal shapes in
+  `lib/core/refusal-messaging.cjs` now name it, and `unreachable`'s old bare-retry promise is
+  replaced with copy that does not promise what a suspended origin cannot deliver. The
+  honest limit, carried verbatim from this plan's own code comment: "This copy ships in
+  bytes. An install that has not updated prints the OLD string, because a main commit is not
+  live until released AND picked up. This change is the durable fix for the next origin move
+  and for honesty; the levers that reach today's stale population are the soak window and
+  the tester note."
+- **The origin literal sweep (Phase 339, plan 339-07, FLIP-01, D-12).**
+  `scripts/probe-brain-contract.cjs` and `scripts/build-brain-census.cjs`, the two remaining
+  runtime sites that declared their own Brain origin literal, now resolve it through
+  `getBrainUrl()` like every other call site; `tests/test-339-origin-single-source.cjs` is
+  fully green (0 violations, was 6). The generated census artifacts
+  (`data/brain-census.generated.json`, `docs/BRAIN-GRAPH-CENSUS.generated.md`) are left
+  unchanged, for three recorded reasons: the generator carries no `--check` release gate by
+  design, because a release gate must never depend on live network; Lane B requires an
+  operator-supplied admin key and Theo has none, so `brain_write` refuses unconditionally;
+  and re-running Lane A against Theo today would silently discard the census record the
+  2026-08 phases were measured against, replacing a census of the incumbent's 29,200-node
+  graph with one of Theo's own (measured live at 1,253 nodes). Re-census against Theo is
+  registered as a deferred item, not addressed by any plan in this phase.
+- **Desktop and Cowork connector docs now point at Theo (Phase 339, plan 339-08, FLIP-06,
+  D-09).** Six hand-authored sources and their generated mirrors now name
+  `https://theo-mcp.onrender.com/mcp`, WITH the `/mcp` path, as the connector URL, under the
+  unchanged connector key `mindrian-brain`, with the `Authorization` header dropped, because
+  Theo returns byte-identical payloads for a real key, a garbage key, and no header at all.
+  What did NOT change: `BRAIN_TOOL_MATCHER` and `hooks/hooks.json` were not touched.
+- **The reciprocal cross-repo record and the 269-05 readiness-gate rewrite (Phase 339, plan
+  339-09, FLIP-07, FLIP-08, D-10, D-14).** `docs/339-NOTE-theo-desktop-connector-key.md` now
+  exists at the path Theo's own shipped README already cites, naming `mindrian-brain` as the
+  sole prescribed connector key; a third alternation token for `BRAIN_TOOL_MATCHER` was
+  deliberately not added. Phase 269-05's Task 1 checklist, which read PASS from facts that
+  were never in question, is rewritten to three legs sourced from live, dated Theo records;
+  the three retired items are kept in place with a dated reason rather than deleted.
+
+**The flip-day content fact, verbatim from Session T (D-06a):** `/mos:leadership` and
+due-diligence consults answer thinner through Theo until the 30 names are ingested (Theo
+holds the `/mos:leadership` command node with zero framework links); this is an
+honest-empty coverage block, not an error. The 30 uncovered names bind Theo's own
+decommission task, NOT this flip, per the coverage ruling. The named-Frameworks ratio is
+RETIRED as a coverage measure: coverage is a set question, `Covered: 228 of 258, 88.4%`,
+`Uncovered: 30 of 258`.
+
+**What this release does NOT reach.** Two populations are unreachable by any release code
+can touch. Every install that has not run the two-command update prints the OLD refusal
+copy, because a main commit is not live until released AND picked up. Every hand-registered
+Claude Desktop or Cowork connector lives in a config file that is not in any git repo.
+Neither is reachable by code; the soak window and the tester note (`docs/testers/outbox/
+2026-09-03-theo-cutover.md`) are the only levers that reach them.
+
+Also worth naming so nobody compresses it: decommission of the incumbent Brain waits for the
+soak window; the incumbent is SUSPENDED and never deleted; the two Render services are
+stopped compute-before-data (`pws-brain-mcp` then `pws-brain-db`); and the per-install
+`MINDRIAN_BRAIN_URL` rollback lever is valid ONLY while the incumbent still runs.
+
+## [2.0.0-beta.15] - 2026-08-28
+
+### Added
+- `scripts/verify-release` gains gate 10e (Phase 267.3, close-out): the whole-tree
+  `commands/*.md` `interactive_first_reward` audit (`node
+  scripts/check-reward-before-investment.cjs`, the CLI's full-audit default mode, no flag) is
+  now a fail-closed release gate, sited alongside gate 10d's registry audit. Proven against a
+  stripped-fixture A/B test before being wired (a `commands/` copy with one declaration
+  stripped exits 1, the real tree exits 0), matching the Phase 271-05 gate-proof discipline.
+  This closes the debt-ratchet gap `DEFERRED-271-D1` documented: a `--staged`-scoped commit
+  gate cannot measure a repo-wide declaration debt, which is how 67 of 113 commands went
+  undeclared for three months invisibly. The `--staged` commit gate itself is unchanged.
+  67 commands backfilled with a ruled `interactive_first_reward` declaration across this
+  phase (17 blocking Phase 271, plus 25 + 25 in the two backfill waves), and the
+  `data/first-reward-surfaces.json` registry (introduced earlier this phase) now declares
+  the first reward for 4 non-frontmatter surfaces inside `scripts/session-start`.
+
+## [2.0.0-beta.13] - 2026-08-28
+
+### Added
+- Memory and Context Operator MCP (Phase 270): three new atomic tools -- `context_assemble` (exposes the four-leg `getRoomContext` budget model with `estimate_only` cost preview before paying it), `graph_reason` (transitive support-closure and cross-room nearest-decision queries, both graph-native and previously unreachable by a flat directory walk), and `identity_write` (the first writer `~/.mindrian-user.md` has ever had). MCP Resources fixed to resolve the room per-session instead of once at boot (`room://state`), plus `mos://tree` and `mos://room/{slug}/tree` exposing the ICM forest live. **Honest tradeoff, not a win:** measured tool-schema token budget went **up** ~17% (36->39 tools, ~7,167->~8,377 approx tokens), not down -- the three new atomic tools cost more than the consolidation saved. Recorded as such, not spun.
+- `interactive_first_reward` vocabulary gains a ninth member, `live_deliverable` (Phase 267.3): a real, deployed, shareable artifact from an irreversible action (a live URL, a sent file) -- minted rather than forcing `/mos:publish`'s actual reward into an existing, incorrect term. A `data/first-reward-surfaces.json` registry now lets non-frontmatter surfaces (bash hooks, injected prose) declare a first-reward contract the linter can read; `scripts/session-start`'s four surfaces (FIRST_INSTALL, UPDATE, MODE_ROUTING, COLD_START_MENU) are now declared.
+- `/mos:doctor --check-rs-engine --fix` and direct auto-install: `scripts/compute-hsi.py` and `scripts/rs-engine.py` (the entry points for `/mos:act`, `/mos:mos-reason`, `/mos:find-bottlenecks`) now call the plugin's own already-shipped Python dependency auto-installer on missing imports, instead of hard-failing with a manual `pip install` instruction. Six sibling scripts already had this; these two did not.
+
+### Fixed
+- Reference-file citations are now anchored with `${CLAUDE_PLUGIN_ROOT}`, so the files a command actually needs load correctly from a real Data Room instead of only from the plugin dev repo. A bare `references/...` path resolves against your session's current working directory, not the plugin install directory, so these citations worked by pure coincidence in development (where the two happen to be the same folder) and silently failed for every installed user on all three surfaces. **134 of 134 measured sites now anchored** (103 commands/skills/agents/pipelines, plus the final 31 -- 16 methodology commands and `commands/doctor.md` -- unblocked by the `interactive_first_reward` vocabulary fix above and landed clean). Hand-authored skills use the fail-closed `${MINDRIAN_OS_ROOT:-${CLAUDE_PLUGIN_ROOT:?...}}` form, which refuses honestly instead of silently reading the wrong path when a foreign Agent-Skills host loads a skill with no plugin root set. `commands/radar.md`'s five sites are a reasoned exception (a genuine write into a git-tracked source of record, not a read -- anchoring it would redirect writes into the install cache every update wipes) -- allowlisted with a written reason, not silently skipped.
+- Added `scripts/check-plugin-path-anchoring.cjs` to the release gates (`scripts/verify-release`, gate 10c) so this class cannot silently return. A newly authored command, skill, agent, or pipeline file citing a bare plugin-relative path now fails the release gate before it can ship. `data/first-reward-surfaces.json` declarations are checked by a companion gate 10d.
+- Capability Radar Absorption + Routing (Phase 265, 23 plans): a full adversarial code review after all plans passed their own tests caught two real regressions no test suite caught -- `/mos:scout`'s competitor fan-out had Write + Brain access despite promising read-only (fixed by minting a genuinely read-only `agents/competitor-watch-fetcher.md`), and `/mos:vault` had a real human-gate bypass (a file-routing step re-invoked before, not after, the navigator's confirmation).
+- MCP layer correctness fixes (Phase 266): a per-call timeout budget that didn't hold in aggregate (60s vs a 30s host budget), caught by independent re-verification after the phase's own tests passed; fixed and re-measured (15.2s).
+
+### Known limitations, stated plainly
+- The other ~50 commands beyond the 17 fixed this release still lack an `interactive_first_reward` declaration (a repo-wide backfill, not yet started; no release gate currently requires full coverage, so this does not block shipping).
+- A code-review pass this cycle found 5 Critical correctness bugs in the local SQLite graph write chokepoint (`lib/core/navigation/edges.cjs`'s `writeEdge` silently discards some writes while reporting success; a schema mismatch fails writes from one of two database openers; the Brain-supplied edge-type allowlist is bypassed on one write path; the busy-timeout fix is applied at 1 of ~20 database openers; a locked room can misreport as having no database at all) -- found and registered as its own phase, **not fixed in this release**. Full detail: `.planning/ROADMAP.md` Phase 273.
+- Phase 134's original objective (eliminating the Python dependency for HSI/reverse-salient analysis entirely) was tracked as complete but was never actually implemented -- the auto-install fix above is a mitigation, not the real fix. Registered as Phase 272, not done here.
+
+## [2.0.0-beta.11] - 2026-08-24
+
+### Added
+- 
+
+### Fixed
+- `/mos:organize`'s D-09 soft-alias redirected to `/mos:rooms organize`, a subcommand that never existed -- an unmatched subcommand silently fell through to `list`'s default behavior instead of failing honestly. `commands/rooms.md` now defines `organize` as a real subcommand that reports "not yet implemented" (tracked as `organize-soft-alias-redirects-to-nonexistent-target`) instead of masking the gap, and any other unrecognized `/mos:rooms` subcommand now gets the standard 3-line error instead of a silent `list` fallback. The `room_content` MCP tool's `command` schema also advertised `organize` as a valid enum value with no matching dispatcher case, so any programmatic caller got a runtime `Unknown room_content command: organize` instead of a validation-time rejection; `organize` is removed from that enum until a real handler exists.
+
+## [2.0.0-beta.9] - 2026-08-23
+
+### Added
+- Roadmap-Type Selector (Phase 264): a navigator's stated research goal is silently classified into one of six scientific-roadmapping output shapes (Landscape Analysis, Technical Roadmap, Pipeline Analysis, Opportunity Analysis, Agenda-Setting Manifesto, Vision Paper) and resolved to the matching framework-name chain via the existing chain_resolve seam. New sensor SENS-18 (`lib/core/sensors/sensor-roadmap-type.cjs`), a deterministic additive-score classifier following `dual-path-detector.cjs`'s template, registered across the 3-array sensor lockstep. New `data/roadmap-type-chains.json` chain table with a five-arm drift validator mirroring the existing `dispatch-framework-map.json` precedent.
+- Challenge-driven execution proof: `find-bottlenecks` (Reverse Salient) now demonstrably runs under the already-shipped `ralph_verify` bounded self-critique seam with a new synchronous, two-pass adversarial critic (`lib/core/salient-governance.cjs`), reusing `eureka-critic.cjs`'s already-ruled 2-judge-unanimous pattern rather than an N-judge panel. Proven via a direct `chainExecutor.runChain()` call (mirroring the existing `debate-composition.cjs` precedent), including a live mutation proof that flipping a gate-condition function makes the test suite go red.
+- `chain-executor.cjs`'s B3/Canon Part 3 stop-condition contract (the chain halts at the first material step, never an autonomous cross-step loop) is now pinned by a scoped sha256 hash over its six gate/stop-condition symbols plus a whole-file zero-diff check, so a future accidental edit there is caught immediately rather than discovered later.
+
+### Known limitations
+- The live `chain_resolve`/`chain_run` MCP path does not yet honor `ralph_verify` -- its async execution branch neither calls the retry seam nor passes a `selfCritiqueFn`. The challenge-driven proof above runs via a direct executor call, not the navigator-facing chain flow. Wiring the live path is a named follow-on, not done in this release.
+- The classifier and chain table are proven-composable (integration-tested end to end) but have no wired UI/reach-card surface yet.
+
+## [2.0.0-beta.7] - 2026-08-19
+
+### Added
+- The dual-graph loop, closed (the "Build the Loop" milestone promise): local sensors supply WHEN, the Brain supplies WHICH and IN WHAT SEQUENCE, a human gate sits between. recommendChain wrapper on the one governed Brain wire (frozen v1 contract, Brain repo docs/RECOMMEND-CHAIN-CONTRACT.md); the brain_framework_chain companion finally has a consumer + chain adapter in chain-recommender (alias normalization, command-map divergence logged as typed memory events, posture authority stays LOCAL); chain offers surface on suggest_next for hookless surfaces (260819-c8j)
+- Hookless-surface runtime protocol served as MCP `instructions` at initialize, plus Desktop prompt-menu entries bind-room / status / act - Desktop and Cowork run the same Larry loop CLI hooks enforce (2026-08-18/19 night session)
+- Doctor class-M layer 6 `store_identity`: resolved endpoint, node-count floor 29,000, the number 28,325 recognized BY NAME as the stale-replica signature, optional GraphRagMeta stamp read (260819-c9b)
+- Dual-graph health gate live reader wired (M4 predicate rewritten to fit the server's 5s read budget, 5031ms to 688ms) and the first conclusive live baseline recorded (260819-c9b)
+- Part 8 in-process egress belt at the callTool chokepoint - free-form payload classification now covers every Brain wrapper, not 4 of 16 (260819-c8j)
+
+### Fixed
+- MCP write path enabled on the Claude Code host: graph_write / memory_event / artifact_file (the governed navigation.cjs door) no longer refuse and provoke ungoverned direct-disk filing fallbacks (260819-bql, RCA option A)
+- One resume owner for material_step gates: gate_answer now executes the halted step through the ledger entry's own resume handle; the documented ratify-then-resume flow no longer dies on the single-use ledger, and no interleaving can double-run a material step (260819-c55)
+- Part 8 hook matcher extended to the pws-brain-mcp server naming - the egress guard and response sanitizer no longer no-op on live Brain calls
+- Phase 234-01 instructions pin evolved from absence to byte-identity: the initialize channel serves exactly RUNTIME_INSTRUCTIONS, moat-vocabulary canaries asserted absent
+
+### Changed
+- Every live surface (setup templates, brain-setup docs, THE-BRAIN, WORKFLOWS, CANON glossary, session-start banner, .env.brain.template) points at the canon store pws-brain-mcp.onrender.com; Aura-era references marked RETIRED do-not-build-against; the stale replica is suspended Brain-side and answers 503
+
+## [2.0.0-beta.5] - 2026-08-11
+
+### Added
+- 
+
 ## [2.0.0-beta.3] - 2026-08-11
 
 ### Added