loki-mode 11.67.10 → 11.67.12

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

package/VERSION

@@ -1 +1 @@
-11.67.10
+11.67.12

package/autonomy/loki

@@ -2614,10 +2614,11 @@ _loki_start_optval_consumes() { [[ -n "${1:-}" && "${1:-}" != --* ]]; }
 # Same message and exit code as the cmd_start parser's catch-all arm.
 _loki_start_unknown_flag() { echo -e "${RED}Unknown option: $1${NC}"; exit 64; }
 
-# One exit-code mapping for an engine10 resume, shared by cmd_resume and
-# `loki start --resume`. 0 and 4 (phase reported) -> 0, 5 (publish failed) -> 1.
+# Exit-code mapping for the engine10 resume REPORTER, used only by cmd_resume.
+# 0 and 4 (phase reported) -> 0, 5 (publish failed) -> 1. `loki start --resume`
+# runs the stage resume (engine10 --resume) and returns its code unchanged.
 # Sets _LOKI_E10_RC and returns 0 when handled; any other code returns 1 with
-# _LOKI_E10_RC set to the raw code (cmd_resume falls through, start returns it).
+# _LOKI_E10_RC set to the raw code (cmd_resume falls through).
 _loki_e10_resume_map() {
     case "$1" in
         0 | 4) _LOKI_E10_RC=0 ;;

package/dashboard/__init__.py

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

@@ -1434,6 +1434,10 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Sibling (engine10 cache): closed by #331, see FC-ENGINE10-CACHE-KEY-NOT-PRODUCER-BOUND.
 - Fixture: tests/mcp/test_phase1_tools.py test_stored_text_appears_only_inside_untrusted_content (red with loki_verify_fast trusted: leaks ['loki_verify_fast']; green after) and tests/test-fast-verify.sh CACHE BINDING block (planted repo-local and forged-MAC empty-list entries; red when the MAC check is replaced by `if False:`, green with it), plus the CACHE KEY and CACHE FILES blocks there: a test-path file moved to a product path must FAIL (red when the path is dropped from cache_key), a copy of fast_verify.py with disabled rules must not poison the real rules' cache (red when PRODUCER is a fixed string), the key and cache json are 0600 and the dir 0700 (red when the key is written 0666), and no verify cache file appears in a repo (red when cache_path points at root/.loki/cache/fast-verify.json). Tests that run fast_verify set LOKI_FAST_VERIFY_CACHE_DIR to a run tmp or pass --no-cache, never the real ~/.loki.
 
+- Recurrence 2026-10-23 (RQ-102, founder-reported): all 12 release runs from v11.66.1 to v11.67.9 failed publish-npm on the 8x15s settle loop of scripts/npm-dist-tags.sh ("dist-tags did not settle on the highest version after 8 tries", run 39938698648), and verify-npm-registry has `needs: publish-npm`, so a failed publish job SKIPPED the only converge step. At 12:58Z latest=11.67.8 next=11.67.9 (npm dist-tag ls and the uncached packument agree; packument modified 10:29:12Z, a late 11.67.8 latest write with no re-assert for 2.5 h). Cause: the settle window (about 2 min) is shorter than the measured registry lag (4 to 11 min), and the converge job was gated on the very step that fails. Same shape for publish-ts-sdk and verify-sdk-registry.
+- Mechanism (one owner, D86): publish-npm owns the upload and one best-effort tag write (LOKI_DISTTAG_TRIES=2, failure is a ::warning, an upload failure stays fatal). verify-npm-registry owns convergence and the red signal: `if: !cancelled() && needs.publish-npm.result != 'skipped'` (a cancelled run stops it; a skipped publish uploaded nothing), it first proves the registry serves the version, then converges with LOKI_DISTTAG_TRIES=50 and LOKI_DISTTAG_SLEEP=15 (at least 12.5 min). Red only if the tags never settle. The SDK pair has the same shape. npm-dist-tags.sh and its never-below-max logic are unchanged.
+- Fixture: tests/test-npm-dist-tags.sh structural cases on .github/workflows/release.yml (verify jobs gate on !cancelled() and not skipped, with always() absent; publish tag step is non-fatal; converge window at least 720 s and timeout at least 40). Mutation: each of these goes red alone: `needs`-only gating, always() gating, a fatal tag call, a dropped TRIES, a short timeout, on both the npm and SDK pairs.
+
 ## FC-CATALOG-CAPABILITY-DRIFT-UNCHECKED A catalog entry whose capabilities drifted from the API failed only at request time
 - User-visible: a catalog entry whose thinking types or effort levels drifted from what the model accepts fails only at request time, as an API error mid-run. Raw: the catalog (providers/model_catalog.json) is static and never compared with models.retrieve.
 - Law broken: a capability the harness relies on is claimed without being checked against its source of truth.
@@ -1939,3 +1943,11 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Mechanism: bench adapters register in SCOPED_OUT when added. The layout test copy set follows the compiler's declared dependencies (pd/303d, not this row).
 - Fixture: claude_flags.test.ts "P12-26b" goes red for any new unlisted benchmarks/ file carrying the flag.
 - Open: the dist-layout half (secret-paths.json copy) is owned by pd/303d 1be1e118d.
+
+## FC-VERIFY-PATH-REROOTED-UNDER-RUNS A `loki verify` argument that is a path to a missing receipt was treated as a run id, so the error named a path that never existed
+- User-visible vs raw: user-visible. `loki verify .loki/runs/e10-nope/receipt.json` printed `receipt not found: .loki/runs/.loki/runs/e10-nope/receipt.json/receipt.json`.
+- Law: a path the user typed is reported as given; the reporter never invents a location.
+- Cause (measured): engine10/verify_cmd.ts treated only an EXISTING file as a path, so a missing one fell through to `join(runsRoot, runId, "receipt.json")`.
+- Siblings swept: run id form (unchanged), absolute path, a receipt copied elsewhere, a non-receipt .json (diff verifier).
+- Mechanism: an argument containing a path separator or ending in .json is a path whether or not the file exists.
+- Fixture: tests/test-verify-receipt-route.sh "a missing receipt at a run path is UNCHECKED rc 2 with the path as given" (red before, green after).