@nexus-cortex/cli 4.116.0 → 4.117.0

package/.env.defaults

@@ -1010,6 +1010,49 @@ CORTEX_ENDTURN_GATE=true
 #CORTEX_FINISH_CONFIRM=
 #CORTEX_FINISH_CONFIRM_MIN_REMAINING=
 #CORTEX_FINISH_CONFIRM_MAX=
+# CORTEX_MEETS_CONFIRM / CORTEX_MEETS_CONFIRM_MIN_REMAINING — R168 HB-MEETS-CONFIRM (4.117.0, 2026-09-17, pilot-12 rerun read). A MEETS was
+# unconditional: decideVetoAction accepted it on the verdict string alone, the judge's own CHECK: lines were never run for a MEETS, and
+# R167's hold excluded MEETS by construction — 2–3 sessions per arm finished on a WRONG MEETS at 81–92% budget left and walked straight
+# through (html-js-filter, mvcc-lsm-compaction, gsea). FIX: with the lever on the judge persona demands one to three `CHECK:` lines whose
+# PASSING proves the task's own criteria; the harness runs them at once; a MEETS with no passing evidence (nothing named, or every named
+# check failed/inconclusive, and the workspace's own check entry point did not pass) with >= MIN_REMAINING (0.5) of the budget left is
+# 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).
+#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
+# a PROMPT clause did not take (pilot-12: 6% of tool-calling turns carried ANALYSIS + PLAN; 8/10 sessions ignored it). Terminus 2 does
+# not ask — its parser REJECTS a response missing the fields and re-prompts. This is that structural half: with ENFORCE=true a
+# tool-calling response whose visible text lacks a line-leading ANALYSIS and PLAN is rejected — its tool calls come back UNEXECUTED as
+# 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).
+#CORTEX_TURN_CONTRACT_ENFORCE=
+#CORTEX_TURN_CONTRACT_ENFORCE_MAX=
+# 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
+# HARNESS-DRIVEN text protocol over the existing single-shot helper call: the helper request path carries no tools (no tools/
+# tool_choice/tool role in any helper adapter), but the harness already RUNS judge-named checks (R166 runCheck) — the missing edge was
+# that the judge never saw the results of the commands it named in the same round. With ROUNDS > 1 the persona offers
+# `VERDICT: INVESTIGATE` + `CHECK: <cmd>` (read-only denylist: no rm/mv/git checkout/redirect-to-file/installs) + `READ: <path>[:a-b]`
+# (in-workspace file slices, 120 lines / 4 KB, binary + oversize refused); the harness executes them, appends an EVIDENCE block and
+# asks again, withdrawing the option on the last round or when the aggregate ROUND_BUDGET_MS (240 s) or 2x that of the wall budget is
+# 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).
+#CORTEX_JUDGE_TOOL_ROUNDS=
+#CORTEX_JUDGE_TOOL_ROUND_BUDGET_MS=
+# (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 —
+# R136's inline-body Dice correctly keeps them apart, and replaying the similarity lens over the real commands gives max window
+# counts of 5 and 3 (diversify fires at 7) with OR without numbered-scratch-file stem grouping; grouping only pushed a healthy
+# exploration (gsea's diagN.py) from 2 to 6. The in-place case (persist coq, one Main.v) reached 15 and DID block. No identity-grouping
+# lever shipped; the class is a distiller artifact + hard tasks. Ledger r-tb4-pilot12-2026-09-17.md §9.
 # (no lever) 4.110.0 closes the 4.109.0 disclosures (2026-09-16): R154 image-rejection heal now also covers the STREAMING loop
 # (continuation re-streamed once after the stub; stream empty-retry and stream R29a synthesis wrapped like the non-streaming calls);
 # the sub-agent console fallback prints a progress beat only on a turn change or every 30 s (was every second: 500+ ticker lines per

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nexus-cortex/cli",
-  "version": "4.116.0",
+  "version": "4.117.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.116.0",
+    "@nexus-cortex/core": "4.117.0",
     "chalk": "^4.1.2",
     "cli-spinners": "^2.9.0",
     "commander": "^11.0.0",