loki-mode 11.57.3 → 11.57.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.57.3
+# Loki Mode v11.57.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.57.3 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.57.5 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.57.3
+11.57.5

package/dashboard/__init__.py

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

@@ -1535,3 +1535,12 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept: stop (SIGINT/SIGTERM) already restored via restoreBranch and keeps the branch (a stopped run is resumable); crashed runs never reach the terminal code, so resume keeps its branch. A run branch with any commit, a branch the user moved off, and a non-`loki/` name are never touched.
 - Mechanism: stop_restore.ts dropEmptyRunBranch, called once from the supervisor after the backstop commit, deletes the branch (update-ref -d with the expected tip) only when the tip equals intake's base_sha, after restoreBranch's plain no-force checkout; run_summary.ts prints `Nothing to accept` for 0 files.
 - Fixture: tests/engine10/supervisor_signal.test.ts "supervisor: a run that committed nothing" (empty, committed positive control, user-switched, dirty, non-loki name) and tests/util/run_summary.test.ts (0-file Decide block).
+
+## FC-GROUP-REFUSES-LOCAL-TASK-WITHOUT-ORIGIN A multi-part prompt in a repo with no owner/repo origin exits NOT PROVEN with no unit started, so a task that needs no remote cannot run at all
+- User-visible vs raw: user-visible. `loki start` on a two-file prompt in a fresh local repo printed "NOT PROVEN: group run needs an origin remote of the form owner/repo; no unit was started" and exited 1 in 0.2 s. The bench (fd-2-two-module-untested, loki arm, 2026-10-23) scored it a failure although Loki never attempted the task.
+- Law broken: a path that needs a remote only for its launcher must be chosen only when the remote exists; a local task never fails because of a capability it did not need (verified-unless-it-cannot-be).
+- Cause (measured): route.ts chose the group runner on decomposability and provider slots alone; run_group.ts then refused at its own origin check (the unit launcher, autonomy/lib/backlog.py, takes the owner/repo slug).
+- Siblings swept (grep for remote get-url origin across loki-ts/src, autonomy, bin): run_group.ts (three checks, now one originSlug); backlog.py origin_slug (the launcher itself, github.com only); run_outputs.ts resume (already degrades with a message); base_guard.ts (already skips without an origin); issue-parser.sh and run.sh issue-mode slug detection (issue mode needs a repo by definition). No other local-task path requires an origin.
+- Mechanism: route.ts asks run_group.originSlug before choosing the real group runner (task or mission) and otherwise takes the existing sequential fallback with the reason named. run_group.ts keeps its own refusal for a direct call.
+- Sibling not closed: originSlug accepts any path-shaped origin with two segments (a local bare path reads as a slug), while backlog.py accepts github.com only; tightening it would change GitHub Enterprise hosts, so it is left and noted here.
+- Fixture: loki-ts/tests/engine10/route_group.test.ts (no origin: sequential with reason, not NOT PROVEN, task and mission; control: an owner/repo origin still reaches the group runner). Red with the two gates in route.ts removed (3 failures).