@nexus-cortex/cli 4.118.1 → 4.119.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/.env.defaults +10 -0
  2. package/package.json +2 -2
package/.env.defaults CHANGED
@@ -1045,6 +1045,16 @@ CORTEX_ENDTURN_GATE=true
1045
1045
  # [LEDGER 2026-09-17 @4.117.0] BUILT + unit-tested (turnContractValidator.test.ts). Field: PENDING (pilot-12 rerun, lever arm vs control).
1046
1046
  #CORTEX_TURN_CONTRACT_ENFORCE=
1047
1047
  #CORTEX_TURN_CONTRACT_ENFORCE_MAX=
1048
+ # 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
1049
+ # json requirement?"). Terminus 2's per-step shape is analysis + plan as FIELDS of the same JSON object as the commands. JSON mode
1050
+ # (response_format json_object) competes with native tool calling, so the faithful expression inside this harness is the action tool's
1051
+ # own JSON: with the lever on, Bash/Edit/Write schemas gain REQUIRED `analysis` + `plan` strings; a call missing either is returned
1052
+ # unexecuted with a corrective error EVERY time (no per-turn cap — unlike CORTEX_TURN_CONTRACT_ENFORCE, whose cap default 2 relented
1053
+ # in 10/12 pilot sessions; that clamp is raised to 10000 in 4.119.0 for a never-relent arm); valid calls have the fields stripped
1054
+ # before dispatch (executors + loop guards see bare params) and keep them in the canonical message, so every action's rationale is in
1055
+ # the trajectory. Event action_plan_reject {iteration, rejects, missing}. Cost: a few dozen output tokens per call. Default off.
1056
+ # [LEDGER 2026-09-18 @4.119.0] BUILT + unit-tested (turnContractValidator.test.ts R172). Field: PENDING (full-66 run arm vs control).
1057
+ #CORTEX_ACTION_PLAN_FIELDS=
1048
1058
  # CORTEX_JUDGE_TOOL_ROUNDS / CORTEX_JUDGE_TOOL_ROUND_BUDGET_MS — R170 HB-JUDGE-TOOL-LOOP (4.117.0, 2026-09-17). The v2 of
1049
1059
  # docs/LIFT_MENTOR_PLANNER_EXPERIMENT_SPEC.md §2.2/§2.4 ("bounded tool-using mentor, turn-capped never token-capped"), built as a
1050
1060
  # HARNESS-DRIVEN text protocol over the existing single-shot helper call: the helper request path carries no tools (no tools/
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nexus-cortex/cli",
3
- "version": "4.118.1",
3
+ "version": "4.119.1",
4
4
  "description": "Nexus Cortex CLI - Terminal interface for multi-provider LLM orchestration",
5
5
  "main": "dist/index.js",
6
6
  "type": "module",
@@ -19,7 +19,7 @@
19
19
  "prepack": "node ../../scripts/copy-pkg-cortex-scaffold.mjs"
20
20
  },
21
21
  "dependencies": {
22
- "@nexus-cortex/core": "4.118.1",
22
+ "@nexus-cortex/core": "4.119.1",
23
23
  "chalk": "^4.1.2",
24
24
  "cli-spinners": "^2.9.0",
25
25
  "commander": "^11.0.0",