loki-mode 11.60.9 → 11.60.11

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.60.9
+# Loki Mode v11.60.11
 
 **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.60.9 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.60.11 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.60.9
+11.60.11

package/dashboard/__init__.py

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

@@ -1601,6 +1601,14 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Mechanism: extract_invocations also reads `loki <word> [--flag ...]` from the text left after backticked spans are removed. A plain hit with a --flag is checked exactly like a backticked one. A bare `loki <word>` could be prose, so it is checked only when the word is already a literal command in loki.bash main_commands; measured on the newest 30 sections the plain extractor finds 4 distinct invocations and no prose false positive.
 - Fixture: tests/test-help-changelog-drift.sh self-test: plain-prose real flag passes, plain-prose unknown flag is reported by name, bare prose naming no command passes, and a window with no invocation still reports broken extraction. With the plain branch removed the first and third fixtures and the real run go red.
 
+## FC-HELP-DRIFT-WINDOW-CAP The help-drift guard went red on main again because five consecutive slice releases named no command, so its fixed 5-section window held nothing and it called its own extraction broken
+- User-visible vs raw: raw (a red gate on a clean main). tests/test-help-changelog-drift.sh exits 1 with "no 'loki ...' invocations (backticked or plain) in the newest 5 CHANGELOG sections; extraction is broken" on origin/main 11ab1df18 (v11.60.6) and on a78f48031 (v11.60.8), after FC-HELP-DRIFT-PLAIN-PROSE-CHANGELOG shipped in v11.60.6.
+- Law: the same as FC-HELP-DRIFT-PLAIN-PROSE-CHANGELOG, a guard that reads nothing proves nothing and is not silenced by relaxing the assertion or by adding text to the CHANGELOG; and a window sized in sections is a rate assumption that slice-per-release cadence (3-10 per hour) breaks.
+- Cause (measured): sections v11.60.4 to v11.60.8 are plain prose naming no `loki <word>`; the plain-prose extractor is correct, the cap was the fault. The nearest section naming an invocation is within 10 sections (LOKI_HELP_DRIFT_SECTIONS=LOKI_HELP_DRIFT_WINDOW=10 gives a green real run), so a cap of 5 is red today and any larger fixed cap is red again after enough command-free releases.
+- Siblings swept: the only other section-count reader of CHANGELOG is the per-version release-notes extraction (scripts/release-notes.sh, tests/test-release-notes.sh), which selects one named version and has no window.
+- Mechanism: LOKI_HELP_DRIFT_WINDOW defaults to 1000 (the whole file). The window still widens one section at a time and stops at the nearest section that names an invocation, so only the newest invocation-bearing sections are checked. "Extraction is broken" now means no invocation anywhere in the CHANGELOG. The assertion text is unchanged.
+- Fixture: tests/test-help-changelog-drift.sh self-test: an invocation six sections down passes (red at the old cap, green now) and a CHANGELOG with no invocation anywhere still reports broken extraction.
+
 ## FC-COMMIT-STAGES-USER-UNTRACKED A commit publishes the user's untracked files that were present before the run (FC-42 family)
 - Law: only what the run changed is published; a pre-run user file the run left untouched is never staged into a Loki commit (the same rule dropSet already applies to pre-run tracked dirt).
 - Cause (measured, #353 CW-18 test): intake records preexisting_untracked_blobs for every untracked file, but only discardIfSatisfied read it. The commit stage and the supervisor backstop run `git add -A` and dropSet excluded only untouched pre-run tracked dirt, so a normal VERIFIED run committed the user's untracked notes.
@@ -1616,3 +1624,12 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept: every other `process.env` spawn in providers/ is already listed with a reason (claude_flags.ts, runner/providers.ts) or token-free; mcp_config.ts is the only unlisted one (guard output).
 - Mechanism: spawn through `tokenFreeEnv(process.env)` (util/safe_git.ts), the shared scoped env builder.
 - Fixture: tests/providers/mcp_config.test.ts runs a fake `cline` that records GH_TOKEN, GITHUB_TOKEN and SSH_AUTH_SOCK with canary values set in the parent; red with `env: process.env` (restored in the mutant run), green with tokenFreeEnv. The full_env_spawn_guard goes red on the same mutant.
+
+
+## FC-WALL-FILE-WITHOUT-RUNNER-SILENTLY-DROPPED A sealed Wall file that no runner of the repo can run was dropped from verify, named nowhere, and the receipt still said wall.passed true
+- User-visible vs raw: user-visible. A Wall of `loki_wall_a_test.py` plus `loki_wall_b.rs` (or `.java`, `.rb`) verified with `wall_passed: true` and an empty `not_proven`; the second acceptance test was sealed read-only and never executed.
+- Law: a sealed Wall file is either executed and passing, or named NOT PROVEN; a proof never covers a file it did not run.
+- Cause (measured): wall.ts guessRunner returns null for any extension other than `.py`, `.go` and the repo's JS/TS runner, so the file was sealed but left out of wallTests and out of not_run_files; verify.ts built wallTests from `map.tests` filtered by the sealed paths, so a path with no test entry vanished, and wall_passed was computed only over the checks that ran.
+- Siblings swept: every extension guessRunner refuses (`.rs`, `.java`, `.rb`, `.php`, `.cs`, a JS file with no JS runner detected), a `.py` or JS Wall file the verify test map does not list (same drop in verify), the all-dropped Wall (wall_passed stays unset, never true), publishableWall (requires an executed passing target check, so a dropped file is never published; it is now named in not_proven instead of vanishing), holdout checks (unchanged, they come from a separate store).
+- Mechanism: one wording, `NO_RUNNER_REASON` in util/check_result.ts. wall.ts adds each sealed file without a runner to `not_run_files` (seal.ts already turns those into `Wall test not executed: <file>: <reason>`); verify.ts adds the same line to `not_proven` for every sealed path missing from wallTests and refuses `wall_passed: true` while any is missing (a failing check still gives false). Seal's set dedups the identical text.
+- Fixture: tests/engine10/verify.test.ts "FC-WALL-FILE-WITHOUT-RUNNER-SILENTLY-DROPPED" (mixed runnable plus `.java` is not a bare true, all-dropped is unset, the runnable-only control stays true with no such line) and the extended tests/engine10/wall.test.ts "a sealed file whose runner cannot be guessed" (the `.rb` is named, the `.py` is not). Mutants: dropping the wall_passed guard, dropping the not_proven push, and dropping the not_run_files push each turn the matching test red.