loki-mode 11.64.0 → 11.65.0

package/SKILL.md

@@ -3,7 +3,7 @@ name: loki-mode
 description: Runs an autonomous software factory that knows what it is supposed to deliver and proves it did, with a signed receipt. Use when the user says Loki Mode or asks to build, fix or verify software autonomously.
 ---
 
-# Loki Mode v11.64.0
+# Loki Mode v11.65.0
 
 **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.
 
@@ -476,4 +476,4 @@ Implemented, planned and deprecated items, with the version each landed in: `ski
 
 ---
 
-**v11.64.0 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.65.0 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.64.0
+11.65.0

package/dashboard/__init__.py

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

@@ -1694,6 +1694,22 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Mechanism: the P12-07n test takes an explicit 60000ms bound; no assertion changed.
 - Fixture: tests/engine10/fix_resume.test.ts P12-07n itself; it fails at 5000ms on origin/main debc7e843 under load and passes with the bound.
 
+## FC-STAGE-DIFFSTAT-CONCURRENT-WALL-NOT-MET The per-stage diff_stat is journaled for wall, implement and fix through runStage, but the concurrent wall (split) path journals none
+- User-visible vs raw: user-visible in the run replay scrubber (#422): the wall stage of a concurrent run shows its line counts as unmeasured. NOT MET, deliberately not fixed in pd/stage-diffstat.
+- Law: a value the journal cannot measure is absent, never a fabricated zero (the diff_stat key is omitted, not 0).
+- Cause: the split wall author runs beside implement and installs into a base copy, so a before/after tree window around it would report implement's changes as wall's.
+- Siblings swept: the other tree-writing stages (implement, fix, non-split wall) all go through runStage and are covered; plan, verify, commit, seal, pr and deep write no tracked files by design.
+- Mechanism (open): measure the install itself (the diff of the base copy before and after install) inside installWallJob.
+- Fixture: none yet; tests/engine10/machine.test.ts covers the covered stages only.
+
+## FC-E2E-A130-DEFAULT-TIMEOUT-UNDER-LOAD Two e2e tests fail at bun's 5000ms default at load 30 and above, on origin/main as well
+- User-visible vs raw: raw. A red test blocks the gate it runs in.
+- Law: a test that spawns the engine carries a load-aware timeout, never bun's 5000ms default (sibling of FC-FIXRESUME-LOOP-TEST-DEFAULT-TIMEOUT).
+- Cause (measured): tests/engine10/e2e.test.ts "A-130 round 2: a tampered event log is TAMPERED..." and "A-130 quiet by default..." failed at 5.1 to 6.4s on a clean origin/main worktree (d7ee510e4) at load 29 to 43; the other 9 tests in the file pass.
+- Siblings swept: not yet; every test in tests/engine10 that spawns the CLI without an explicit timeout.
+- Open question: should these use setLoadAwareTimeout from tests/preload.ts instead of a fixed bound? Not fixed in this slice.
+- Fixture: bun test tests/engine10/e2e.test.ts at load 30 or higher.
+
 ## FC-P9-DYNAMIC-IMPORT-FALSE-POSITIVE Moat case P9.allowtoken-only-fetch-callers went red on main for a dynamic import of reviewerGitEnv in cli.ts, which is not an allowToken caller
 - User-visible vs raw: raw (a red moat case on main; no user-facing message).
 - Law: allowToken reaches safeGit only from the two fetch callers (FC-25c); the guard must fail closed on anything that can hide a caller, and must not fail on code that provably cannot reach the opt-in.