loki-mode 11.55.0 → 11.55.2

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

package/VERSION

@@ -1 +1 @@
-11.55.0
+11.55.2

package/dashboard/__init__.py

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

@@ -1432,3 +1432,14 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept: effortForTier clamp (bash and Bun, parity-checked), claudeEffortLevels, the catalog freshness row (age only, offline).
 - Mechanism: loki doctor "Model capabilities" row. With ANTHROPIC_API_KEY it calls models.retrieve per claude catalog id and prints each mismatch (effort levels, API-expressible thinking types); without a key or offline it warns and never changes the tally or exit code. The bench runner takes --effort sweep, expanding to the catalog levels for --model.
 - Fixture: loki-ts/tests/commands/doctor.test.ts "model capability row", tests/test_bench_runner.py sweep tests, tests/test-bash-bun-parity.sh effort clamp cells. Red when the comparison, the sweep catalog read or the clamp model argument is removed.
+
+- Mechanism: run_group sets base = baseRef on every non-fix unit before writing dag.json, so dispatch and the journal key use the same value. The adoption is further bound to the signed task sha256, the unit branch tip and the verified receipt. #317b: task.sha256 covers items only, so the receipt also signs unit_spec.sha256 (unitSpecSha256 in unit_mode.ts over id, items, acceptance, writeSet, base), written by the seal stage and recomputed by adoptJournaled from the same function; an absent, empty or mismatched value rejects the adoption. No time bound is needed: a key that names the base and card never matches work built on another base, and a moved base misses.
+- Fixture: loki-ts/tests/engine10/seal_group.test.ts "#317: local HEAD ahead of origin/HEAD, every unit starts at the journal-key base". Red before the fix (unit base undefined), green after. #317b fixtures: "a colliding key whose signed unit spec has a different acceptance is not adopted" and "a receipt with no signed unit_spec is not adopted", red with the spec check removed or acceptance left out of the hash.
+
+## FC-TEST-TIMEOUT-OVERRIDES-CLI A file-level setDefaultTimeout(30_000) overrides the bun test --timeout flag and ignores machine load, so a slow-but-correct test fails on a busy host
+- User-visible vs raw: user-visible to every engineer and release gate. `runAutonomous > repo profile cache hit` failed at 30.1s on origin/main at load average 28 on 14 cores, both with `--timeout 30000` and with `--timeout 120000`. The same test passed with the literal raised to 240_000 (87s wall, including startup).
+- Law: a test's time budget scales with the load of the machine it runs on, and the operator has an env knob that always works; a flake is a missing scale, not a reason to retry. bun test does not expose `--timeout` to the process (argv, Bun.argv and execArgv were probed under `bun test --timeout 777777`: argv=[bun, file]), so the knob is an env var, not the CLI flag.
+- Cause (measured): 14 test files call `setDefaultTimeout(N)` with a fixed literal (10 at 30_000, 3 at 130_000, 1 at 60_000; count: `git grep -n 'setLoadAwareTimeout(' -- loki-ts/tests` after the change, `git grep -n 'setDefaultTimeout(' fff00b1da^ -- loki-ts/tests` before), and a file-level call wins over the CLI flag.
+- Siblings swept: all 14 literals in loki-ts/tests, replaced in one change; per-test `, N)` timeouts are explicit single-test budgets and are not in this class.
+- Mechanism: loki-ts/tests/preload.ts exports `setLoadAwareTimeout(baseMs)`: baseMs times clamp(ceil(2 * loadavg1 / cpus), 1, 10). `LOKI_TEST_TIMEOUT_SCALE` (positive number, capped at 10) replaces the factor; `LOKI_TEST_TIMEOUT_MS` is a floor that wins when larger. A guard in loki-ts/tests/util fails on any direct `setDefaultTimeout(` call in tests.
+- Fixture: loki-ts/tests/util/test_timeout_guard.test.ts tests FC-TEST-TIMEOUT-OVERRIDES-CLI, including a subprocess run through the real setLoadAwareTimeout path (env knob lifts the budget, a real hang still times out).