@mindrian_os/cli 1.14.0-beta.3 → 1.14.0-beta.7

package/CHANGELOG.md

@@ -1,3 +1,33 @@
+## [1.14.0-beta.7] - 2026-06-23
+
+The v1.14.0-beta train continues: the deck surface consolidates onto one born-wired front door (Phase 175) and Scenario Planning is wired into its canon chain (Phase 176), on top of the beta.5 payload (Canon Part 11 / CIRS, ACE/diffusion, methodology-ingest, /mos:show).
+
+### Added
+- **Phase 175 -- /mos:deck, the consolidated deck command.** One born-wired front door (`commands/deck.md`) for investor-grade deck generation, replacing the scattered deck surfaces. The legacy `MOSDeckEngine` and `feynman-engine` handles are aliased to `/mos:deck` (`data/deck-aliases.json`, doctrine + data) so existing invocations route to the new style selector instead of a dead path. Three deck styles (Feynman first-principles, HEART narrative, mesh), each built per-section through a Shape F.1 accept/reshape/skip gate rather than auto-advancing. Deck style + section-schema source of truth lives in `data/deck-styles.json`; the `make-land` lane is repointed to `/mos:deck`. Born-wired per Canon Part 11 (CIRS R1/R2): the command is WIRED with a `connector:` block and passes the hard coverage gate. A WARN-first deck-design ruleset (`lib/core/deck-design-rules.cjs` pure helpers + `scripts/check-deck-design.cjs` `--check` CLI) lints a deck against the design rules and warns without blocking. Behavior suite `tests/test-deck-consolidation.cjs` + `tests/test-deck-design-check.cjs`; phase gate `tests/run-all-175.sh` 20/20.
+- **Phase 176 -- Scenario Planning wired into its canon chain.** Three curated FEEDS_INTO chain edges (bare framework names, on the orchestration projection per Canon Part 11 R6): `Domain Selection -> Scenario Planning` (0.68, the F.1 next step after `/mos:explore-domains`), `PEST Analysis -> Scenario Planning` (0.60, the STEEP feeder), and `Scenario Planning -> Futures Wheel` (0.66, the cascade out to `/mos:futures`). The `/mos:scenario-plan` command body and `references/methodology/scenario-plan.md` are reconciled to the canonical 10-step arc (Define Domain -> STEEP -> independent critical uncertainties -> 2x2 -> PARTS-tested narratives -> identify opportunities -> cross-scenario -> prioritize + bank to the Opportunity Bank -> robust strategies -> iterate) with a dual-name note. Additive only: no reach, edge type, or node type minted, and no Brain wire opened; both coverage `--check` ledgers stay gap=0. Phase gate `tests/run-all-176.sh` 5/5.
+
+### Fixed
+- **data-ai image provenance.** `checkImageProvenance` hardened to flag bare-boolean `data-ai` image markers that previously slipped through provenance verification.
+
+## [1.14.0-beta.5] - 2026-06-23
+
+The v1.14.0-beta train: Canon Part 11 (the Invocation Constitution) ratified and shipped as a born-wired hard coverage gate, the four-class governance-ISA (canon v1.15), /mos:act made governed + always-on + intent-calibrated, cross-class command-to-pipeline-to-framework chaining, the rs-* family + presentation surfaces wired, Phases 170 (ACE/diffusion) + 171 (methodology-ingest) reconciled to CIRS-conformance, and Phase 173 (the /mos:show JTBD need-selector front door).
+
+### Added
+- **Canon Part 11 -- The Invocation Constitution (CIRS R1-R14), born-wired as a hard coverage gate (Phase 172).** The invocation/reachability layer is now a constitutional Part, peer to Part 8 (Boundary) and Part 9 (Memory): every invocable surface (command, skill, agent) is in exactly one of two states, WIRED (`connector:` block) or EXCLUDED (`connector:{excluded,reason}`), and a new or modified surface fails the gate CLOSED unless it satisfies R1. Coverage is a lifecycle invariant enforced at every merge, not a number checked once. The born-wired gate is wired into pre-commit + install-pre-commit + release.sh (Step 2.4) + doctor --acceptance. Both coverage ledgers report gap=0 (89 wired / 36 excluded / 0 gap on the connector registry; projection gap=0). The recurring 143.x / 144.1 dark-surface regression now has a structural cure.
+- **Phase 173 -- /mos:show JTBD need-selector front door.** A Shape F.1 publish-needs selector (`data/publish-needs.json` + a `--check` validator + a role_blend-to-lane mapper) plus the SENS-SHOW show/share trigger sensor (`lib/core/sensors/sensor-show-share.cjs`, R4) registered in dispatchSensors, with the orchestration projection + connector registry + harness manifest regenerated in lockstep (R5). End-to-end R1-R7 flow test green; run-all-173 7/7.
+- **Phase 170 -- Adoption-Capacity Engine (ACE) + dual-use diffusion trigger (`/mos:diffusion`).** Canonized Horowitz's adoption-capacity theory into the Brain (Neo4j + Pinecone) as a first-class methodology: variables (financial intensity, organizational capital, conceptual capacity), 7 cases incl. 3 dual-use worked examples, the 2x2 typology, 7-step pipeline, 5-path response, academic critiques, and the FEEDS_INTO chain (S-Curve / Reverse Salient / PEST / Macro Trends / Sustaining-vs-Disruptive INTO ACE; ACE INTO Scenario Planning / Mullins / Triple Validation Compass / Ansoff / Now-New-Next / Self-Selling Loop). Also deepened the Hooked Model and minted the Self-Selling Loop (mindrian-operation tier). New `SENS-09` dual-use diffusion sensor (`lib/core/sensors/sensor-diffusion-adoption.cjs`, frozen `brain_consult` reach; keyword + marker + signal modes) surfaces ACE proactively on defence/navy/drone/dual-use turns; `/mos:diffusion` is the explicit front door. `brain_search` retrieval verified. Additive only (no frozen-set move; no canon amendment). Test 20/20 + regression fences green.
+- **Phase 171 -- reusable methodology-ingest pipeline (`/mos:ingest-methodology`).** Codifies the 7-step "add a methodology to the Brain" process so every future framework follows the same safe path: encode -> Canon Part-8 boundary gate (hard halt) -> graph write -> vector write -> trigger + chain -> register -> local refresh. Engine `lib/core/methodology-ingest.cjs` (pure: `auditSpecPart8` gate, parameterized `buildFrameworkCypher`, `buildPineconeRecords`, `ingestPlan`) test 19/19; local step `scripts/methodology-ingest-local.sh` regenerates command-registry -> connector-registry -> brain-orchestration-projection (the local intelligence cache the navigation engine / dial / ranker read), each behind its `--check` drift gate, so a Brain-written framework is operable Local-Only with no live Brain call.
+
+### Changed
+- **Canon advanced to v1.15.** Part 11 R1's unit-of-coverage now enumerates the four governed surface classes -- mechanical (a non-framework command/operation), framework (a pws methodology), intelligence (an engine/sensor/analysis surface), and pipeline (a chain/workflow) -- as the invocation governance ISA; the gate is class-aware. The `coverageReport()` `class` enum is purely additive metadata (wired/excluded/gap counts unchanged). Appendix D entry 26 records the amendment; mints no new edge/node/reach type and opens no Brain wire.
+- **/mos:act is now governed, always-on, and intent-calibrated**, resolving through the one governed path (dispatchSensors -> decide() -> resolver) rather than a second selection brain. Cross-class command-to-pipeline-to-framework chaining now resolves through the same spine.
+- **The rs-* family and the presentation surfaces are wired** into the connector spine (CIRS R1), closing the largest dark-surface band; every thinking-surface gap is now WIRED or explicitly EXCLUDED-with-reason.
+- **Phases 170 + 171 are no longer release-held.** Both were CIRS-conformance targets gated before release; Phase 172 Plan 12 reconciled them to conformance, so they ship in this beta.
+
+### Fixed
+- **The CIRS coverage gate flipped from WARN to hard-FAIL.** `build-connector-registry.cjs --check` and `build-orchestration-projection.cjs --check` now exit non-zero on any surface neither WIRED nor EXCLUDED (and any command counterpart neither ranked nor excluded). A command counterpart EXCLUDED at the connector layer now propagates to EXCLUDED in the projection, so the two ledgers stay reconciled at gap=0. The flip landed after the baseline was wired/excluded, so CI never went RED mid-sweep.
+
 ## [1.14.0-beta.3] - 2026-06-19
 
 ### Added

package/package.json

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