loki-mode 11.17.83 → 11.17.85

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

package/VERSION

@@ -1 +1 @@
-11.17.83
+11.17.85

package/dashboard/__init__.py

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

@@ -1228,8 +1228,9 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - 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.
+- Mechanism: one `outOfRepoTarget` detector in project_model/conventions.ts (homedir, Path.home, $HOME, ~/; comments ignored; a literal absolute path with no home-derived value does not flag, TEN-QUALITY-41; the HOME-assignment exemption covers only lines from the assignment on, TEN-QUALITY-42); 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. The detector also flags a quoted absolute home literal (/Users, /home, /root, C:\Users) that is the direct target of an import, require or source line (the installed-copy import shape), while plain string literals stay unflagged; fixture "literal import target flagged".
+- Sibling (TEN-QUALITY-44, fixed): the implement-stage repro test (LOKI_E10_REPRO=1, lean path). After the session, changed test-like files go through the same `outOfRepoTarget` (`outOfRepoTests` in project_model/conventions.ts) and one re-ask built by the shared `outOfRepoReask` text the Wall also uses. Fixture: loki-ts/tests/engine10/implement.test.ts `-t "repro test out of repo"`.
 ## FC-OUT-OF-REPO A request whose change has no target in the repository ran every stage before ending BLOCKED (OUT-OF-REPO-INTAKE)
 - User-visible vs raw: user-visible. `loki start anthropics/claude-code#21527` (a feature whose code lives in a hosted Slack/web service) on 11.17.60 to 11.17.74 spent plan, wall, implement and fix before ending BLOCKED. Raw: the plan session had nothing to name, but plan-scope.json with zero files was read as "no scope", so the flow continued into implement.
 - Law: cheap checks run before expensive stages; a run that cannot succeed says so at the first stage that knows; BLOCKED names the question, never a bare failure.

package/docs/v10/PROGRESS.md

@@ -2623,3 +2623,9 @@ v11.17.21 published (Release success on 462fbc40a; npm latest 11.17.21, next 11.
 
 ## 2026-10-19T08:48Z (CoS) v11.17.83
 - 11.17.83: FC-WALL-PHANTOM-PATH r1-r3 (298fddf96..82233dad0; HIGH APPROVE after 2 BLOCK rounds; full real #81826 Wall file against base ef7bfdc reports plugins/ralph-loop; 3 round-3 mutations each red). Main targeted 662 pass 0 fail incl budget.
+
+## 2026-10-19T09:07Z (CoS) v11.17.84
+- 11.17.84: TEN-QUALITY-41/42 (21aa567a8, TL APPROVE, 2 mutations red), TEN-QUALITY-44 (e6d010590 219cf7a7d, TL APPROVE, mutation red), TEN-QUALITY-45 merge-interaction fix (b9db7ad92, TL APPROVE, mutation red 2 tests). Main targeted 612 pass 0 fail, tsc rc=0.
+
+## 2026-10-19T10:34Z (CoS) v11.17.85
+- 11.17.85: main Tests fix-forward (red on c5358b462..6a710258f): 65259575d WF-GATE-DEDUP drift, 74862da13 app_probe docker stub, 0a897c42c L0 guard breach (MANIFESTS literal) in conventions.ts. HIGH opus APPROVE: mutations caught (gate pytest, app_probe text, L0 literal), engine10 split 761+1828 pass 0 fail, util 459/0, tsc rc=0; route_matrix_mutation unverified (timeout). Follow-ups filed: nameless-manifest fallback false phantom, \w*_modules too broad, chained pip+pytest bypass.