loki-mode 11.0.1 → 11.0.3

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.0.1
+# Loki Mode v11.0.3
 
 **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 legacy engine, which still ships and is being removed (`loki start owner/repo#N` still routes to it; prefer `loki owner/repo#N`).
 
@@ -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.0.1 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.0.3 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.0.1
+11.0.3

package/dashboard/__init__.py

@@ -7,7 +7,7 @@ Modules:
     control: Session control API (start/stop/pause/resume)
 """
 
-__version__ = "11.0.1"
+__version__ = "11.0.3"
 
 # Expose the control app for easy import
 try:

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.0.1. Do not edit by hand.
+Generated from `loki-ts/src/cli/registry.ts` by `scripts/generate-stale-zero.sh` for v11.0.3. 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 @@
 
 The flagship product of [Autonomi](https://www.autonomi.dev/). Loki Mode is a spec-driven autonomous builder with a built-in trust layer that takes any spec to a deployed product and verifies completion with evidence (quality gates plus a completion council), not just a "done" claim. Complete installation instructions for all platforms and use cases.
 
-**Version:** v11.0.1
+**Version:** v11.0.3
 
 **Engine note:** `loki "<task>"`, `loki owner/repo#N` and `loki quick` run the Loki 10 engine. `loki start` still routes to the legacy engine, which is being removed (planned work resumes 2026-10-07); prefer `loki owner/repo#N`. See [docs/v10/GUIDE.md](v10/GUIDE.md).
 

package/docs/v10/FAILURE-CLASSES.md

@@ -312,3 +312,17 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings: every CP entry that spawns `loki` (POST /v1/start, /v1/runs, retry); every summary line that is derived without a verify event; the stale-CP restart (a CP from an old install keeps the old behavior after upgrade).
 - Mechanism: one repoRefusal check in spawn.ts (refuse `/`, HOME and non-git dirs with a human reason) that every spawn path calls; one summaryLine that reads the terminal stop event; free text goes to Ask (read-only) and never to /v1/start.
 - Fixture: packages/control-plane test for repoRefusal (HOME, `/`, non-git, real repo); the A4b summaryLine test ("The run failed before verification ran." for a FAILED run with no verify event); the A3f cleanup test with cc22 and e606 look-alikes.
+
+## FC-27 A short product brief skips the Wall because a tree-wide token looks like a named file
+- User saw: `loki start` with a one-line UI brief on a local repo (run e10-20261004T143536Z-2582) sized the task small, skipped Plan, and skipped the Wall ("small task with a relevant test"). The implementer edited test configuration, broke an existing test, and the run ended FAILED with no PR. Raw Claude Code would have kept planning against the repo instead of treating the brief as a covered one-file fix. The receipt also listed deferred deep checks, "repo not recorded" (no GitHub remote), and "playwright not resolvable"; those are separate output gaps, not this mechanism.
+- Law: L0 (the harness must not decide that an unnamed brief already names its files), L2 (sizing and the Wall are work surfaces: when the signal is not specific, keep the Wall).
+- Siblings: `selectRelevantFiles` (plan hints, decompose, implement brief context) still counts every overlapping token, on purpose. The only caller that turns that list into a skipped Wall is `speedLikelyFiles` via `hasRelevantTests` (plan.ts and wall.ts). `namedFiles` (basename in the task text) is unchanged and still lean-eligible.
+- Mechanism: one selector, `selectSpecificFiles`, drops tokens that occur in more than half the repo-map entries before scoring. `speedLikelyFiles` uses it. A distinctive symbol still selects its file. Plan hints stay on `selectRelevantFiles`.
+- Fixture: loki-ts/tests/engine10/sizing_lean.test.ts, "FC-27: a token on most paths is not a relevant test, so the Wall stays".
+
+## FC-28 A short brief skips the Wall because a common word sits inside a longer symbol
+- User saw: the same one-line brief, rerun e10-20261004T210509Z-9f4f after 11.0.2, still skipped the Wall ("small task with a relevant test") and ended FAILED with no PR. The jest failure was a different test in the same file. FC-27 only dropped tokens that hit most of the tree. A shorter word still matched as a substring of one symbol, and that one file with a test was enough to skip the Wall. Raw Claude Code does not treat a common word inside a longer name as proof the change is already covered.
+- Law: L0 (the harness must not decide that an unnamed brief already names its files), L2 (when the signal is not an exact name, keep the Wall).
+- Siblings: `selectRelevantFiles` still uses substring overlap for plan hints. `namedFiles` still matches a basename written out in the task. FC-27's half-repo drop stays on the same selector.
+- Mechanism: `selectSpecificFiles` counts a task word only when it equals a path segment or a symbol. A word inside a longer name does not. `speedLikelyFiles` is still the only caller that can skip the Wall.
+- Fixture: loki-ts/tests/engine10/sizing_lean.test.ts, "FC-28: a word inside a longer symbol is not a relevant test, so the Wall stays".