@nexus-cortex/cli 4.124.6 → 4.124.8

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 +14 -0
  2. package/package.json +2 -2
package/.env.defaults CHANGED
@@ -1183,7 +1183,21 @@ CORTEX_ENDTURN_GATE=true
1183
1183
  #CORTEX_FRAME_CANDIDATES=
1184
1184
  #CORTEX_FRAME_WAIT_CAP_S=
1185
1185
  #CORTEX_FRAME_SCREEN_LINES=
1186
+ # [LEDGER 2026-09-22 @4.124.7] R182 KEYSTROKE GUARD (CORTEX_FRAME_KEY_GUARD, default on; operator: "block harmful keystroke patterns, not just a
1187
+ # contract instruction"): before the menu step every generator candidate is classified — pane killers (C-d at an IDLE prompt, exit/logout, exec,
1188
+ # tmux kill-*, kill -9 -1, pkill/killall of bash|tmux) and destructive commands (rm -rf on /, ~, /app, /root…; mkfs; dd/redirect to a block
1189
+ # device; fork bomb; shutdown/reboot; chmod/chown -R /; mv of a root) are REMOVED from the menu, never sent, and the writer is told which and why.
1190
+ # C-d while a command is running stays allowed (EOF to a REPL/cat/heredoc). Templates are never blocked. All-blocked turn → nothing sent, a
1191
+ # re-plan note. Banked on frame_turn as `guard`. Frame-only; the E1/E2 cells stay on 4.124.4/.5.
1192
+ # [LEDGER 2026-09-22 @4.124.8] R183 (operator: "isn't there going to be some legitimate use for destructive commands?" + "use Jev to verify or
1193
+ # override a questionable command"): the guard splits HARD (pane killers, rm -rf of system roots/home, real block devices, shutdown, chmod -R /
1194
+ # — refused outright) from SOFT (rm -rf of /app or ./*, mkfs on a file/image, mv /app, git reset --hard/clean -f/force push — destructive but a task
1195
+ # can ask for it). Soft with Jev on: `intended_<id>` noul (does the TASK TEXT or the note authorize it) ≥ 0.6 runs it; Jev off: runs only with a
1196
+ # justifying `why` (≥ 20 chars) — the writer is told to resend with the reason. Chooser: `unsafe` names the concrete cases (Jev scored the
1197
+ # freecad C-d at unsafe 0.34 under the old wording — the miss that started R180); new `questionable` ("would c1 lose work already produced?")
1198
+ # ≥ 0.5 → restrict to templates + full screen unless `why` justifies c1. Banked guard outcomes: blocked / held / allowed_by_why / allowed_by_jev.
1186
1199
  #CORTEX_FRAME_CONTRACT_EXTRA=
1200
+ #CORTEX_FRAME_KEY_GUARD=
1187
1201
  # (no lever) R169 HB-NEARDUP-SCRATCH-STEM — REFUTED before shipping (2026-09-17, pilot-12 trajectory replay). The distiller's 16
1188
1202
  # "repeated-identical-retry" candidates were re-read: the two stuck sessions (coq-block-bound base arm: `cat > /tmp/tN.v <<EOF` with a
1189
1203
  # DIFFERENT proof body each attempt; rs-archive-clone: 191 distinct `python3 -c` bodies) are unconverged EXPLORATION, not retries —
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nexus-cortex/cli",
3
- "version": "4.124.6",
3
+ "version": "4.124.8",
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.6",
22
+ "@nexus-cortex/core": "4.124.8",
23
23
  "chalk": "^4.1.2",
24
24
  "cli-spinners": "^2.9.0",
25
25
  "commander": "^11.0.0",