@nexus-cortex/cli 4.107.2 → 4.108.0

package/.env.defaults

@@ -282,6 +282,7 @@ CORTEX_EFFORT_TAIL=false
 #   ⇒ the flash-low verdict was low-vs-HIGH (not low-vs-medium): ~30% cheaper at pass-rate WASH.
 #   Applies to the ACTION model here; the mentor roles run 'max' (top), the helper middleware runs 'none'.
 # [LEDGER 2026-09-11 @4.107.0] cell-n-r4 (hard core 13×K=2, flash action model, FINAL 47/52 rows): high = NO LIFT — ah-none 6/22 (0.27), ah-low 7/25 (0.28) vs control 11/26 (0.42); +3.5–4.5 min/task latency, turns unchanged (narrow door intact). Keep unset (card default). DARK. Ledger r-cell-n-r34.
+# [LEDGER 2026-09-12 @4.107.2] PRO @high on the k=5 series COMMON (tb21-k5-ph1, full 89, K=1): 72/89 = 80.9% (Wilson 0.72-0.88), $12.77, med 737 s — +3-4 pts over the flash series (77.3 ± 2.7), CIs overlap; effort NOT separated from model (pro @default not yet run). Flash @high = no lift (cell-n-r4). Stays DARK. Ledger .cortex/bench/r-tb21-k5-ph1-2026-09-12.md
 #CORTEX_ACTION_EFFORT=
 # Trigger helper-model review on tool errors (only applies when mentorship is enabled)
 MENTORSHIP_TRIGGER_ON_ERROR=false
@@ -375,6 +376,7 @@ MENTORSHIP_HELPER_MODEL=deepseek-flash
 #   4.107.0, PAIRED 6 losses / 1 gain, fewer turns on 12/18 tasks (finishes earlier, less verification: gcode read "gcodo3"
 #   without the control's max-zoom check). Shipped together with EndTurn essential, so attribution needs the 2×2 (cell-n-r6:
 #   base / et-ess / doc-v2 / et-doc). Default v1 = measured baseline until the 2×2 decides.
+# [LEDGER 2026-09-11 @4.107.2] cell-n-r6 2×2: v2 8/26 vs v1 7/26 (standard tier), 7/26 vs 11/26 (essential tier); main effect 15/52 vs 18/52. Neutral to negative → v1 stays default; the doctrine-mine candidates (r5 §7) queue as a v3 arm. DARK.
 #CORTEX_LIFT_PLAN_DOCTRINE=
 # [LEDGER 2026-09-11 @4.107.0] cell-n-r1 arm fh-plan (LIFT_PLAN_REASONING=on @high + resolver none): 7/25 vs control 10/24 — the thinking-on planner did not help on the hard core. DARK.
 #CORTEX_ENDTURN_RESOLVER_REASONING=
@@ -719,13 +721,26 @@ ROUTER_MIN_SAMPLES=3
 # [LEDGER 2026-09-03 @4.91.0] DARK/PENDING → **RECOMMENDED ON for k=5 (with REQUIREMENTS=strict)** — 4.91.0: gates now run on the STREAMING path too (were sendMessage-only; one shared endTurnGates.ts, live-proven on stream:true) and Stage-2 grounding accepts text the model WROTE this turn (Write/Edit content) — the false 'not grounded' rejections on authored files are gone. COST (v4 pass mining + doctrine-mine): every pass paid 4-8 EndTurn round-trips, the biggest share = Stage-2 CITATION rejects (17/43 doctrine findings; the model never re-ran a command for a fresh verbatim line) → 4.90.2 nudge teaches per-turn grounding + re-run; expect controls' +25-35% turn tax to drop — measure at k=5. — v4 (n=1, @4.90.0): gate engaged heavily under strict (flash gate_req=22/cite=13, pro 17/4), controls bn-fit+sqlite held on BOTH models, pro flips vs p3: dna-insert, pytorch-model-cli, cancel-async (n=1 candidates). Prior 3 cells: 4.71 fp 11→1 · fd +2/5 · c3 (n=2, r-c3-candidate-config) code-from-image FLIP 2/2 (first flash-family pass ever; Stage-4 requirement rejections, no mentor) + dna-insert 1/2; 0 clean regressions outside its LIMIT (accepts a re-attested wrong artifact: pytorch-model-cli r2, dna-insert fd). Cost: attestation turns. Operator decision pending. PRO (r-p3, n=1): controls 3/3 held with NO attestation tax (bn-fit 53→30 turns), 0 regressions, 0 paralysis; 0/13 flips on pro's hard core (budget timeouts while working). → k=5 config for BOTH models: guards + GATE+REQ + ENABLE_WEBTOOLS=false, mentor/tail off.
 # [LEDGER 2026-09-06 @4.93.0] ON (reson standard baseline). GATE+REQ (with REQUIREMENTS=true, NOT strict) shipped as the shared reson baseline through resolver-k5 — proven net-positive as a stack. k5 held GATE on in both arms; prior cell evidence stands. Part of the standard.
 CORTEX_ENDTURN_GATE=true
-# CORTEX_ENDTURN_TIER — EndTurn discovery tier: standard (default; deferred behind SearchTools, the 4.107.0 baseline) |
-#   essential (in the turn-1 tool set; no SearchTools hunt for the mandatory finish tool).
+# CORTEX_ENDTURN_TIER — EndTurn discovery tier: essential (DEFAULT since 4.107.3; in the turn-1 tool set, no SearchTools
+#   hunt for the mandatory finish tool) | standard (deferred behind SearchTools; the 4.107.0 baseline, for A/Bs).
 # [LEDGER 2026-09-11 @4.107.2] LEVER (was hard-wired essential in 4.107.1 after the cell-n-r1 census: 70–80% of sessions spent a
 #   SearchTools call hunting EndTurn, 11 tried Task as a finish tool). MECHANISM PROVEN on cell-n-r5: SearchTools 21→2, Task 3→0 —
 #   but the hard core REGRESSED (4/18 vs 11/26) with fewer turns per task: a more salient finish tool may end turns EARLY.
 #   Shipped with the planner doctrine, so the 2×2 (cell-n-r6) attributes it. Default standard = baseline until then.
+# [LEDGER 2026-09-11 @4.107.2] cell-n-r6 2×2 (hard core, n=26/arm): essential 11/26 vs standard 7/26 (same doctrine), main effect 18/52 vs 15/52, paired +7/−3; equals the best control. → k=5 runs with CORTEX_ENDTURN_TIER=essential (K5_EXTRA_COMMON); code default flips to essential in the next release if k=5 n=1 confirms. r5's 4/18 was variance + 8 lost rows, not this lever.
+# [LEDGER 2026-09-11 @4.107.2] tb21-k5-n1 (FULL 89, K=1, flash, essential via K5_EXTRA_COMMON): 70/89 = 78.7% (prev flash best 67/89), $2.81 off-peak, SearchTools 3/88 tasks, resolver false-accept 0.04. → CODE DEFAULT flips to essential in the next release (k=5 n=1 confirms).
+# [LEDGER 2026-09-11 @4.107.3] DEFAULT FLIPPED to essential (code); empty = essential. standard stays available for baselines.
+# [LEDGER 2026-09-11 @4.107.2/4.107.3] k=5 SERIES (TB2.1 full 89 × 5 sequential runs, essential + doctrine v1 + mentor flash/none): 70/71/65/70/68 → pass@1 mean 77.3% (sd 2.7), pooled 344/445; SearchTools ≤5 calls/run. CONFIRMED as default (4.107.3). Installed-DSH control on the same substrate = 71/89 (79.8%), published 90.6 not reproduced. Ledger .cortex/bench/r-tb21-k5-series-2026-09-11.md
 #CORTEX_ENDTURN_TIER=
+
+# CORTEX_COMPACTION_RESUME — resume memory across PROACTIVE compaction (4.108.0, HB-COMPACTION-RESUME). Before 4.108.0 the orchestrator
+# silently DROPPED the oldest message groups at the compaction threshold (~747K tokens on a 1M card) — no summary, no event, no trace,
+# and the task statement itself could be lost. true (default): the helper model summarizes the dropped messages into a resume memory,
+# the original task is pinned verbatim, both are prepended as a <system-reminder>, a `compaction` event lands in decisions.jsonl, the
+# reminder is appended to the session JSONL, and .cortex/memory/resume-<session>.md is written. false = the old silent drop.
+# [LEDGER 2026-09-12 @4.108.0] BUILT + unit-tested (compactionResume.test.ts); UNMEASURED on a bench — the first TB4.0 (8-h budget) run on
+# 4.108.x is the field test (count `compaction` events per session; compare pass rate on tasks that compacted vs the 4.107.2 VM run).
+#CORTEX_COMPACTION_RESUME=
 # Stage 4 (4.70.0, requires the gate ON): task-requirements attestation —
 # enumerate each stated requirement with what satisfies it + how it was
 # verified; mutating turns with no checks are challenged. Default OFF.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nexus-cortex/cli",
-  "version": "4.107.2",
+  "version": "4.108.0",
   "description": "Nexus Cortex CLI - Terminal interface for multi-provider LLM orchestration",
   "main": "dist/index.js",
   "type": "module",
@@ -19,7 +19,7 @@
     "prepack": "node ../../scripts/copy-pkg-cortex-scaffold.mjs"
   },
   "dependencies": {
-    "@nexus-cortex/core": "4.107.2",
+    "@nexus-cortex/core": "4.108.0",
     "chalk": "^4.1.2",
     "cli-spinners": "^2.9.0",
     "commander": "^11.0.0",