loki-mode 11.17.92 → 11.17.93

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

package/VERSION

@@ -1 +1 @@
-11.17.92
+11.17.93

package/dashboard/__init__.py

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

@@ -1281,6 +1281,11 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Mechanism: `strayInTestDir` in phantomRepoPaths additionally reports a path that stays inside the test dir when its first segment is absent from the test dir but present at the package or repo root (the author meant a repo path). Same exemptions (plan with parent, created, ignored by the VCS, write/expect/tmp lines); fixtures the test dir lacks (fixtures/a.json) and __self__ stay unreported.
 - Fixture: fc23_wall_conventions.test.ts "in-testdir phantom" (incident lines report tests/plugins/ralph-loop; plan-named, fixtures, created and __self__ paths pass). Red before the fix, green after.
 - Siblings swept (review of 11.17.85): the package-root fallback trusts a known project model fully (its package cwd, else the repo root) and otherwise walks up to the nearest manifest-shaped JSON (string name plus another key); config files (tsconfig, linter, test-runner, xml, cfg, toml) are never roots, so they cannot hide a real phantom (fixture "fallback no false root"). Known limit: a nameless manifest or a non-JSON-manifest package resolves only through the model; without one the repo root is the cwd. The vendor-dir exemption is the ignore check alone, with no vendor-dir name or `*_modules` pattern, so src/my_modules/x and src/feature_modules/x are reported (fixture "modules dir phantom"). The release-gate pytest guard strips only the pip install segment before checking (tests/test-release-gate-dedup.sh M10).
+- Sibling note (walk-up base, run e10-20261019T121849Z-848d, #81826 rerun): the Wall found the plugin with `for (const start of [process.cwd(), import.meta.dir]) { let dir = resolve(start); while (true) { const candidate = join(dir, 'plugins', 'ralph-loop'); ... dir = dirname(dir) } }` and threw 'plugins/ralph-loop not found'; the repo has plugins/ralph-wiggum. Raw: the loop variable is unresolved, so phantomRepoPaths evaluated nothing, no re-ask ran, the implementer could not touch the Wall test and the run sealed SPEC_CONFLICT.
+- Law: same as above; a repo path the Wall invents is corrected up front, however the base directory is reached.
+- Siblings swept: the only place that dropped unresolved bases is `ev` in phantomRepoPaths; outOfRepoTarget and seal's addedSymlinkNotes build no paths. Error-message literals like 'plugins/ralph-loop' are not path construction and are never evidence.
+- Mechanism: in phantomRepoPaths a `for (const X of [items])` makes X, and `let dir = resolve(X)`, a walk-up base only when every item evaluates to the cwd or the test directory (process.cwd(), import.meta.dir, __dirname or a const bound to them); repo-relative strings and join(...) items leave X unresolved, as before. A join/resolve on a walk-up base with literal segments is reported when its first literal segment exists at the package or repo root and the full path is missing at every directory the walk passes through: the test dir, the package root and the repo root, and each parent between them and the repo root. A path found at any of those directories is real and is not reported. A first segment absent everywhere stays silent as before; paths built on a walk-up base never use the escape rule, and nested joins on a candidate are not double reported. Temp and mkdtemp bases never resolve and stay unflagged; plan, created and ignored exemptions are unchanged.
+- Fixture: fc23_wall_conventions.test.ts "walk-up phantom" (the real Wall shape reports plugins/ralph-loop; ralph-wiggum, plan-named, absent first segment, mkdtemp and tmpdir bases give []; HIGH review block fixtures FP-A repo-relative string loop, FP-B join on cwd loop, FP-C several joins loop, FP-D2 walk-up whose file exists on the way up all give []). Red before the fix, green after.
 
 ## FC-MEDIUM-REVIEWER-UNCREDITED The medium tier selects "one reviewer", nothing on the default path runs or credits it, so every medium run lists it NOT PROVEN and seals PARTIAL
 - User-visible vs raw: user-visible. A real run on anthropics/claude-code#81826 (v11.17.83, risk tier medium) listed "one reviewer" under NOT PROVEN.

package/docs/v10/PROGRESS.md

@@ -2650,3 +2650,6 @@ v11.17.21 published (Release success on 462fbc40a; npm latest 11.17.21, next 11.
 
 ## 2026-10-19T12:12Z (CoS) v11.17.92
 - 11.17.92: medium default same-vendor review (FC-MEDIUM-REVIEWER-UNCREDITED sibling) d40a36677+378bfa1c6+7822aafeb as r3 2abb45519. HIGH APPROVE round 3 after two BLOCKs (seal 60s limit; group kill + backstop clamp). Case D replay: receipt not_run in 5227ms, no orphan. Gates 436/0 (11 files), never_below_raw+l0_guard 19/0, spawn env guards 7/0, tsc clean (control-plane filtered). Follow-ups: bounded pipe drain for setsid grandchild (P2), Number.isFinite guard on roomS.
+
+## 2026-10-19T12:36Z (CoS) v11.17.93
+- 11.17.93: FC-WALL-PHANTOM-PATH walk-up sibling, 4d7b7abf4 + 1de873678 (cherry-picks of 09fef8ead, 3e2b7b492). HIGH opus review round 1 BLOCK (FP-A..D2 reproduced), round 2 APPROVE: gate 210/0 + tests/util 461/0, tsc 0 non-control-plane, 3 mutations red. Field case run e10-20261019T121849Z-848d reports plugins/ralph-loop.