@nexus-cortex/cli 4.124.60 → 4.124.62

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 +18 -0
  2. package/package.json +2 -2
package/.env.defaults CHANGED
@@ -626,6 +626,13 @@ CORTEX_LIFT_PLAN=true
626
626
  # [LEDGER 2026-09-27] MiMo K=3 wire (banked `mentor`, 192 lift plans): pro thinking-on @max median 108 s, p90 166 s, 15/192 thinking-off retries — 12–22% of a 900 s MiMo agent budget. e6 (09-18) found no effort level separating (max 10/28, high 12/29, none 11/29 at 10× faster lift); max buys nothing measured. Candidate: CORTEX_LIFT_PLAN_REASONING=none (operator decision).
627
627
  #CORTEX_LIFT_PLAN_EFFORT=max
628
628
  #CORTEX_LIFT_PLAN_BUDGET_TOKENS=4000
629
+ # [LEDGER 2026-10-06] TRAP: this lever governs ONLY the orchestrator's outer wait (withTimeout around generateTaskPlan); the helper's own
630
+ # first-call abort (the one that fires at 180 s and triggers the thinking-OFF truncated retry) follows the per-effort thinking table
631
+ # (mentorRole THINKING_TIMEOUT_MS max=300 s × FIRST_CALL_SHARE 0.6) because the lift-plan mentor config is resolved WITHOUT a timeoutMs
632
+ # input (HelperModelMiddleware ~1617). The 10-05 cap cell set this to 1,000,000 and every abort still recorded firstCallTimeoutMs 180,000.
633
+ # Workaround = CORTEX_MENTOR_THINKING_TIMEOUT_MS (all thinking-on surfaces); proper fix = pass this lever into the lift-plan mentor resolve.
634
+ # [LEDGER 2026-10-06 @4.124.60] FIXED — the lift-plan mentor resolve now receives this lever as timeoutMs, so the first-call abort = 0.6 ×
635
+ # max(this, thinking table): 1,000,000 → 600 s (mentorRole.test.ts). Cells may drop the CORTEX_MENTOR_THINKING_TIMEOUT_MS workaround.
629
636
  #CORTEX_LIFT_PLAN_TIMEOUT_MS=90000
630
637
  #CORTEX_LIFT_PLAN_INTERACTIVE=false
631
638
  #CORTEX_LIFT_PLAN_RECON_TIMEOUT_MS=8000
@@ -1053,6 +1060,10 @@ CORTEX_ENDTURN_GATE=true
1053
1060
  # mid-conversation, thinking resumes next call; costs ONE uncached prefix read). Exhaustion kinds only, never a no-tools nudge. R240 rides
1054
1061
  # along: the retry's usage is now counted in the session ledger. Events: wall_retry_ladder {wallIndex, cap, forceAction, iteration}.
1055
1062
  # [LEDGER 2026-10-06 @4.124.60] DARK — BUILT + unit/integration-tested (wallRetryLadder.test.ts, wallGuard.integration.test.ts); first arm pending.
1063
+ # [LEDGER 2026-10-06 @4.124.60 WIRE-PROVEN] local headless session through the capture proxy (OUTPUT_CAP 1200, LADDER 1150,1100, FORCE_AT 2):
1064
+ # wall 1 (iter 5) → retry max_tokens 1150, no forced choice; wall 2 (iter 7) → retry max_tokens 1100 + tool_choice "required" +
1065
+ # thinking {type: disabled} on the wire → the model acted and finished the task. Events wall_retry_ladder {wallIndex 1 cap 1150}, {wallIndex 2
1066
+ # cap 1100 forceAction true}. Note: with CORTEX_REASONING_EXHAUST_BACKOFF unset the retry effort also stepped down (bundle sets it false).
1056
1067
  #CORTEX_WALL_RETRY_LADDER=
1057
1068
  #CORTEX_WALL_FORCE_ACTION_AT=2
1058
1069
  # CORTEX_HTTP_TIMEOUT_MS — HTTP timeout for the NON-STREAMING chat call (2026-10-05). The openai SDK default (600 s, 2 retries) bounds the
@@ -2089,7 +2100,14 @@ MENTORSHIP_ACTIVE_DISCOVERY=false
2089
2100
  # [LEDGER 2026-10-02 @4.124.45] DARK — BUILT + unit-tested (request shape + usage carried). Live probe: DeepSeek streaming
2090
2101
  # accepted stream_options (200; usage on the final chunk WITH finish_reason, not a separate choices:[] chunk). The prefix
2091
2102
  # harness cannot reach the streaming builders.
2103
+ # [LEDGER 2026-10-06 @4.124.62 R236] DEFAULT FLIPPED, provider-aware: unset = ON for openai | deepseek (live-probed 10-02) | groq, OFF for every
2104
+ # other provider (they may reject the field); explicit on forces any provider; explicit off disables everywhere. Streaming usage had been
2105
+ # zeros by default — the session ledger, lastUsageAnchor and the exhaustion token counts were wrong on every stream (parity map row 4).
2092
2106
  #CORTEX_STREAM_USAGE=
2107
+ # [LEDGER 2026-10-06 @4.124.61 R238] The chat-completions stream's finalMessage now SETTLES on any early exit (consumer break / abort /
2108
+ # throw) with the partial message: finish_reason 'aborted', content + reasoning_content + tool_calls accumulated so far, x_partial: true,
2109
+ # x_estimated_output_tokens (chars/4 — the provider usage chunk never arrives on an abort), x_error on a throw. Natural end byte-identical.
2110
+ # Unblocks an on-stream loop detector with abort (plan P1/P3). Messages and Responses readers untouched.
2093
2111
  # CORTEX_OPENAI_TOOLS_REASONING — HB-OPENAI-TOOLS-REASONING (DARK, 2026-10-02; stack-portability N1). OpenAI reasoning cards never declare
2094
2112
  # reasoning.toggleable, so the gateway withheld the request/action effort (CORTEX_ACTION_EFFORT was a NOOP on every OpenAI path).
2095
2113
  # on: the gateway forwards the effort for OpenAI reasoning cards → Responses `reasoning.effort` (+ summary auto). Chat/completions is
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nexus-cortex/cli",
3
- "version": "4.124.60",
3
+ "version": "4.124.62",
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.124.60",
22
+ "@nexus-cortex/core": "4.124.62",
23
23
  "chalk": "^4.1.2",
24
24
  "cli-spinners": "^2.9.0",
25
25
  "commander": "^11.0.0",