loki-mode 11.67.0 → 11.67.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.67.0
+# Loki Mode v11.67.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.67.0 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.67.2 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.67.0
+11.67.2

package/dashboard/__init__.py

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

@@ -1725,6 +1725,14 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Mechanism: in the P9 AST scan, a literal `await import("...safe_git...")` is accepted only as the initializer of an object destructuring whose every element is a plain identifier property (no rest, no computed key, no string key, no nested pattern) and none of whose names is an opt-in helper. Any other dynamic or require form still flags. A destructured safeGit with allowToken is still caught by the raw allowToken grep outside the two fetch callers.
 - Fixture: tests/moat/p9-rule-of-two.sh positive controls for a rest destructure, a computed-key destructure, a renamed opt-in helper and a destructured safeGit carrying allowToken (each must be flagged), and a negative control for the real `{ reviewerGitEnv }` form (must not flag). Mutant: accept any destructure shape; the rest and computed controls must go red.
 
+## FC-MERGED-SLICE-BROKE-REPO-WIDE-ENGINE10-GUARD Three merged slices (35f9a1988, 8b439ee51, 5fc8c5d46) left main red on repo-wide engine10 size and stack-knowledge guards that their selected tests never ran
+- User-visible vs raw: raw (red guards on main; no user-facing message). One consequence is user-visible: the implement lead named a Python runner, which is stack knowledge in a harness that must stay generic.
+- Law: the e10ext tree stays under 1500 lines, the engine10 core stays under 5000 lines, and no file under loki-ts/src names a manifest or runner unless l0_guard.allowlist lists it. Slice gates that run only the touched test files never execute these guards.
+- Cause (measured on clean origin/main 5cae48655): tests/engine10/budget.test.ts e10ext count was 1513 after 35f9a1988 (FC-COMMIT-STAGES-USER-UNTRACKED, +14 lines in preexisting_dirty.ts); l0_guard.test.ts failed on src/e10ext/context.ts naming pytest after 8b439ee51; the core count (the test's split("\n") rule, summed over src/engine10 excluding modernize/) was 4972 at 837abdc40, 5011 at 5fc8c5d46 (FC-ENGINE10-CACHE-KEY-NOT-PRODUCER-BOUND, cache.ts +49 lines since the 9872ddead trim to 4959), 5012 at 8066c0108 and 5025 at c955a15e8 (R100-022 preflight); history is not linear, so 5fc8c5d46 is the first measured crossing and c955a15e8 the final count on main.
+- Siblings swept: every test under tests/engine10 that reads src repo-wide was listed; the three failing here are the only ones red on main. The same weakness exists for any future slice, so the sweep rule is that a slice touching loki-ts/src runs budget.test.ts and l0_guard.test.ts, not only its own files.
+- Mechanism: untouchedUntracked moved to features/untouched_untracked.ts; the producer fingerprint code moved from engine10/cache.ts to util/producer_fingerprint.ts; the implement lead now says to run tests with the exact command the Project Model lists instead of naming a runner. No cap was raised and no allowlist entry was added.
+- Fixture: the existing guards themselves, red before (1513, a pytest literal in context.ts, 5025) and green after. Mutants: five blank lines appended to commit_filter.ts turn the e10ext cap red, five to cache.ts turn the core cap red, and a pytest literal put back into context.ts turns the L0 guard red.
+
 ## FC-FULL-SUITE-IGNORES-PROJECT-INTERPRETER The deep-verify full pytest suite ran under bare `python`, not the project's own interpreter, so a repo with a working .venv and no `python` on PATH could never prove its suite
 - User-visible vs raw: user-visible. An uninterrupted run on a Python fixture with a working .venv and ruff ended PARTIAL because the full-suite check could not run (bare `python` missing or without pytest), while per-test runs under the same repo used the venv.
 - Law: every check that executes project code resolves its interpreter through one resolver (project venv first), and no stage hardcodes a bare interpreter name.
@@ -1922,3 +1930,11 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - 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) |
+
+## FC-GUARD-FIXTURE-MISSES-NEW-DEPENDENCY A change that added a guarded token (98a3c7a67 codex bench adapter) or a runtime file read (77f1196c5 secret-paths.json) did not update the guard fixture, so claude_flags.test.ts P12-26b and the dist-layout test went red on main
+- User-visible vs raw: raw only. P12-26b fired on docstring prose in benchmarks/bench/adapters/codex.py, not a launch. The layout test gap fails closed to plan, never to skip-permissions.
+- Law broken: a change that adds a guarded token or a runtime file read updates the guard's allowlist or fixture in the same slice.
+- Siblings swept: claude_flags.ts loadPermissionsModule (repo-root and dist paths); autonomy/lib/claude-flags.sh and tests/test-claude-flags.sh (bash route, does not load the compiler); os_sandbox.py and tests/lib/test_os_sandbox.py (repo-relative secret-paths.json reads, unaffected); SCOPED_OUT rows claude_code.py and attribution.py (bench arms, same rationale as codex.py).
+- 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.