loki-mode 11.59.0 → 11.60.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.59.0
+# Loki Mode v11.60.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.59.0 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.60.1 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.59.0
+11.60.1

package/dashboard/__init__.py

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

@@ -1566,3 +1566,12 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept: touched() prefix rule, the loop resolving a path under a gitlink against cwd and root, rule (i) bare basename, rule (ii) final-segment component; all four now share one gitlink check (checkedOut, deleted-in-diff).
 - Mechanism: citationVerdict returns "refuted" | "unproven" | "ok". A gitlink directory with content on disk and no deleted-in-diff record (CitationContext.gitlinkDeleted, filled by voter_agents from the submodule old..new diff) refutes the citation (MEDIUM, [citation not found]); an absent or empty gitlink directory keeps HIGH and prefixes the description with [NOT PROVEN: ...], which travels in the council issue text.
 - Fixture: loki-ts/tests/council/finding_schema.test.ts "submodule citation: checked out", "not checked out" and "deleted in the diff"; red when the return in the gitlink branch of citationVerdict is mutated back to "ok".
+
+## FC-PYTEST-IMPORT-SYMLINK-UNDER-TESTS A committed change carried a symlink under tests/ (tests/kvparse.py, tests/wcl.py in 2 of 3 cw20 pilots), flagged only after the fact as NOT PROVEN by base_guard.ts (FC-WALL-PHANTOM-PATH)
+- User-visible vs raw: user-visible; the PR holds a link the task never asked for and the verdict degrades to NOT PROVEN.
+- Law broken: the change contains only what the task needs.
+- Cause (SUSPECTED, evidence status: code reading only, no transcript yet): no engine call creates a link under tests/ (engine links are node_modules, .venv, venv in throwaway worktrees: base_guard.ts, mutation_proof.ts, before_after.ts; treeswap.ts restores an attempt's own link). The implement agent most likely links `tests/<mod>.py` to a root module so a bare `pytest` import works; the commit stage's `git add -A` then stages it. The Wall brief already carried `python -m pytest <file>` (wall_hints.ts), the implement brief did not.
+- Siblings swept: fix.ts and other stages build on FIXED_RULES or a brief without a runner line; the Wall brief already states the invocation. Only the implement lead lacked it.
+- Mechanism: one line in FIXED_RULES (cache-stable lead of the implement brief) naming the exact invocation and forbidding files or links under tests/ to satisfy imports.
+- Fixture: tests/e10ext/full_job_brief.test.ts "FC-PYTEST-IMPORT-SYMLINK-UNDER-TESTS" and the implement-brief golden.
+- Open: confirm by grepping the loki implement transcripts of the fd-1 and fd-4 grid trials for `ln -s` and bare `pytest` (eng-303c); update this row with the result. Not covered: an agent that links anyway is still only flagged, not blocked.

package/docs/v10/GUARDS.md

@@ -877,3 +877,7 @@ previously mismarked two merged guards (S-16, S-74) as PENDING.
 - **Root cause:** each env builder deleted a subset of credential paths itself; only the worker env reset the rest.
 - **Guard:** `loki-ts/tests/util/fc90_credential_env.test.ts` plants a fake gh hosts.yml and a fake global git credential helper in a fake HOME, proves the raw env sees them, and proves an env from plainTestEnv does not; it also pins the one-dir-per-process GH_CONFIG_DIR lifecycle. It lives in loki-ts/tests/util, which `scripts/global-guards.tsv` already selects on every diff.
 - **The test that proves it fires:** removing the GH_CONFIG_DIR line, the credential.helper reset or the sentinel from `loki-ts/src/util/credential_env.ts` turns it red. Run: `cd loki-ts && bun test tests/util/fc90_credential_env.test.ts`.
+
+### 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.