loki-mode 11.17.76 → 11.17.78

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

package/VERSION

@@ -1 +1 @@
-11.17.76
+11.17.78

package/dashboard/__init__.py

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

@@ -1222,3 +1222,11 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept (every `failIds(` and test-output-parsing `run(` under loki-ts/src, all checked): package_suite.ts runPackageSuites (fixed), engine10/stages/deep.ts runFullSuite (fixed), runner/repo_profile.ts shellRunner (already plainTestEnv + stripAnsi), engine10/stages/verify.ts runOnce (plainTestEnv + stripAnsi, FC-69) and its base rerun failIds at subtractBase (consumes runOnce output), runner/load_owner.ts runOnBase (plainTestEnv + stripAnsi), engine10/stages/wall.ts (plainTestEnv + stripAnsi), runner/quality_gates.ts npm test run (summaryFailedCount strips ANSI itself; no ids parsed). The remaining `run(` sites (python, doctor, proof, status, provider, supply, speed) do not parse test output.
 - Mechanism: one `suiteEnv(path)` (plainTestEnv plus the caller's PATH override) for both full-suite runners; ANSI stripped at capture before harnessLoadReason, classifyCheck and failIds; `failIds` strips ANSI itself (idempotent) so no caller can regress; attributeFullSuite says "head failure ids unparseable" instead of "none of the failing checks match them" when a failing check has no parsed ids against an attributable baseline (still blocking, fail-closed); a full-suite failure carries a redacted bounded `failureExcerpt` into the existing verify `excerpts` map, so the fix brief shows failure text.
 - Fixture: loki-ts/tests/engine10/verify_prered.test.ts "FC-FULLSUITE-ANSI-IDS" (colored vitest transcript), loki-ts/tests/engine10/monorepo_cwd.test.ts (colored failing package run keeps ids and a redacted excerpt; child runs under FORCE_COLOR=0 NO_COLOR=1), loki-ts/tests/runner/harness_intelligence.test.ts (colored head excused against a plain superset baseline, colored new ids still block, unparseable ids named, excerpt in the brief). Red before the fix, green after.
+
+## FC-WALL-OUT-OF-REPO-TARGET A Wall check resolved the code under test from an installed copy outside the repo, so the implementer edited runner config and the run ended PARTIAL (WALL-OUT-OF-REPO-TARGET)
+- User-visible vs raw: user-visible. `loki start anthropics/claude-code#81826` on loki 11.17.76 ended PARTIAL with a runner-config tampering flag. Raw: the Wall test's target was `process.env.X ?? join(homedir(), '.claude/plugins/.../name')`, an installed copy, while the change lives in the repo; the implementer added bunfig.toml and a preload to redirect the env var.
+- Law: a Wall check exercises the repo's own code on the tree under change; it never needs runner config to reach it.
+- Cause (measured): the Wall writer prompt never said to use repo-relative paths and no validation looked at where a Wall file resolves its target.
+- Siblings swept: Wall author (fixed); implement brief repro-test line (implementer-written tests are not statically checked; with an in-repo Wall the implementer has no reason to touch runner config); fix and plan stages write no tests.
+- Mechanism: one `outOfRepoTarget` detector in project_model/conventions.ts (homedir, Path.home, $HOME, ~/, absolute /Users|/home|/root; comments ignored); wallAuthor re-asks once with the precise reason, a file still failing is discarded (sealed copy only, listed in `discarded`); one sentence in the cache-stable Wall brief.
+- Fixture: loki-ts/tests/engine10/fc23_wall_conventions.test.ts describe "FC-WALL-OUT-OF-REPO-TARGET" (rejected, re-asked, discarded; repo-relative and tmpdir pass). Red before the fix, green after.

package/docs/v10/PROGRESS.md

@@ -2602,3 +2602,9 @@ v11.17.21 published (Release success on 462fbc40a; npm latest 11.17.21, next 11.
 
 ## 2026-10-19T05:27Z (CoS) v11.17.76
 - 11.17.76: FC-FULLSUITE-ANSI-IDS. Diagnosed on FireLater#20 run e10-20261019T045437Z-7939 (base 156 fails, head 150, 0 new; failIds raw 0 vs stripped 296/307). Engineer b9767d997 red-then-green 5 tests; HIGH review APPROVE (190/0, mutation removing stripAnsi turns 2 tests red). Main after cherry-pick 9944bc030: 83/0 on 4 touched suites.
+
+## 2026-10-19T06:34Z (CoS) v11.17.77
+- 11.17.77: FC-WALL-OUT-OF-REPO-TARGET. Diagnosed on anthropics/claude-code#81826 run e10-20261019T061221Z-ec31 (11.17.76 PARTIAL: Wall targeted ~/.claude/plugins ralph-loop, implementer added bunfig.toml preload). Engineer 1a5c55790+a38987338; HIGH review BLOCK (sizing cap, prefix placement, 5 false positives) then APPROVE 199/0 across 13 files.
+
+## 2026-10-19T06:50Z (CoS) v11.17.78
+- 11.17.78: main CI guard fixes (L0 project_model names, never_below_raw AST matcher, M1 anchor, modernize producer scan). Engineer chain 21187a2c7..9e17b7f75; HIGH review BLOCK x4 then APPROVE (134/0, 23 parent shapes still caught + 7 new, shipped source zero violations).