@nexus-cortex/cli 4.124.52 → 4.124.55

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 +39 -0
  2. package/package.json +2 -2
package/.env.defaults CHANGED
@@ -1822,6 +1822,13 @@ MENTORSHIP_ACTIVE_DISCOVERY=false
1822
1822
  # [LEDGER 2026-10-02 @4.124.44] DARK — BUILT + unit-tested (transportFixes.test.ts: OpenAI/xAI/streaming request shapes,
1823
1823
  # off = byte-identical). Live probe: DeepSeek /responses accepted function_call → function_call_output → user reminder
1824
1824
  # item (200, model obeyed the reminder). NO bench arm. evidence: transport map 10-02 (R215/R216/R218).
1825
+ # [LEDGER 2026-10-03 @4.124.52] LIVE on OpenAI, full harness (cell-smoke, gpt-6-luna + deepseek-v4-pro mentor, payload log): the one
1826
+ # reminder-carrying tool turn went as [function_call_output, message] — inline after the tool output; instructions carried only the static
1827
+ # prompt. First bench arm = STDB run g6rs2 (vs g6pro2 without the lever), 2026-10-03.
1828
+ # [LEDGER 2026-10-03 @4.124.51 cell] NEGATIVE SIGNAL on its first bench arm: STDB MiMo-40 g6rs2 (gpt-6-luna action, deepseek-v4-pro mentor,
1829
+ # R215+R216 on) = 15/40 vs the otherwise-identical g6pro2 = 24/40 (−9; 10 PASS→FAIL / 1 FAIL→PASS; protected rejects 5 vs 3). R216 never
1830
+ # fired (0 truncations) so the drop is R215's. Engagement: effcfg gate active + smoke payload-log shape; no wire log in the cell. Stays DARK.
1831
+ # Ledger omniclaude-v4/.cortex/bench/r-mimo64-g6pro2-g6rs2-2026-10-03.md.
1825
1832
  #CORTEX_RESPONSES_INLINE_REMINDERS=
1826
1833
  # CORTEX_RESPONSES_STOP_REASON — R216 HB-RESPONSES-STOPREASON (DARK, 2026-10-02). extractStopReason returned undefined for
1827
1834
  # the responses and hf-space patterns, so a max-output-tokens cutoff was never classified `truncated` and the wall levers
@@ -1834,7 +1841,39 @@ MENTORSHIP_ACTIVE_DISCOVERY=false
1834
1841
  # reasoning exhaustion; streaming response.incomplete). Live probe: DeepSeek /responses max_output_tokens 8 → status
1835
1842
  # incomplete, incomplete_details {reason: max_output_tokens}, same in the streaming response.incomplete event.
1836
1843
  # evidence: transport map 10-02 (R215/R216/R218).
1844
+ # [LEDGER 2026-10-03 @4.124.52] on in STDB run g6rs2 (first bench arm); the 10-03 OpenAI smoke produced no truncation, so the classifier
1845
+ # path is still unit-test + DeepSeek-probe evidence only (it is response parsing — cannot 400).
1846
+ # [LEDGER 2026-10-03 @4.124.51 cell] UNEXERCISED in g6rs2 (40 tasks, 0 wall/truncation events) — no evidence either way; stays DARK.
1837
1847
  #CORTEX_RESPONSES_STOP_REASON=
1848
+ # CORTEX_CHAT_REMINDERS_TO_SYSTEM — R231 HB-CHAT-REMINDERS-SYSTEM (DARK, 2026-10-03). chat/completions mirror of the Responses-OFF
1849
+ # reminder delivery: every <system-reminder> block carried in a USER text block (lift plan, requirement ledger, PID1 note, plateau
1850
+ # instruction, lift nudge, deferred-corpus header, mentor insight) is lifted out of the conversation and appended to the system message
1851
+ # on every request; reminders prepended to tool results stay in place (same scope as the Responses extractor); the compaction marker
1852
+ # stays. off (default): unchanged — in place with the tags stripped (ChatCompletionsAPIAdapter.stripSystemReminderTags). Cache note:
1853
+ # the system message changes whenever a new reminder appears → DeepSeek prefix-cache miss on those turns (Responses-OFF pays the same).
1854
+ # Why: MiMo-40 g6rs2 (R215 on = in place) 15/40 vs g6pro2 (reminders in `instructions`) 24/40 on GPT-6 Luna; a DeepSeek cell has never
1855
+ # had the system-message delivery. A/B = deepseek-flash action + V4 Pro mentor, MiMo-40, off vs on; readout incl. judge false-accept.
1856
+ # [LEDGER 2026-10-03 @4.124.53] DARK — BUILT + unit-tested (transportFixes.test.ts: lift from user text blocks only, tool-result and
1857
+ # compaction marker untouched, off = byte-identical; gateway scoped to ChatCompletionsAPIAdapter). NO bench arm yet.
1858
+ # [LEDGER 2026-10-03 @4.124.54] WIRE-PROVEN on DeepSeek (cell-smoke through a local CORTEX_PROXY_BASE_URL capture proxy, flash action +
1859
+ # V4 Pro mentor): ON = from the lift on, the reminder text sits in the system message (1007 → 5107 chars, byte-stable across the next 7
1860
+ # requests) and is absent from every user/tool message; OFF = system stays 1008, the reminder is in place in the user/tool messages.
1861
+ # 4.124.53 re-released as 4.124.54 (CI test needed a dummy key). First bench arm = STDB run rsys (off vs on), 2026-10-03.
1862
+ #CORTEX_CHAT_REMINDERS_TO_SYSTEM=
1863
+ # CORTEX_LIFT_PLAN_MODEL / CORTEX_ENDTURN_RESOLVER_MODEL / CORTEX_DEADLINE_EXIT_MENTOR_MODEL / CORTEX_LOOP_TOOL_BLOCK_MODEL /
1864
+ # CORTEX_MENTOR_CONSULT_MODEL — R232 HB-MENTOR-SURFACE-MODEL (DARK, 2026-10-03). Per-surface MENTOR MODEL override: the mentor model
1865
+ # was one knob (MENTORSHIP_HELPER_MODEL fed every surface) while reasoning/effort were already per-surface. An explicit per-surface id
1866
+ # wins over the caller's helperModelId and the global (mentorRole.resolveMentorRoleConfig → modelSource = the var; generateGuidance
1867
+ # calls THAT model; R217 provider-match still applies to defaulted ids). The resolver var also covers the walled-thinking summary
1868
+ # (same surface). Unset = unchanged. Why: MiMo-40 10-03 — V4 Pro mentor 24/40 vs V4 Flash mentor 21/40 on the Luna action model, but
1869
+ # the Flash judge's false-accept was 20% vs Pro's 44% → test "Pro planner + Flash judge" (and the Flash-action analogue).
1870
+ # [LEDGER 2026-10-03 @4.124.55] DARK — BUILT + unit-tested (mentorRole.test.ts: per-surface id wins, unset = inputs/global, modelSource;
1871
+ # events carry the per-surface model via describeMentorWire). NO bench arm yet.
1872
+ #CORTEX_LIFT_PLAN_MODEL=
1873
+ #CORTEX_ENDTURN_RESOLVER_MODEL=
1874
+ #CORTEX_DEADLINE_EXIT_MENTOR_MODEL=
1875
+ #CORTEX_LOOP_TOOL_BLOCK_MODEL=
1876
+ #CORTEX_MENTOR_CONSULT_MODEL=
1838
1877
  # CORTEX_ANTHROPIC_HISTORY_CACHE — R218 HB-ANTHROPIC-CACHE (DARK, 2026-10-02). Anthropic Messages requests set cache_control
1839
1878
  # only on the system prompt and the last tool, so the conversation history was never cached on Claude. on (and
1840
1879
  # ANTHROPIC_PROMPT_CACHING not false): rolling message breakpoints on the last markable block (not thinking, not empty
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nexus-cortex/cli",
3
- "version": "4.124.52",
3
+ "version": "4.124.55",
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.52",
22
+ "@nexus-cortex/core": "4.124.55",
23
23
  "chalk": "^4.1.2",
24
24
  "cli-spinners": "^2.9.0",
25
25
  "commander": "^11.0.0",