@mindrian_os/cli 1.15.3-beta.24 → 1.15.3-beta.28

package/CHANGELOG.md

@@ -1,16 +1,205 @@
+## [1.15.3-beta.28] - 2026-07-18
+
+### Added
+
+- **Eureka: killed two distinct causes of unusable portfolio-scan output, plus a warm-cache
+  MCP path.** Live-verified on two independently-chosen real rooms
+  (`aion-eureka-synergy`, `iia-deeptech-centers`), not just fixture-green.
+
+  - **Seam 2 (statement-metadata gap, RESOLVED).** Every entity-entity Opportunity Statement
+    was rendering the literal placeholder text "unknown x unknown approach to a unknown x
+    unknown cross-domain bridge" instead of a real mechanism. Root cause: Phase 218 wired
+    entity nodes (company/technology/market) into the 215 opportunity-statement pipeline but
+    patched only the `title` slot for that node class, leaving `section`/`primary_problem`/
+    `problems`/`shared_problems` falling through to content-node defaults entity nodes
+    structurally can't satisfy. Fixed in `lib/core/eureka/room-native-substrate.cjs`: the
+    entity-node branch now inherits `section` from its already-shipped `DESCRIBES` edge to its
+    source memory_artifact (55/56 entities have one; pure composition over an existing edge,
+    sibling of the prior title fix), with an `entityType` fallback for the remainder, plus a
+    relation-edge-typed bridge label (`competes-with`/`uses-component`/`supplies-to`) in
+    `scripts/eureka-portfolio-report.cjs` instead of the generic phrase. 22/25 -> 0/25
+    "unknown x unknown" statements on both proving rooms.
+  - **Seam 3 (candidate-generation gap, RESOLVED).** Real content was getting ranked against
+    its own containing section (`problem-definition` x `problem-definition`) because `Section`
+    container nodes -- the room's own top-level folder nodes -- were admitted as pairing
+    candidates. The critic already had a correctly-firing rejection tag for this
+    (`domain_swap_invariant`) but nothing upstream excluded these pairs before they consumed
+    ranked-list slots. Fixed with an additive either-endpoint `Section` exclusion at the same
+    generation-layer insertion point the 260715-0nj scaffold-pair fix established (Reuse
+    Before Build), with an honest `container_pairs_excluded` counter surfaced in provenance.
+    1,575 degenerate pairs (9.8% of the candidate set) excluded on `iia-deeptech-centers`;
+    proven a true no-op on `aion-eureka-synergy` (0 Section nodes there) by output diff, not
+    by assertion.
+  - **New: `eureka-run`/`eureka-status`/`eureka-report` on the `intelligence` MCP router
+    tool.** Calls the same governed dispatcher (`scripts/eureka-command.cjs` `main(argv)`)
+    in-process instead of spawning a fresh child process per call, so
+    `embedding-spine.cjs`'s existing module-level encoder cache stays warm across scans on
+    the Phase 198 resident daemon (spiked: same-process call 2 is 0ms vs. call 1's 179ms,
+    unmodified cache mechanism). Transport-gated per call: in-process on the http resident
+    daemon; detached child on stdio, since `process.stdout` is the JSON-RPC framing channel
+    there and the scan writes progress to stdout. Registered on the `intelligence` tool's
+    enum only, outside the 65-command CLI/MCP parity array (mirrors the `eureka_critic`
+    precedent). `/mos:eureka`'s CLI behavior and output contract are unchanged (verified
+    byte-identical).
+
+  Flagged, deliberately out of scope for this pass: Seam 1 (entity-extraction noise --
+  generic-noun and near-duplicate entities still reach the ranker on `aion-eureka-synergy`,
+  tracked separately) and a newly-observed WhitespaceZone-dominated pairing pattern on
+  `iia-deeptech-centers` (AHP composite doesn't differentiate a room where ~87% of nodes are
+  whitespace hypotheses) -- both real, both future work, neither papered over.
+
+- **Phase 230: MindrianOS Skill Fleet Optimization -- the harness for testing whether
+  MindrianOS's own 124 skills trigger correctly and stay quiet when they shouldn't.**
+  Two workstreams. WS1 (trigger-accuracy, all 124 skills): per-family eval-query generation
+  exploiting sibling near-misses, a roster-wide judge funnel (one call scores a query against
+  all 124 skill descriptions at once, catching competitive collisions isolated per-skill
+  grading structurally cannot see), flagged skills escalate to a real live trigger-test loop
+  with train/validation-gated description revision. WS2 (code-quality, the ~59 script/
+  workflow-backed skills -- the design estimated ~10-20, the real inventory came in ~3x
+  higher, disclosed rather than silently re-scoped): adversarially-verified review
+  (Refute-or-Promote) with a deterministic evidence-quote anchor so a fabricated finding
+  cannot reach the report. Live-smoke-tested end to end on a 13-skill human-approved
+  calibration set (`scripts/skillopt-*.cjs`, `lib/core/skillopt-schemas.cjs`,
+  `tests/run-all-230.sh`, 9 deterministic legs): the real Skill-fire detector proved correct
+  in both directions on fresh live captures (it turned out MindrianOS's own `mos:` skills
+  fire via an MCP tool call, not Claude Code's native Skill tool -- caught before anything
+  was built on the wrong assumption), and WS2 independently re-discovered the real
+  `check-card-fire.cjs` over-enforcement defect (see Fixed, below) with zero false positive
+  on a known-clean control. The smoke calibration gate itself came in under tolerance (30%
+  agreement vs. an 85% bar) -- accepted as informative, not blocking, since most of the gap
+  is real full-roster collisions a human's isolated pre-labels couldn't see plus one disclosed
+  query-labeling bug; the reconciliation (fix the labeling bug, re-run smoke) is tracked as
+  SEED-061, not silently dropped. **The full 124-skill fleet run and any multi-agent
+  Workflow-tool orchestration are explicitly deferred behind a future opt-in -- this release
+  ships the harness, not a fleet run.** Nothing was ever written to a real `SKILL.md` or
+  script; every proposed change surfaces in a human-approved report only.
+
+### Fixed
+
+- **`check-card-fire.cjs` no longer force-fires the Decision-Gate card on plain prose with no
+  actual gate.** Two independent over-fire mechanisms, logged three times across 12 days
+  (2026-07-05, 2026-07-11, 2026-07-17) before being root-caused against a live 17-record
+  intercept-log replay: (1) the backstop's bare numbered-prose detector had a 7/7
+  false-positive rate in the logged evidence and zero true catches -- retired outright,
+  genuine ASCII-box degrades stay caught by the separate bracket-arm detector, unchanged;
+  (2) the primary registry-gated path fired on `ran_entries` alone, which a side-channel
+  session-key/TTL union bled into every turn for roughly 10 minutes regardless of relevance
+  -- now requires a confirmed, non-empty gate-subject plus relevance against that real
+  subject. Verified against all 7 real logged firings (0/7 re-fire) plus the full
+  card-fire-specific suite (11/11 + 27 assertions). Trade-off, disclosed not hidden: a lone
+  genuine numbered-prose fork no longer force-fires at the hook level and now depends on the
+  model's own Phase-210/SEED-021 judgment -- the same trust boundary the existing
+  under-firing watch (`feedback_false_success_silent_skip_gates_academy_testers.md`) already
+  tracks from the opposite direction.
+- **Per-session room binding no longer re-prompts every turn after a real bind.** The MCP
+  `room_bind` tool wrote the session's binding state keyed by the actual Claude session UUID;
+  the CLI `UserPromptSubmit` hook read it keyed by `process.env.CLAUDE_SESSION_ID`, which is
+  unset in that hook's execution context, so it silently fell back to a
+  `sha256(roomDir+day)` hash key that never matched -- confirmed with an exact hash-vs-
+  on-disk-filename proof, not inferred. The hook now reads the real session id from its own
+  stdin payload first. This also un-breaks Phase 225's zero-score gate (SEED-039), which
+  shared the same key-mismatch root and was never separately regressed -- just never covered.
+- **The reach/navigation dial no longer offers a topically-unrelated room or claim with no
+  relevance check.** `cross_room` was a permanent member of the reach candidate bank, always
+  offered in a cold room's top-3 regardless of what the live conversation was actually about,
+  filtered only by advisory instruction text the model had to apply itself. A structural
+  relevance gate (`lib/hmi/reach-relevance-gate.cjs`) now suppresses off-topic candidates by
+  token overlap against the live turn before they're ever offered; `cross_room` also no
+  longer "borrows from itself" (filling its own room-name slot with the current room).
+
+## [1.15.3-beta.26] - 2026-07-16
+
+### Added
+- **Phase 227: Ignite / mode-select timing across turns 1-4 (SEED-060).** The session-start
+  mode-selection Decision Gate (Just Talk / Explore+Capture / Build a Room) gets a structural,
+  advisory-only backstop: a new `doctor.cjs` check class (`lib/core/mode-select-sidechannel.cjs`
+  + `lib/core/doctor/mode-select-checkpoint-module.cjs`) detects a silent skip (the gate neither
+  firing a card nor stating a default) and warns, never blocks, never re-fires the gate itself.
+  A systemic sweep of methodology skills for the same loose-description auto-fire bypass that
+  let `trending-to-absurd` reach for itself on a casual remark before its 2026-06-24 fix found
+  and closed 3 trivial instances inline (`MOSDeckEngine`, `client-discovery-interview`,
+  `mullins-scaffold`), with the rest reported and explicitly deferred. A scripted regression
+  test (`tests/test-227-frontdoor-restraint.cjs`) now proves the front-door restraint fix holds
+  without needing a live human tester re-run. `skills/larry-personality/SKILL.md` names ignite
+  for the first time and documents the gate's timing with real Hooked-Model (Fogg B=MAP / TARI)
+  reasoning: the gate is a Prompt, not an Investment, fired only when the navigator's opener
+  does not already signal a lane. `conversation-mode`'s Mode 3 (Build a Room) now routes through
+  ignite's Directive/`--express` path instead of calling `/mos:new-project` directly, correctly
+  reserving Gate B1's four-door persona pick for sessions that genuinely have not yet
+  established a role or venture. Same-day code review (independently re-verified, not
+  self-certified) caught and fixed two real defects before this landed: Mode 3's routing text
+  originally claimed established context unconditionally even on a cold direct pick with zero
+  prior exchange, and the mode-select "card-fired" recorder was wired against text no live code
+  path actually renders through `pickShape()`. Both closed at the design level in this same
+  pass (independently re-verified: 8/8 + 4/4 tests pass, both diffs re-read after landing),
+  not patched around the symptom.
+
+- **Phase 229: HUJI Pitch Feedback Module (IN PROGRESS, 8/9 plans -- not yet shipped).**
+  MindrianOS's first paying job: turn each student's diarized 5-minute pitch transcript into
+  one Minto-structured formative feedback artifact, batch-orchestrated across 200+ submissions
+  at a $4-5/unit cost ceiling, local-only scoring (Brain read-only, generic handles per Canon
+  Part 8). Built so far: the evidence/feedback zod schemas plus generated JSON Schema
+  (`229-01`); a labeled test-inventory harness and `run-all-229.sh` aggregator (`229-02`);
+  deterministic code checks covering quote verification, recall, drift, schema validation,
+  similarity, cost, and Part-8 hygiene (`229-03`); the `PWS_grading` recipe with a
+  score-and-continue rubric (`229-04`); a Stage A intake adapter porting the Claims-Aware
+  Fusion Mode A pipeline (`229-05`); an LLM judge spawner with a calibration protocol that
+  fails closed below a 0.7 anchor-hygiene bar (`229-06`); and a single-submission runner plus
+  batch orchestrator with pool/ledger/resume/retry and G1-G6 per-unit guardrails (`229-07`,
+  `229-08`). Not yet shipped: `229-09`, the mandatory demo run and human verdict checkpoint
+  this whole pipeline is gated on before any real submission gets scored -- per this project's
+  own standing rule, judge accuracy and calibration are a human-verify bar, never
+  self-certified.
+
 ## [1.15.3-beta.24] - 2026-07-16
 
 ### Added
-- 
+- No discrete feature completed exactly at this tag. This pre-release snapshot captured
+  in-progress work on Phase 227 (the mode-select firing checkpoint, sweep, and Mode 3 routing
+  work) and Phase 229 (the HUJI Pitch Feedback Module's Stage A intake adapter) mid-flight,
+  neither phase-complete at cut time. Phase 227's full, finished feature set is recorded once
+  under `[Unreleased]` above rather than split and duplicated across the interim tags it
+  happened to span.
 
 ## [1.15.3-beta.22] - 2026-07-16
 
 ### Added
-- 
+- No discrete feature completed exactly at this tag either, for the same reason as beta.24:
+  a pre-release snapshot mid-flight through Phase 227 (the skill-description sweep landed
+  here) and Phase 229 (PWS_grading recipe + score-and-continue rubric work).
 
 ## [1.15.3-beta.20] - 2026-07-16
 
 ### Added
+- **Backfilled here (this changelog under-documented this tag at cut time): five phases that
+  actually shipped in this release window.**
+  - **Phase 222 (reach-ranking-unification).** The three surfaces that suggest a next move
+    (`/mos:suggest-next`, the reach-candidates list, and the auto-fire engine) now always
+    agree on the top pick instead of occasionally diverging, and the ranking improves over
+    a room's own accept/reject history rather than staying static.
+  - **Phase 223 (jtbd-driven-intelligence-pipeline, governed bono).** `/mos:bono` is now an
+    8-phase governed research debate with Six-Thinking-Hats-style scrutiny (the Black hat
+    must disconfirm first, the White hat must cite-or-retract) and three explicit navigator
+    approval pauses (topic, hypothesis, ruling) instead of one collapsed confirmation. New
+    `/mos:intel-pipeline` command runs a staged research pipeline oriented on the room's
+    active JTBD (calibrate -> decompose -> fan out -> compute -> synthesize -> close), pausing
+    for approval twice and disclosing a thin fan-out pass rather than silently proceeding.
+  - **Phase 224 (graph-derivation-harness, SEED-034).** Every markdown write to a room now
+    enqueues and background-derives typed graph edges, closing the previously twice-reconfirmed
+    0-typed-edge gap on the write path -- no manual "derive" step required.
+  - **Phase 225 (per-session-room-binding, SEED-039).** Session-to-room binding now correctly
+    supports multi-room binds. Fixed during code review: a binding answer was silently
+    collapsing a multi-room selection down to a single room regardless of what was picked.
+  - **Phase 226 (eureka-reasoning-mode-fallback, SEED-058).** When the local embedding encoder
+    is unavailable, `/mos:eureka` now degrades to a labeled, lower-confidence REASONING MODE
+    result (a real short ranked list with an honest caveat naming the degrade cause) instead of
+    a hard `pairs_scored: 0` dead end. `banked` is structurally `false` on every reasoning-mode
+    row; a later healthy re-run over the same room surfaces the reasoning-to-embedded delta
+    instead of silently replacing the earlier result. Same-day code review found and fixed
+    three real data-loss edge cases in the upgrade-delta path before this shipped (a repeated
+    degrade could silently overwrite a completed reasoning report with no trace; a stale
+    session file could let a later healthy run get clobbered; reseeding could silently orphan
+    an in-progress judging session).
 - **Eureka entity extraction gets a two-tier WHAT-vs-WHY classifier.** A free, fully local
   embedding pass (`lib/core/eureka/embedding-classifier.cjs`) now resolves the confident
   majority of candidates at zero API spend, reusing the same encoder Eureka's own ranking

package/README.md

@@ -10,7 +10,7 @@
   Powered by PWS (Problems Worth Solving), an innovation methodology built and tested through 20 years of teaching by Prof. Lawrence Aronhime.
   Engineered by Jonathan Sagir.
 
-  [![Version](https://img.shields.io/badge/version-1.15.1--beta.1-1E3A6E)](CHANGELOG.md)
+  [![Version](https://img.shields.io/badge/version-1.15.3--beta.26-1E3A6E)](CHANGELOG.md)
   [![License](https://img.shields.io/badge/license-BSL_1.1-C8A43C)](LICENSE)
   [![Works on](https://img.shields.io/badge/CLI_+_Desktop_+_Cowork-2D6B4A)](#three-surfaces)
 
@@ -128,7 +128,7 @@ The commands below are internals. You never have to memorize them or type them.
 /mos:grade                # honest assessment against real ventures
 ```
 
-That is a slice of 110 commands across 14 skills and 9 agents. If you do not know which one to run, that is the normal case. Just talk: Larry reaches for the right one.
+That is a slice of 111 commands across 124 skills and 9 agents. If you do not know which one to run, that is the normal case. Just talk: Larry reaches for the right one.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindrian_os/cli",
-  "version": "1.15.3-beta.24",
+  "version": "1.15.3-beta.28",
   "description": "Install MindrianOS into Claude Code with one command -- `npx @mindrian_os/cli`. Ships the MindrianOS plugin (Larry + PWS methodology + Data Room) plus a setup/diagnostics CLI (install/doctor/update).",
   "scripts": {
     "mcp": "node bin/mindrian-mcp-server.cjs",