loki-mode 11.60.17 → 11.61.1

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

package/VERSION

@@ -1 +1 @@
-11.60.17
+11.61.1

package/dashboard/__init__.py

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

@@ -1684,3 +1684,11 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept: every other test in fix_resume.test.ts that loops is pure (the P12-07j malformed-event loop at :382, the P12-07m cap loop at :560); the single-supervisor async tests run one resume and the only subprocess test (P12-07m main(), :576) already has 70000.
 - Mechanism: the P12-07n test takes an explicit 60000ms bound; no assertion changed.
 - Fixture: tests/engine10/fix_resume.test.ts P12-07n itself; it fails at 5000ms on origin/main debc7e843 under load and passes with the bound.
+
+## FC-P9-DYNAMIC-IMPORT-FALSE-POSITIVE Moat case P9.allowtoken-only-fetch-callers went red on main for a dynamic import of reviewerGitEnv in cli.ts, which is not an allowToken caller
+- User-visible vs raw: raw (a red moat case on main; no user-facing message).
+- Law: allowToken reaches safeGit only from the two fetch callers (FC-25c); the guard must fail closed on anything that can hide a caller, and must not fail on code that provably cannot reach the opt-in.
+- Cause (measured): the commit 58a365567 (FC-REVIEWER-GIT-CONFIG-EXEC) added `const { reviewerGitEnv } = await import("./util/safe_git.ts")` at loki-ts/src/cli.ts:330. The scan's import rule flags every literal dynamic import or require of safe_git, because a namespace-style result can be reached through a computed key. `bash tests/moat/p9-rule-of-two.sh` on a clean origin/main worktree with deps installed printed `CASE P9.allowtoken-only-fetch-callers FAIL ... safe_git imported by alias, namespace, require or dynamic import ...: loki-ts/src/cli.ts`. tests/moat/run.sh step 0a installs loki-ts deps before the case runs, so this was a real red, not a missing-typescript false red.
+- Siblings swept: cli.ts:330 is the only dynamic import of safe_git outside loki-ts/src/util (git grep). Static named imports of safe_git were already accepted; the dynamic destructured form is the same shape.
+- 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.