@nexus-cortex/cli 4.119.1 → 4.120.0

package/.env.defaults

@@ -283,6 +283,7 @@ CORTEX_EFFORT_TAIL=false
 #   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
+# [LEDGER 2026-09-18 @4.119.1] TB4.0 cell e6 (29 ever-passed tasks, 3-h budgets, flash, 1 repeat): LOW = REJECT 3/29 vs high 10/28 (+2/−9, p 0.07; tokens equal, wall +60%); MAX = WASH vs high 10/29 (+4/−4) at +30% tokens/+60% wall. Wire: reasoning/iteration FLAT across levels (4.6K/5.0K/4.8K chars), only the peak call scales (15.8K/22.7K/26.1K tok) — effort caps peak reasoning, not typical. Keep HIGH for TB4.0. Ledger r-tb4-e6-effort-2026-09-18.md.
 #CORTEX_ACTION_EFFORT=
 # Trigger helper-model review on tool errors (only applies when mentorship is enabled)
 MENTORSHIP_TRIGGER_ON_ERROR=false
@@ -300,6 +301,8 @@ MENTORSHIP_CUSTOM_KEYWORDS=
 # (apprentice) so the mentor is genuinely stronger on the task.
 # (For image/vision background tasks, deepseek-v4-flash-vision-exp is the vision-capable option.)
 # [LEDGER 2026-09-02 @4.89.0] ON=pro — NEVER a same-strength mentor: flash→flash peer = −2 engaged (m88b, confident-wrong hints lost chess+tune-mjcf); pro elder = +1 engaged (m88). For a PRO apprentice this makes pro→pro = the harmful peer config → run pro with CORTEX_MENTOR_AUTO=false.
+# [LEDGER 2026-09-18] 🔴 V4 PRO IS NOT RETIRED — DeepSeek REINSTATED it (operator, repeated correction): "In response to user demand, we have decided to continue providing API services for DeepSeek V4 Pro after September 14, 2026, with the billing method remaining unchanged. We will provide further notice should there be any changes. Thank you for your understanding and support!"
+#   deepseek-v4-pro serves V4 Pro weights, same billing; the 09-10 retirement note below is HISTORY, do not repeat it.
 # [LEDGER 2026-09-10 @4.102.0] deepseek-flash @max — V4 Pro is RETIRED 2026-09-14 04:00 UTC (routes to V4.1 Flash after
 #   that). DeepSeek states V4.1 Flash surpasses V4 Pro; the mentor roles (lift/resolver/deadline/loop-exit, AskForAdvice) run
 #   at effort max regardless of card. The "never a same-strength mentor" rule (m88b: v4-FLASH peer −2 engaged) was measured
@@ -335,6 +338,8 @@ MENTORSHIP_HELPER_MODEL=deepseek-flash
 #   surface's own *_EFFORT (CORTEX_LIFT_PLAN_EFFORT etc.), when explicitly set, wins over it. Empty = per-surface (max).
 # [LEDGER 2026-09-10 @4.105.0] unset — cell-m A/Bs {pro, deepseek-flash} × {low, high, max} (+ thinking-off baselines).
 # [LEDGER 2026-09-11 @4.107.0] cell-n-r3 flash@low (REASONING=on): REJECT — delivery 91% thinking-on (the treatment fired) but false-accept 0.67 (worst measured; high 0.56, max 0.50, off 0.33) and 6/24 vs control 11/26. Effort is monotone in cost only; ANY thinking on the resolver raises false accepts. Moot while REASONING=none (k=5). DARK. Ledger r-cell-n-r34.
+# [LEDGER 2026-09-18 @4.119.1] TB4.0 cell e6, pro planner (resolver thinking-off in all arms, so this reached ONE call/session — the lift plan): control per-surface max 10/28 · low 9/29 (+3/−4) · high 12/29 (+5/−3, p 0.73, best point estimate, ~half of max's planner latency) · REASONING=none 11/29 (+3/−2, 10x faster lift). No level separates at n=29; candidate for the full run = high. Wire: max delivered thinking-on 5/5 @118–178 s; high 4/5 (+1 thinking-off retry) @60–158 s; low 3/5 (+2 retries) @53–84 s.
+# [LEDGER 2026-09-19 @4.119.1] FIELD, full TB4.0 (stack arm, =high): WASH vs per-surface max control (12/62 each); planner thinking-on 20/36 (16 retries) vs max 24/38 (14 retries).
 #CORTEX_MENTOR_EFFORT=
 # [LEDGER 2026-09-10 @4.105.0] cell-m pilot: low/high/max UNMEASURABLE — the thinking-on calls came back empty (see CORTEX_MENTOR_REASONING). Only flash@low ever delivered (1/4 plans, 2/3 verdicts). Re-test after HB-MENTOR-BUDGET.
 #   CORTEX_ASK_FOR_ADVICE — true|false. Include the model-initiated AskForAdvice consult tool while mentorship is on.
@@ -388,10 +393,11 @@ MENTORSHIP_HELPER_MODEL=deepseek-flash
 # grader; the planner's limit is planning from a snapshot — and every later steering surface anchors to that plan. Event lift_plan +=
 # {toolRounds, roundsUsed, investigateChecks, investigateReads, investigateRefused, investigateAfterWithdraw, roundLatencyMs,
 # evidenceChars}. Default 1 = 4.117.3 byte-for-byte.
-# [LEDGER 2026-09-18 @4.118.0] BUILT + unit-tested (liftPlanner.test.ts R171). Field: PENDING (pilot-12 arm lp = ROUNDS 3 vs control c4).
+# [LEDGER 2026-09-18 @4.118.0] BUILT + unit-tested (liftPlanner.test.ts R171). FIELD 09-18 (arm lp, 4.118.1): DELIVERED + FULLY ENGAGED (12/12 sessions investigated, 47 checks + 36 reads), NULL — 1/12 = control; planner cost 2–9 min/task at pro/thinking-on → use the flash planner or ROUNDS=2 (ledger §10).
 #CORTEX_LIFT_PLAN_TOOL_ROUNDS=
 #CORTEX_LIFT_PLAN_TOOL_ROUND_BUDGET_MS=
 # [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.
+# [LEDGER 2026-09-19 @4.119.1] FIELD, full TB4.0 (stack arm, =on @high, pro): thinking-on delivered 38/87 verdicts, 47/87 fell to the thinking-off retry (16K allowance exhausted); outcome WASH vs thinking-off control (12/62 each).
 #CORTEX_ENDTURN_RESOLVER_REASONING=
 #CORTEX_DEADLINE_EXIT_MENTOR_REASONING=
 #CORTEX_LOOP_TOOL_BLOCK_REASONING=
@@ -1032,7 +1038,7 @@ CORTEX_ENDTURN_GATE=true
 # HELD once — sharing CORTEX_FINISH_CONFIRM_MAX with R167 — with the check results, the budget and the junior's open_items; an
 # unverified MEETS also no longer silences the R151/R157 nudges. A MEETS backed by a passing check stands. Event: finish_confirm
 # {action:'accept', meets:true, evidencePassed, checksNamed, namedRanNow, namedPassed, …}. =false restores 4.116.2 byte-for-byte.
-# [LEDGER 2026-09-17 @4.117.0] BUILT + unit-tested (endTurnResolver.test.ts R168). Field: PENDING (pilot-12 rerun, lever arm vs control).
+# [LEDGER 2026-09-17 @4.117.0] BUILT + unit-tested (endTurnResolver.test.ts R168). FIELD 09-17 (pilot-12 rerun-3 arm mc): DELIVERED, NULL, PRECISION-LIMITED — every MEETS named 2–3 checks, >=1 PASSED each time, hold fired 0x, 1/12 vs control 1/12 (ledger §9).
 #CORTEX_MEETS_CONFIRM=
 #CORTEX_MEETS_CONFIRM_MIN_REMAINING=
 # CORTEX_TURN_CONTRACT_ENFORCE / CORTEX_TURN_CONTRACT_ENFORCE_MAX — HB-TURN-CONTRACT-ENFORCE (4.117.0, 2026-09-17). The channel contract as
@@ -1042,7 +1048,7 @@ CORTEX_ENDTURN_GATE=true
 # error results carrying the re-prompt — up to ENFORCE_MAX (2) times per turn, then the batch runs as-is (liveness). Finish batches
 # (EndTurn) are exempt. Pair with CORTEX_TURN_CONTRACT=channel (the prompt half). Events: turn_contract_reject {iteration, rejects,
 # max, missing, tools}, turn_contract_fallback. Default off = byte-identical.
-# [LEDGER 2026-09-17 @4.117.0] BUILT + unit-tested (turnContractValidator.test.ts). Field: PENDING (pilot-12 rerun, lever arm vs control).
+# [LEDGER 2026-09-17 @4.117.0] BUILT + unit-tested (turnContractValidator.test.ts). FIELD 09-17 (rerun-3 arm tc): DELIVERED, NULL — 22 rejections / 10 fallbacks, compliance 6% → ~95%, 0/12 vs control 1/12, output +9% (ledger §9).
 #CORTEX_TURN_CONTRACT_ENFORCE=
 #CORTEX_TURN_CONTRACT_ENFORCE_MAX=
 # CORTEX_ACTION_PLAN_FIELDS — R172 HB-ACTION-PLAN-FIELDS (4.119.0, 2026-09-18, operator: "can we have the model output those as a structured
@@ -1054,6 +1060,7 @@ CORTEX_ENDTURN_GATE=true
 # before dispatch (executors + loop guards see bare params) and keep them in the canonical message, so every action's rationale is in
 # the trajectory. Event action_plan_reject {iteration, rejects, missing}. Cost: a few dozen output tokens per call. Default off.
 # [LEDGER 2026-09-18 @4.119.0] BUILT + unit-tested (turnContractValidator.test.ts R172). Field: PENDING (full-66 run arm vs control).
+# [LEDGER 2026-09-19 @4.119.1] FIELD, full TB4.0 (stack arm): 21 action_plan_reject events in 15/32 sampled sessions (enforced, model complied); outcome 12/62 vs control 12/62 — WASH. The Terminus "analysis+plan per action" half does not move flash here.
 #CORTEX_ACTION_PLAN_FIELDS=
 # CORTEX_JUDGE_TOOL_ROUNDS / CORTEX_JUDGE_TOOL_ROUND_BUDGET_MS — R170 HB-JUDGE-TOOL-LOOP (4.117.0, 2026-09-17). The v2 of
 # docs/LIFT_MENTOR_PLANNER_EXPERIMENT_SPEC.md §2.2/§2.4 ("bounded tool-using mentor, turn-capped never token-capped"), built as a
@@ -1066,7 +1073,8 @@ CORTEX_ENDTURN_GATE=true
 # gone; an INVESTIGATE after withdrawal abstains (never re-loops). Investigation checks that pass count as evidence for R168.
 # The thinking-on escalation is skipped when >1 round ran. Event endturn_resolver gains {toolRounds, roundsUsed, investigateChecks,
 # investigateReads, investigateRefused, roundLatencyMs, evidenceChars}; `mentor` describes the LAST call. Default 1 = 4.116.2.
-# [LEDGER 2026-09-17 @4.117.0] BUILT + unit-tested (endTurnResolver.test.ts R170, judgeEvidence.test.ts R170). Field: PENDING (pilot-12 rerun, ROUNDS=3 arm vs control).
+# [LEDGER 2026-09-17 @4.117.0] BUILT + unit-tested (endTurnResolver.test.ts R170, judgeEvidence.test.ts R170). FIELD 09-17: 4.117.0 arm VOID (closing line overrode the offer; fixed 4.117.1); 4.117.2 arm jl2 DELIVERED + ENGAGED (5/26 adjudications multi-round, 27 checks/reads) — 2/12 vs control 1/12, within noise (ledger §9).
+# [LEDGER 2026-09-19 @4.119.1] FIELD, full TB4.0 (62 tasks, 1 repeat, in the STACK arm with resolver reasoning on @high + R172 + mentor high): 12/62 vs control 12/62 — WASH (7 flips each way, p 1.0). Engaged: 2–3 rounds in 59/87 adjudications, 122 checks + 183 reads. Lever pile CLOSED for TB4.0; ledger r-tb4-full-f1-2026-09-18.md.
 #CORTEX_JUDGE_TOOL_ROUNDS=
 #CORTEX_JUDGE_TOOL_ROUND_BUDGET_MS=
 # CORTEX_JUDGE_TOOL_AUTOLOOP — R170b (4.117.3, 2026-09-17, rerun-3 jl/jl2 field read). Offered INVESTIGATE (persona + closing
@@ -1075,8 +1083,34 @@ CORTEX_ENDTURN_GATE=true
 # verdict that names CHECK lines is treated as provisional — the harness runs them (read-only denylist), appends the EVIDENCE block
 # ("your provisional verdict was …; decide again on these results") and asks once more; checks run in the loop are cached so the
 # R166 evidence pass does not re-run them. Event endturn_resolver += {autoLooped, toolAutoLoop}. Needs ROUNDS >= 2. Default off.
-# [LEDGER 2026-09-17 @4.117.3] BUILT + unit-tested. Field: PENDING (rerun-3 jl3 arm: ROUNDS=3 + AUTOLOOP vs control).
+# [LEDGER 2026-09-17 @4.117.3] BUILT + unit-tested. FIELD 09-17 (arm jl3): ENGAGED HARD (9/25 adjudications multi-round, 56 checks/reads), NULL — 1/12 vs control 1/12; the judge re-issues the same verdict on its own checks' results (ledger §9).
 #CORTEX_JUDGE_TOOL_AUTOLOOP=
+# CORTEX_JUDGE_GAP_HOLD — R173 HB-GAP-HOLD (4.120.0, 2026-09-20; from the f1 curation r-tb4-f1-curation-2026-09-19.md: the judge often
+# named the real defect, the finish was accepted "with gap" because no harness-run check had FAILED (R166 evidence mode, effective veto
+# budget 1), and 96/100 failing sessions gave up with ~85% of the budget unused). With GAP_HOLD an evidence-mode GAP that names open
+# items is RETURNED to the junior — with or without a failed check — while >= CORTEX_BUDGET_CONTINUE_MIN_REMAINING of the wall budget
+# remains and the budgeted cap (MAX_REJECTS_BUDGETED, 6) allows; the R165 progress rules still apply (re-attest without progress →
+# one thinking-on escalation, then the finish stands). Below the floor, or with no deadline, R166 is unchanged. Event endturn_resolver
+# += {gapHold, gapHoldable}. Default off.
+# [LEDGER 2026-09-20 @4.120.0] BUILT + unit-tested (R173 block in endTurnResolver.test.ts). FIELD: pending (cell g1: control vs GAP_HOLD+SPEC_TESTS on the 29-task ever-passed cell ∪ the 13-task fixable pool).
+#CORTEX_JUDGE_GAP_HOLD=
+# CORTEX_JUDGE_GAP_HOLD_JEV / _MIN — R173b (4.120.0): typed gate on the hold via TypeSafe Jev (fixable_with_more_turns noul over the
+# task + the reviewer's items + the budget; ~0.3 s, $0.042/M input, zero output tokens; measured AUC 0.72 / ECE 0.06 on 262 sessions).
+# off (default) | shadow (bank jevFixable on the event, no control-flow change) | gate (hold only when P >= _MIN, default 0.3; fail-closed
+# to R166 when the call fails). Needs TYPESAFE_API_KEY in the executor env. The typed result changes control flow, never prose.
+# [LEDGER 2026-09-20 @4.120.0] BUILT + unit-tested (jevGate.test.ts). FIELD: shadow on cell g1 (bank the probabilities against the grader).
+#CORTEX_JUDGE_GAP_HOLD_JEV=
+#CORTEX_JUDGE_GAP_HOLD_JEV_MIN=
+# CORTEX_JUDGE_SPEC_TESTS / _MAX — R174 HB-SPEC-TESTS (4.120.0, 2026-09-20): BLIND spec-derived checks. At the first finish of a turn
+# a mentor call (endturn-resolver wire, its own persona) that sees ONLY the task text + environment report writes up to _MAX (4; 1..8)
+# read-only `CHECK:` commands that exit non-zero with a printed reason when a requirement the task states is unmet; the harness runs
+# them (R170 runner + denylist) at every adjudication, shows the results to the judge, and a FAILED spec check is objective evidence
+# for the veto (R166 checksFailed) — independent of the agent's own tests (83/100 failing sessions had their own test passing) and of
+# the judge's post-hoc checks (f1: 122 checks confirmed the agent's reading of the spec). Events: spec_tests {checks, genLatencyMs,
+# refused}; endturn_resolver += {specTests, specChecks, specRan, specPassed, specFailed, specInconclusive, specGenLatencyMs}. Default off.
+# [LEDGER 2026-09-20 @4.120.0] BUILT + unit-tested (R174 block in endTurnResolver.test.ts). FIELD: pending (cell g1).
+#CORTEX_JUDGE_SPEC_TESTS=
+#CORTEX_JUDGE_SPEC_TESTS_MAX=
 # (no lever) R169 HB-NEARDUP-SCRATCH-STEM — REFUTED before shipping (2026-09-17, pilot-12 trajectory replay). The distiller's 16
 # "repeated-identical-retry" candidates were re-read: the two stuck sessions (coq-block-bound base arm: `cat > /tmp/tN.v <<EOF` with a
 # DIFFERENT proof body each attempt; rs-archive-clone: 191 distinct `python3 -c` bodies) are unconverged EXPLORATION, not retries —

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nexus-cortex/cli",
-  "version": "4.119.1",
+  "version": "4.120.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.119.1",
+    "@nexus-cortex/core": "4.120.0",
     "chalk": "^4.1.2",
     "cli-spinners": "^2.9.0",
     "commander": "^11.0.0",