loki-mode 11.17.63 → 11.17.65

package/SKILL.md

@@ -3,7 +3,7 @@ name: loki-mode
 description: An autonomous software factory that knows what it is supposed to deliver, and proves it did. Use when the user says Loki Mode or asks to build, fix or verify software autonomously.
 ---
 
-# Loki Mode v11.17.63
+# Loki Mode v11.17.65
 
 **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.
 
@@ -483,4 +483,4 @@ See `CHANGELOG.md` entries [7.5.7], [7.5.8], [7.5.13] for the per-fix list and r
 
 ---
 
-**v11.17.63 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.17.65 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.17.63
+11.17.65

package/dashboard/__init__.py

@@ -7,6 +7,6 @@ Modules:
     control: Session control helpers (status, atomic writes, origin check)
 """
 
-__version__ = "11.17.63"
+__version__ = "11.17.65"
 
 __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.17.63. Do not edit by hand.
+Generated from `loki-ts/src/cli/registry.ts` by `scripts/generate-stale-zero.sh` for v11.17.65. 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.17.63
+**Version:** v11.17.65
 
 **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

@@ -1145,3 +1145,18 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings: the machine fix loop (ran on any failing verify regardless of implement.exit), the 11.17.61 confirmation rule in the loop (required a second conflict claim from fix; removed), fix stage output spec_conflict (only consumer was that rule; removed), the implement/fix briefs (context.ts FIXED_RULES) and the shared stage prefix (lean_prefix.ts) that plan, wall and implement read.
 - Mechanism: the fix loop condition stops when implement.exit is spec_conflict (verify still runs once, E-98b); FIXED_RULES and the stage prefix forbid docs, changelog or README text announcing behavior the code lacks and direct the agent to LOKI_SPEC_CONFLICT. The A-110/E-67 draft PR for a conflict with real implement work is kept.
 - Fixture: loki-ts/tests/engine10/machine.test.ts E-98b case (one verify, no fix round; red on the old loop), implement brief and spec-first goldens re-captured.
+
+## FC-LINT-OOM Tests shard 0 died with "runner has received a shutdown signal" (exit 143) during ShellCheck Linting (LINT-OOM)
+- User-visible vs raw: user-visible (red Tests on main for 11.17.61 and 11.17.63). Raw: no suite failed; the hosted runner was killed mid-lint.
+- Law broken: a gate must fit its machine; resource exhaustion read as a red verdict hides real results.
+- Siblings: the ratchet pass (autonomy/loki, started in the background first) and the per-file pool in tests/run-shellcheck.sh; both could hold a multi-GB shellcheck at once. Measured RSS: autonomy/loki 8.4 GB, autonomy/run.sh 9.8 GB, 16 GB runner.
+- Mechanism: one scheduling rule in tests/run-shellcheck.sh: a file of at least LOKI_SHELLCHECK_HEAVY_LINES (default 5000) lines runs alone (pool drained first, nothing starts until it ends); the ratchet runs serially. Verdict logic unchanged (598 pass, 0 fail locally, 1m45s).
+- Fixture: tests/test-shellcheck-heavy-serial.sh (fake shellcheck records overlap; red on the previous script, green now).
+
+## FC-TEST-LEAKS-INTO-REPO Running the engine10 tests left an untracked loki-ts/calc.ts in the checkout (TEST-LEAKS-INTO-REPO)
+- User-visible vs raw: raw (a dirty tree after any full `bun test tests/engine10`; seen in main and in engineers' worktrees). No user run is affected.
+- Law broken: a test must not write outside its temp repo; a probe must not run in the caller checkout.
+- Writer: preflight's codex login probe (providerLoginIssue, `codex login status`) spawned the stub codex CLI in the process cwd (loki-ts); the stub ignored its args and appended multiply() to calc.ts. Only tests/engine10/providers.test.ts reaches it. Not a session write: sessions already run in ctx.repoDir.
+- Siblings: the cline and aider stubs have no probe today (they only warn on login); the e2e claude stub answers `--help` and `auth status` before touching files.
+- Mechanism: the codex stub exits 0 for `login ...` before any edit, and providerLoginIssue runs the probe in tmpdir() so no probe ever executes in the caller checkout.
+- Fixture: loki-ts/tests/engine10/providers.test.ts snapshots untracked files under loki-ts before and after each provider run and expects none new (red on the old stub, green now).

package/docs/v10/PROGRESS.md

@@ -2563,3 +2563,9 @@ v11.17.21 published (Release success on 462fbc40a; npm latest 11.17.21, next 11.
 
 ## 2026-10-18T21:32Z (CoS) v11.17.63
 - FC-VACUOUS-WALL-GREEN + FC-FIX-OVER-CONFLICT (anthropics/claude-code#21527). HIGH review (review-21527) BLOCK B1 (green-on-base Wall counted as VERIFIED proof) fixed, re-review APPROVE: 430 pass 0 fail across check_result/seal/wall/machine/wall_concurrent/already_done/verify/discard_proto/budget, tsc 0. Full suite shards aa-ad + ae1 0 fail (ae1 723 pass); route_matrix rerun pending (timed out together, fix-forward signal). CI-only guards help-drift/sigpipe/select-tests rc=0.
+
+## 2026-10-18T21:52Z (CoS) v11.17.64
+- FC-LINT-OOM: Tests shard 0 killed (runner shutdown, exit 143) mid ShellCheck on 303d5df9b and d8293520e; measured shellcheck RSS loki 8.4 GB, run.sh 9.8 GB. Heavy files lint alone. tests/test-shellcheck-heavy-serial.sh red on old script, green now; real lint 598 pass 0 fail 1m45s; shard-coverage, sigpipe, select-tests, registration, help-drift, no-dashes rc 0. LOW review (review-21527) APPROVE.
+
+## 2026-10-18T22:54Z (CoS) v11.17.65
+- FC-TEST-LEAKS-INTO-REPO: writer was providers.test.ts codex stub via preflight providerLoginIssue in process cwd. Fix 3c09faeb5: probe cwd tmpdir, stub exits 0 on login. Guard red on parent (codex case fails at providers.test.ts:184, calc.ts appears), green now: providers+preflight 58 pass 0 fail; help-drift rc 0, sigpipe rc 0. TL review APPROVE (note: relative LOKI_CODEX_CLI path resolves against tmpdir; warning only, follow-up).