loki-mode 11.17.61 → 11.17.63

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

package/VERSION

@@ -1 +1 @@
-11.17.61
+11.17.63

package/dashboard/__init__.py

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

@@ -1122,5 +1122,26 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - User-visible vs raw: user-visible. A rerun of `loki start anthropics/claude-code#21527` after FC-ISSUE-FOREIGN-REPO ended BLOCKED (SPEC_CONFLICT, 0 files changed) yet pushed an empty branch to the operator's fork (NOT PROVEN: "PR not opened: fork-only: pushed ..."), logged the skipped status comment as ok, spent two more fix rounds (one on opus) after the implement session had already declared the conflict, and printed a Reason with two model messages joined mid-word ("has shippedI still").
 - Law broken: a run publishes only what it changed, and its result reads as one honest line; spend stops once the outcome is decided.
 - Siblings: the supervisor PR gate (net diff computed only for FAILED, so SPEC_CONFLICT, PARTIAL and VERIFIED skipped it), the status projector and backstop comment (a skip read as a post), session marker parsing (LOKI_SPEC_CONFLICT and LOKI_ALREADY_DONE both line-anchored on glued text), the fix loop (E-98b keeps verifying a single conflict claim, but a fix session confirming it with an unchanged tree was not treated as confirmation).
-- Mechanism: one net-diff check for every verdict gates every push; the push script reports a skipped comment on stdout and callers record it; session text blocks are newline-separated before marker parsing; a fix round that also exits spec_conflict on an unchanged tree ends the loop with the SPEC_CONFLICT verdict.
+- Mechanism: one net-diff check for every verdict gates every push; the push script reports a skipped comment on stdout and callers record it; session text blocks are newline-separated before marker parsing; a fix round that also exits spec_conflict on an unchanged tree ended the loop (superseded by FC-FIX-OVER-CONFLICT: no fix round runs at all after implement declares the conflict).
 - Fixture: supervisor no-diff SPEC_CONFLICT case (no push), tests/test-engine10-push.sh skipped-comment line, session two-block marker case, machine confirmed-conflict case.
+
+## FC-LOKI-DIR-DIRT A repo that committed Loki's own .loki/ state could never start a run once that state was removed (LOKI-DIR-DIRT)
+- User-visible vs raw: user-visible. `loki start asklokesh/FireLater#20` ended FAILED in 1s with "dirty tracked tree: D .loki/CONTINUITY.md, D .loki/STATUS.txt, ...": the repo tracks four legacy-engine state files, the operator had cleared .loki/ by hand (shell history), and every later run refused to start (the same failure hit #17 on 2026-10-04).
+- Law broken: Loki's own state is never the operator's change; a run is blocked only by the operator's files.
+- Siblings: intake's dirty check (the only consumer of tracked-tree status before the run branch); every later stage already excludes .loki (the diff pathspec ':(exclude).loki', info/exclude, commit staging), so only intake disagreed.
+- Mechanism: intake's dirtyTrackedFiles drops any status line whose paths are all under .loki/, rename sides included; the commit stage keeps excluding them, so the run never commits or reverts those deletions.
+- Fixture: loki-ts/tests/engine10/intake.test.ts FC-LOKI-DIR-DIRT (red: the exact reported reason; green: intake completes and the run's commit names only README.md).
+
+## FC-VACUOUS-WALL-GREEN A Wall test that already passed on base was sealed as ALREADY_SATISFIED for a feature the repo does not have (VACUOUS-WALL-GREEN)
+- User-visible vs raw: user-visible. `loki start anthropics/claude-code#21527` (GitLab support for a hosted Slack integration) on 11.17.61 ended ALREADY_SATISFIED for $0.09 and posted "already satisfied" on the upstream issue. The Wall test it sealed asserted only things the base tree already had (5/5 pass on base, run a97b events wall base_run pass 1 fail 0), so a green-on-base result became the claim itself.
+- Law broken: ALREADY_SATISFIED needs evidence the requested behavior exists; a test that passes before any change proves only that the test is weak.
+- Siblings: seal verdictOf (green-on-base alone returned ALREADY_SATISFIED), discard alreadySatisfied (same three-way OR), the Wall installer (set already_satisfied on intake output, short-circuiting implement), runWall reauthor (kept: a green-on-base test is still reauthored once).
+- Mechanism: green on base is recorded as `green_on_base` proof only; the claim comes from exactly two sources, intake's evidence-cited already-done check or implement's LOKI_ALREADY_DONE, and seal still requires proof for either. One rule in seal and discard.
+- Fixture: loki-ts/tests/engine10/wall.test.ts green-on-base cases (red: ALREADY_SATISFIED with no claim; green: implement runs) and check_result.test.ts "verdict gate" FC-VACUOUS-WALL-GREEN case (a changed tree on a Wall green on base caps at PARTIAL with NOT PROVEN "Wall green on base: no Wall test discriminates the change"; the Wall proves only an intake or implement claim).
+
+## FC-FIX-OVER-CONFLICT A fix round papered over a declared spec conflict with documentation for a behavior the code does not have (FIX-OVER-CONFLICT)
+- User-visible vs raw: user-visible. On 11.17.62 the same #21527 run had implement declare LOKI_SPEC_CONFLICT twice (the feature lives in a hosted service, not that repo); verify then failed, fix round 1 wrote a CHANGELOG line and a README section announcing GitLab support, verify passed, and the commit was pushed to the operator's fork (run fdfc, commit 980a166) under a SPEC_CONFLICT seal.
+- Law broken: once implement declares the task conflicts with the repository, spend stops and nothing may be written to satisfy the check; docs never substitute for missing code.
+- Siblings: the machine fix loop (ran on any failing verify regardless of implement.exit), the 11.17.61 confirmation rule in the loop (required a second conflict claim from fix; removed), fix stage output spec_conflict (only consumer was that rule; removed), the implement/fix briefs (context.ts FIXED_RULES) and the shared stage prefix (lean_prefix.ts) that plan, wall and implement read.
+- Mechanism: the fix loop condition stops when implement.exit is spec_conflict (verify still runs once, E-98b); FIXED_RULES and the stage prefix forbid docs, changelog or README text announcing behavior the code lacks and direct the agent to LOKI_SPEC_CONFLICT. The A-110/E-67 draft PR for a conflict with real implement work is kept.
+- Fixture: loki-ts/tests/engine10/machine.test.ts E-98b case (one verify, no fix round; red on the old loop), implement brief and spec-first goldens re-captured.

package/docs/v10/PROGRESS.md

@@ -2557,3 +2557,9 @@ v11.17.21 published (Release success on 462fbc40a; npm latest 11.17.21, next 11.
 
 ## 2026-10-18T20:30Z (CoS) v11.17.61
 - P1 FC-NO-DIFF-PUBLISH (anthropics/claude-code#21527 rerun): empty fork push, skipped comment logged ok, glued reason, extra fix rounds. Slices P1-AD (551267ec5) and P1-C (8fcc1315b) merged. Checks: tsc clean (control-plane excluded); bun test budget, supervisor_backstop, machine, sdk_stream_parser, spawn_env_guard, contract 192 pass 0 fail; e2e, issue_ref_e2e, already_done, pr, tests/util 571 tests 0 fail; test-engine10-push.sh 85 passed 0 failed; sigpipe 4 passed; select-tests 119 passed.
+
+## 2026-10-18T20:38Z (CoS) v11.17.62
+- FC-LOKI-DIR-DIRT (asklokesh/FireLater#20): intake blocked on deleted tracked .loki/ legacy files; deleter traced to manual rm in shell history, not Loki (scratch-clone repro on 11.17.60 left them intact). Fix in intake dirtyTrackedFiles. Checks: intake + budget 82 pass 0 fail (new test red first with the exact reported reason); tsc clean (control-plane excluded); e2e, supervisor_backstop, seal, spawn_env_guard, contract, e10ext 380 pass 0 fail.
+
+## 2026-10-18T21:32Z (CoS) v11.17.63
+- FC-VACUOUS-WALL-GREEN + FC-FIX-OVER-CONFLICT (anthropics/claude-code#21527). HIGH review (review-21527) BLOCK B1 (green-on-base Wall counted as VERIFIED proof) fixed, re-review APPROVE: 430 pass 0 fail across check_result/seal/wall/machine/wall_concurrent/already_done/verify/discard_proto/budget, tsc 0. Full suite shards aa-ad + ae1 0 fail (ae1 723 pass); route_matrix rerun pending (timed out together, fix-forward signal). CI-only guards help-drift/sigpipe/select-tests rc=0.