loki-mode 11.66.0 → 11.66.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.66.0
+# Loki Mode v11.66.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.66.0 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.66.2 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.66.0
+11.66.2

package/dashboard/__init__.py

@@ -7,6 +7,6 @@ Modules:
     control: Session control helpers (status, atomic writes, origin check)
 """
 
-__version__ = "11.66.0"
+__version__ = "11.66.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.66.0. Do not edit by hand.
+Generated from `loki-ts/src/cli/registry.ts` by `scripts/generate-stale-zero.sh` for v11.66.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.66.0
+**Version:** v11.66.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/dev/release-checklist.md

@@ -127,6 +127,8 @@ For a manual push (`git push origin main`), run `bash scripts/local-ci.sh` first
 npm, then creates the tag and GitHub Release, builds/pushes Docker (including `:latest`), and updates the Homebrew tap. Do not manually
 create tags.
 
+Before any release merge or push to main, run `bash scripts/release-approval-gate.sh --range origin/main..<sha>` (FC-RELEASE-UNNAMED-STACKED-PARENT): every commit in the range must be named by a `TL|HIGH|CTO|tl-x|rev-x APPROVE <sha>` line in docs/v10/BOARD.md, be rebase-equal by `git patch-id --stable`, or be an exempt clean merge or release commit; a held slice denies. Exit 1 lists each unapproved SHA with its reason, and `LOKI_RELEASE_APPROVED` does not bypass it.
+
 Before pushing the release commit, run `bash scripts/release.sh --check-clean` (E-151): it exits 1 naming any tracked file (for example a stamped `loki-ts/dist/loki.js.map`) the commit left modified; `--bump-only` prints the "stage these files:" list.
 
 ### 5. Verify ALL Distribution Channels

package/docs/v10/FAILURE-CLASSES.md

@@ -1882,3 +1882,19 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept (`grep -n "group:" docs/examples/loki-issue-to-pr.yml.example`): four jobs carry a group; only the two publish jobs shared one.
 - Mechanism: the stub records its subcommand and the tests require `reseal` for fix and `explain` for explain; groups are now `loki-issue-`, `loki-issue-publish-`, `loki-pr-fix-`, `loki-pr-publish-`, and a guard requires four distinct groups.
 - Fixture: tests/test-issue-to-pr-action.sh; mutants: drop `SUB="reseal"` (2 failures), make the publish group equal the agent group (guard red).
+
+## FC-RELEASE-UNNAMED-STACKED-PARENT A release merge shipped stacked parent commits that no reviewer had approved by SHA, including slices on hold, because the approval gate only checked the VERSION line (#436)
+- User-visible vs raw: users received v11.58.0 containing cw20-r2 parents e4c445b73 and 13b46699d, plus cw15/ux350/roadmap100 parents 9bf08f534, dc2e16314, 64e9f1a09 and cf177adf5, while the slice hold stood. Raw: the range held commits no TL or HIGH APPROVE line named; a rebase had also changed f8f263627 after approval.
+- Law broken: D12/D13 (a release carries only what a named reviewer approved); a hold is a block (OPERATING-MODEL.md, Release Manager).
+- Sibling sweep: scripts/release-approval-gate.sh (VERSION-only), scripts/train-cycle.sh phase_b (pushes a SHA to main), scripts/release.sh (stages release commits). Phase B is the only other push-to-main path.
+- Mechanism: one default-deny check inside scripts/release-approval-gate.sh, run on every invocation before the VERSION check: each commit is named by an approval line, rebase-equal by git patch-id --verbatim (indentation edits are content), or exempt (clean merge, release-files-only release commit whose dist files are exactly release.sh RELEASE_DIST_FILES); a held slice id denies; an approval line with no board row is denied by name (holds cannot be checked); an unreadable range exits 1, never ALLOWED. LOKI_RELEASE_APPROVED and --approve do not reach it. train-cycle.sh phase B calls the same script.
+- Fixture: tests/test-release-approval-gate.sh (stacked A,B,C; clean rebase; changed rebase; hold; exemptions; env bypass; replay 9556d6f16..8aad0307f; indentation-only rebase; bad range; 6-column parked row; dist/loki.js exempt vs dist/evil.js denied; rowless approval denied) plus one mutant per rule.
+
+## FC-FULLSUITE-GO-CARGO-IDS A Go or Rust full suite already red on base was charged to the change because failIds knew only pytest, jest, vitest and node ids (FULLSUITE-GO-CARGO-IDS)
+- User-visible vs raw: user-visible. FULL_SUITE_CMD runs `go test -json ./...` and `cargo test`, but failIds returned [] for both, and attributeFullSuite treats "no known ids" as nothing excused, so any base-red Go or Rust repo blocked the change for failures it did not cause.
+- Law broken: a failure the change did not cause is never charged to the change (same law as FC-BASELINE-PER-PACKAGE).
+- Siblings: pytest, jest, vitest and node ids (unchanged); the Rust Wall runner (FC-WALL-FILE-NOT-DISCOVERED-BY-RUNNER, guessRunner has no `.rs` mapping and cargo test takes no file argument; NOT closed here, gated on pd/wallfile merging); cargo's `--no-fail-fast` and doc-test ids.
+- Mechanism: failures.ts goCargoIds, ahead of the generic ID_LINE path. go -json: id `pkg::Test` per Action=fail with a Test, the package for a package-only fail; count is the `--- FAIL:` output lines plus package-only fails. go plain: `--- FAIL:` names plus `FAIL<TAB>pkg` lines no test explains. cargo: `test x ... FAILED` against the summed `N failed`. Every branch stays fail-closed (ids fewer than the count returns []).
+- Fixture: loki-ts/tests/engine10/verify_prered.test.ts "FC-FULLSUITE-GO-CARGO-IDS"; loki-ts/tests/runner/harness_intelligence.test.ts "FC-FULLSUITE-GO-CARGO-IDS: a go or cargo full suite red on base is excused for the same failing id, not for a new one".
+| FC-GO-PACKAGE-ID-CHANGED-FILE | A go full suite fails on base and head with a package id ("pkg" build failure or "pkg::Test") and the change edits a .go file in that package; the id excuses itself as pre-existing though the change touched the failing code | user-visible: a verdict excuses a red the change may own | Engine Law 1 (no excuse without proof): an id excuses only if no changed file maps to it | Siblings: cargo ids (closed by FC-CARGO-ID-CHANGED-CRATE below); pytest, jest, vitest ids use the changed-file substring check already | Mechanism: repo_profile.ts goIdTouched walks up from each changed .go file to its nearest go.mod (nested modules and go.work members included) and compares the id to that module path plus the file's directory below it (suffix match only when no go.mod exists); a changed go.mod or go.sum touches every package of its module (id equal to the module path or under it); a changed go.work or go.work.sum touches every go id; attributeFullSuite eligibility requires !goIdTouched and the line gains "NOT PROVEN: package <p> did not build on base or head; its tests ran on neither" | Fixture (module-root M2 and non-.go M4 mutants): loki-ts/tests/runner/harness_intelligence.test.ts "FC-GO-PACKAGE-ID-CHANGED-FILE: the module-root package is touched only by a root .go file, and only a .go file touches a package"; also loki-ts/tests/runner/harness_intelligence.test.ts "FC-GO-PACKAGE-ID-CHANGED-FILE" (mutant dropping the check goes red) |
+| FC-CARGO-ID-CHANGED-CRATE | A cargo full suite fails on base and head with the same test id and the change edits Rust source or a manifest; the id (a module path with no crate or file) excuses itself as pre-existing though the edited crate may own it | user-visible: a verdict excuses a red the change may own | Engine Law 1 (no excuse without proof): fail closed when the id cannot be mapped to the change | Siblings: go ids (FC-GO-PACKAGE-ID-CHANGED-FILE); pytest, jest, vitest ids use the changed-file substring check | Mechanism: repo_profile.ts cargoTouched makes every failing full-suite check ineligible, whatever its command (make test and npm test wrap cargo), when any changed file is .rs, Cargo.toml, Cargo.lock or build.rs, and the line gains "NOT PROVEN: <name> may run cargo tests and the diff edits Rust source or a manifest" | Fixture: loki-ts/tests/runner/harness_intelligence.test.ts "FC-CARGO-ID-CHANGED-CRATE"; mutants: drop the cargoTouched term, or key it on the command name again (wrapper fixture goes red); walk only the root go.mod (nested-module fixture goes red); ignore go.mod and go.sum edits (module-file fixture goes red) |

package/docs/v10/GUARDS.md

@@ -880,4 +880,4 @@ previously mismarked two merged guards (S-16, S-74) as PENDING.
 
 ### 2026-10-23: release manager shipped unnamed stacked parents
 - **Incident:** rm-1 shipped unnamed stacked parents (cw20-r2 e4c445b73 13b46699d; cw15/ux350/roadmap100 parents 9bf08f534, dc2e16314, 64e9f1a09, cf177adf5). cw20-r2 shipped as v11.58.0 while a hold on that slice stood.
-- **Guard:** the approval line must name every shipped SHA and its reviewer; holds match by slice name, not SHA; a queue order is never an approval. A scripted check follows as a slice.
+- **Guard:** the approval line must name every shipped SHA and its reviewer; holds match by slice name, not SHA; a queue order is never an approval. The check is scripted: `scripts/release-approval-gate.sh` denies any range commit not named by SHA, rebase-equal by patch-id or exempt, and any commit whose slice is held; `scripts/train-cycle.sh` phase B calls it. Proof: `bash tests/test-release-approval-gate.sh` (stacked parents, clean and changed rebase, hold, exemptions, env bypass, and mutants that must go red).