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

package/CHANGELOG.md

@@ -1,3 +1,57 @@
+## [1.15.3-beta.22] - 2026-07-16
+
+### Added
+- 
+
+## [1.15.3-beta.20] - 2026-07-16
+
+### Added
+- **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
+  already depends on. The existing LLM classifier is demoted to an escalation-only path,
+  called per artifact only for the genuinely ambiguous residual the embedding tier cannot
+  confidently place. Measured on a real room: 61.1% of candidates resolve locally and
+  correctly, 14.3% fewer artifact-level LLM calls. Honest degrade throughout: no LLM key
+  means a disclosed low-confidence embedding best-guess, never a silent default; `classifier_source`
+  now reports `embedding` / `model` / `mixed` / `fallback` so every result states which tier
+  produced it. Tunable via `MINDRIAN_WHATWHY_MARGIN` (default 0.10, calibrated against a
+  measured holdout set). (Quick task 260714-k44.)
+
+### Fixed
+- **A low-confidence WHY term is no longer structurally indistinguishable from a confident one.**
+  When Eureka's two-tier classifier places a candidate as a framework (WHY) term but has no
+  working LLM to confirm the low-margin embedding best-guess, the term lands in the artifact's
+  `framework_terms` prop. The only trace that the guess was low-confidence lived in the aggregate
+  `status.json` counter (`tier2_low_confidence`); once written onto the node, the guess looked
+  exactly like a confidently-resolved term. Each term that lands via the no-LLM degrade path is
+  now disclosed per-term in an additive `framework_terms_low_confidence` sibling prop (always a
+  subset of `framework_terms`); a confident later run removes the marker; and existing readers of
+  `framework_terms`, which stays a plain comma-joined scalar, are unaffected. The 219 metadata
+  test now pins the disclosure so it cannot silently disappear. Caught live by the run-all-221
+  regression chain. (Quick task 260715-cu8.)
+- **Eureka's ranked top-25 no longer refills with scaffold pairs when real entities are thin.**
+  Every room stores one `memory_artifact` node per file as document scaffolding. When a room's
+  real-entity cohort is thin, those scaffolding nodes were pairing with each other and flooding
+  the ranked top-25 with `memory_artifact`-vs-`memory_artifact` pairs that carry no cross-domain
+  signal (measured at 72.0 percent of the top-25 on a live room once entity extraction correctly
+  thinned the entity population). Scaffold-vs-scaffold pairs are now excluded from the ranked-pair
+  candidate set by construction, at the point the candidate list is built, so the structural share
+  drops to 0.0 percent on the same live substrate regardless of how sparse the real entities are.
+  The exclusions are counted honestly in the report provenance (`scaffold_pairs_excluded`, in both
+  the JSON and the markdown table), never silently dropped. Pairs with only ONE scaffolding side
+  are unaffected, so a real entity paired with the artifact it came from still ranks. (Quick task
+  260715-0nj.)
+- **Eureka's entity-extraction pre-step no longer fails silently.** `/mos:eureka run`'s
+  auto-extraction step (shipped in beta.18) could fail (a thrown error, or the more likely
+  internally-caught non-zero return) with zero visible trace: exit 0, status `done`, nothing
+  in the report to say extraction never actually populated the graph. This reproduced the
+  exact false-success shape found in a live intern QA session. Failures on both paths now
+  surface as an additive `extraction_error` field in the eureka status.json plus one stderr
+  line; ranking, fallback behavior, and exit codes are unchanged (the degrade-never-throw
+  contract stays intact, only the silence is gone). Proven via a RED-then-GREEN reproduction
+  test wired into the permanent suite. (Quick task 260714-jjm.)
+
 ## [1.15.3-beta.18] - 2026-07-13
 
 ### Added

package/package.json

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