loki-mode 11.60.3 → 11.60.5

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

package/VERSION

@@ -1 +1 @@
-11.60.3
+11.60.5

package/dashboard/__init__.py

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

@@ -1576,3 +1576,11 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Mechanism: one line in FIXED_RULES (cache-stable lead of the implement brief) naming the exact invocation and forbidding files or links under tests/ to satisfy imports.
 - Fixture: tests/e10ext/full_job_brief.test.ts "FC-PYTEST-IMPORT-SYMLINK-UNDER-TESTS" and the implement-brief golden.
 - Open: confirm by grepping the loki implement transcripts of the fd-1 and fd-4 grid trials for `ln -s` and bare `pytest` (eng-303c); update this row with the result. Not covered: an agent that links anyway is still only flagged, not blocked.
+
+## FC-SHARD-WATCHLIST-STALE The shard-coverage guard hardcoded which five suites are the heaviest; the table moved on, and one new registration shifted LPT tie rotation and turned main red
+- User-visible vs raw: raw (CI guard). tests/test-shard-coverage.sh T5 failed on main: "expected 5 watched suites in 5 distinct shards", with trust-core tests and E2e Features both in shard 1. It is also a misleading signal, because no shard was unbalanced.
+- Law: a guard asserts the property that holds by construction, over inputs derived from the live data, never over a name list that was true on one date.
+- Cause (measured): bisected across the four commits that touched the runner or the table. 54700a30b: 0 failures; 71b292af4 (registers npm-dist-tags.sh with no duration row): 1 failure; 4b880492b and 77f1196c5: 1 failure. The hardcoded watch list held "E2e Features" (20s in the table) and "Review deadline, ..." (45s), which stopped being among the five heaviest long ago (ShellCheck 140, trust-core 130, reachability 95, Quick receipt order 90, v10 ops 70). They only separated by tie rotation, and the new registration moved the rotation. LPT guarantees the heaviest n suites land in n distinct shards; light suites carry no such guarantee.
+- Siblings swept: test-shard-durations-drift.sh failed on the same commit for the same missing row (npm-dist-tags.sh); fixed with a measured row (8s). T1 to T4 do not name suites.
+- Mechanism: T5 derives its five suites from tests/shard-durations.tsv, restricted to registered names, sorted by seconds descending.
+- Fixture: tests/test-shard-coverage.sh T5. Executed mutation: replacing the runner's `shardof[idx] = pick` with `idx % 2` turns T5 red (and the empty-shard checks).

package/docs/v10/PROGRESS.md

@@ -2732,3 +2732,4 @@ v11.17.21 published (Release success on 462fbc40a; npm latest 11.17.21, next 11.
 - bun test survives SIGTERM: 3 engine10 runs under bare `timeout 590` lived 28-50 min. Rule now: `timeout -k 15 <s>`, at most 2 full engine10 runs company-wide.
 - Wall mechanism: a single one lands. eng-cw12 a1c07ce3c is the base. eng-314f splits bed40cfb4 into A (fullSuiteCmd plus seal wording) and B (rev-c rules B covered or delta).
 - Roadmap-100: lanes defined by arch-100, one live slice per hot-spot file. None of the 100 items has shipped yet.
+- 06:39Z: 11.60.1 tgz 200 (publish 06:30:51, so 4-8 min lag, variable). dist-tag ls latest=next=11.60.1. 11.59.0 version doc /loki-mode/11.59.0 returns 200, signed, shasum 71ae74c5; its tgz and `npm pack loki-mode@11.59.0` still 404. Not called lost. Interim rule: no VERSION push until the previous tgz is 200.