loki-mode 11.71.3 → 11.72.1

package/SKILL.md

@@ -3,7 +3,7 @@ name: loki-mode
 description: Runs an autonomous software factory that knows what it is supposed to deliver and proves it did, with a signed receipt. Use when the user says Loki Mode or asks to build, fix or verify software autonomously.
 ---
 
-# Loki Mode v11.71.3
+# Loki Mode v11.72.1
 
 **Current entry points (Loki 10 engine):** `loki "<task>"`, `loki owner/repo#N` and `loki quick "<task>"` run the Loki 10 engine and end with a signed receipt (`loki verify`). `loki backlog owner/repo --all` runs many issues in parallel. Guide: `docs/v10/GUIDE.md`. The skill instructions below, and `loki start`, describe the previous bash loop. PRD-file starts (`loki start ./prd.md`) and the opencode provider still run on it until FC38-SWEEP ports them; the legacy-engine command and the LOKI_ENGINE switch remain removed. Prefer `loki owner/repo#N` for issues.
 
@@ -476,4 +476,4 @@ Implemented, planned and deprecated items, with the version each landed in: `ski
 
 ---
 
-**v11.71.3 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.72.1 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.71.3
+11.72.1

package/dashboard/__init__.py

@@ -7,6 +7,6 @@ Modules:
     control: Session control helpers (status, atomic writes, origin check)
 """
 
-__version__ = "11.71.3"
+__version__ = "11.72.1"
 
 __all__ = ["__version__"]

package/docs/CLI-REFERENCE.md

@@ -1,6 +1,6 @@
 # CLI reference
 
-Generated from `loki-ts/src/cli/registry.ts` by `scripts/generate-stale-zero.sh` for v11.71.3. Do not edit by hand.
+Generated from `loki-ts/src/cli/registry.ts` by `scripts/generate-stale-zero.sh` for v11.72.1. Do not edit by hand.
 Hidden and legacy-only commands are omitted; see `docs/v10/CLI-MODERN.md` for the full inventory.
 
 | Command | Description |

package/docs/INSTALLATION.md

@@ -2,7 +2,7 @@
 
 Loki Mode, by [Autonomi](https://www.autonomi.dev/), turns a spec or an issue into a verified pull request with a receipt you can check. This page covers installing it, a first run, and the options around it.
 
-**Version:** v11.71.3
+**Version:** v11.72.1
 
 **Engine note:** `loki start` is the primary command. `loki start`, `loki "<task>"`, `loki owner/repo#N` and `loki quick` all run the Loki 10 engine, whatever the flag order or input form (PRD file, issue ref, task or one-word brief). The previous loop runs only on `--engine legacy`, `LOKI_ENGINE=legacy`, or for one call when a flag Loki 10 cannot honor is present. See the [user guide](v10/GUIDE.md) and the [5-minute quickstart](QUICKSTART.md).
 

package/docs/v10/FAILURE-CLASSES.md

@@ -1990,3 +1990,21 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept: telemetry row (printed the full LOKI_TELEMETRY_ENDPOINT url including path; now host only), update check, model inference (unchanged, still the only REQUIRED row and the only one that sets the exit code), JSON output (same rows with `required: false`), a server name or env value holding a tab, newline or other control character (cleaned to `?` where each record is emitted, and the JSON reader skips a malformed line instead of raising), the three MCP config files (`.mcp.json`, `$LOKI_DIR/mcp-config.json`, `~/.claude/mcp.json`; `url` servers only, stdio servers are local). Unicode line separators U+0085, U+2028 and U+2029 in a server name or url host are masked like C0 and the --json loader splits on "\n" only (splitlines() would break on them and hide hosts).
 - Mechanism: `_LOKI_AIRGAP_EGRESS_ENV` (name and meaning) and `_LOKI_AIRGAP_EGRESS_NOT` (name and reason) sit beside the audit; `_loki_airgap_configured_egress` emits one row per set registry name plus one per MCP url server, host only, with a loopback flag and the exact disable step. tests/test-airgap-commands.sh section 6 greps the tree and fails on any egress-looking name in neither list.
 - Fixture: tests/test-airgap-commands.sh section 6: every registry name set to a host is named (path not leaked), JSON carries the host, nothing configured reports no extra rows and exit 0, an MCP url server is named and a stdio server is not, the tree guard is green, and a fixture tree with a fake `LOKI_FOO_URL` reader turns it red.
+
+
+## FC-WORKER-NO-PROCESS-LIMITS The engine10 worker and every process it starts ran with the caller's resource limits, so a runaway build or fork loop in a worker could exhaust memory or the process table of the whole machine (#265 slice B)
+
+- User-visible vs raw: user-visible (a machine-wide stall during a run).
+- Law: an explicit opt-in limit must either hold for the worker tree or stop the run with a named reason; it must never run unlimited silently, and an unset knob must leave the spawn untouched.
+- Cause (measured): `git grep -n ulimit -- autonomy providers loki-ts/src` returned no hit in any spawn wrapper, and spawnWorker in loki-ts/src/runner/worker_proc.ts passed [cmd, ...args] straight to spawn. Node cannot set rlimits, so a shell wrapper at this one call site is the only mechanism.
+- Siblings swept: bash-route provider spawns are owned by the #335 confinement wrapper, and the subagent cap is #265 slice C; both are out of scope here. The detached deep-verify spawn in loki-ts/src/engine10/supervisor.ts is the same class (a model-driven child under the worker env) and now goes through `ulimitArgv` too (r2); an invalid knob records `deep verify not spawned: <reason>` in NOT PROVEN instead of spawning. Mutant: spawn the raw deepArgv and the new deep_wiring test (ulimit -u reads 2000 in the deep child) goes red.
+- Mechanism: ulimitArgv in runner/worker_proc.ts wraps argv in `/bin/sh -c 'ulimit ... || exit 97; shift N; exec "$@"'` only when LOKI_ULIMIT_VMEM_KB or LOKI_ULIMIT_NPROC is set. Values travel as positional arguments, never in the script text, and a value that is not a positive integer is refused before any spawn. A ulimit the OS refuses (macOS rejects -v) exits 97 with a named reason.
+- Fixture: loki-ts/tests/runner/worker_proc.test.ts covers the applied limit, the byte-identical unset argv, the refused injection value, the exit-97 path, and a mutant that drops the exit.
+
+## FC-L0-GUARD-RED-ON-MAIN
+- User-visible vs raw: raw (tests/engine10/l0_guard.test.ts red on main e4e5043ea, 2 of 3 tests failing; no user effect).
+- Law broken: Engine Law gate integrity. A guard that is red on main means merged slices bypassed it, so it no longer protects the generic-not-per-stack rule.
+- Cause (measured, git log -S): six new hits landed on 2026-10-23 in 6912e4a21 (failures.ts go test and cargo test, repo_profile.ts npm test comment), 8e5dc5028 (verify.ts pyproject.toml, requirements.txt) and e409e4b91 (util/shell.ts go test comment); 62f946e19 removed wall.ts jest and vitest without shrinking the allowlist. scripts/select-tests.sh --files-from on the 8e5dc5028 file list DOES select loki-ts/tests/engine10/l0_guard.test.ts (R8, measured), so the selector is not the gap; the slice gates that approved these commits did not run or did not heed the selected guard, and only the post-merge run showed it red. The guard itself was always correct.
+- Siblings swept: all six hits plus both stale rows, decided per hit: 3 comment-only hits reworded away (repo_profile.ts, util/shell.ts) or kept as output-parser rows (failures.ts go and cargo, same role as the listed jest, pytest, vitest rows); verify.ts manifests allowlisted with a reason (lint tool detection of the target repo as data); 2 stale wall.ts rows removed.
+- Mechanism: the allowlist stays reviewed one row at a time; no regeneration.
+- Fixture: tests/engine10/l0_guard.test.ts 3 pass; mutation: re-adding a removed probe makes "no unlisted manifest probe" red.