@mindrian_os/cli 1.15.3-beta.22 → 1.15.3-beta.26

package/CHANGELOG.md

@@ -1,11 +1,96 @@
+## [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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindrian_os/cli",
-  "version": "1.15.3-beta.22",
+  "version": "1.15.3-beta.26",
   "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",