loki-mode 11.63.8 → 11.63.9

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

package/VERSION

@@ -1 +1 @@
-11.63.8
+11.63.9

package/dashboard/__init__.py

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

@@ -1792,3 +1792,19 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept: the other help suites (test-help-discoverability.sh, test-help-no-removed-surfaces.sh, test-help-start-flags.sh, test-help-changelog-drift.sh) were edited by 826deafd2 itself; no other file in tests/ names the Build:/Session: headers (git grep).
 - Mechanism: the help-structure block runs `loki help all`; the entry-count bound is 32 with the measured count in the comment. No assertion text changed except the bound.
 - Fixture: tests/cli/test-alias-forwarding.sh itself, 211 passed, 0 failed on both routes. Mutants: point the block back at `loki help` (all 9 red), rename a header (1 red), bound 31 (1 red), Usage text (1 red).
+
+## FC-AUTH-CAUSE-ONLY-IN-IMPL-LOG A rejected API key ends the run as "exit 1 (general error)" while the cause sits only in the implement log
+- User-visible vs raw: `ANTHROPIC_API_KEY=<bad> loki start "<brief>"` printed `Reason: exit 1 (general error)` and `next: loki doctor`. Raw: `.loki/iteration-<run>-impl.log` held `Invalid API key · Fix external API key`, and the SDK frame carried `error: "authentication_failed"` with `api_error_status: 401` (measured with `claude -p --output-format stream-json`). The run ran every later stage on a key the provider had already rejected.
+- Law: a failure the provider names is reported by that name at the moment it happens, with the fix command (ENGINE-LAWS: user-visible output states the cause, not the exit code).
+- Cause: `session.ts` classifies fatal auth only from child stderr plus `[sdk-loop error: ...]` lines. `sdk_stream_parser.ts` never wrote such a line for the structural `authentication_failed` assistant frame, so the machine's fatal:auth path (`machine.ts` sessionKind) never fired; stdout text is deliberately never classified (forgery guard in fatal_e2e.test.ts).
+- Siblings swept: every stage that opens a provider session (wall, plan, implement, already_done, deep council, fix) calls `ctx.sessions.run`, which the machine wraps once, so one classifier covers all of them (`git grep -n 'sessions.run(' loki-ts/src`). Child-stderr route already classified and is unchanged. The `billing_error` assistant frame is the same shape but maps to quota_exhausted, which waits and reruns by design (P12-09); it is not changed here and stays a follow-up.
+- Mechanism: the stream parser writes `[sdk-loop error: Failed to authenticate (authentication_failed): <provider text>]` for the structural frame only. `session.ended` records the provider text as `provider_error`; `reasonOf` appends it to "provider authentication failed", and `nextOf` names the fix: `claude login`, or the key to replace when the provider says API key.
+- Fixture: loki-ts/tests/runner/sdk_stream_parser.test.ts, loki-ts/tests/engine10/output.test.ts and loki-ts/tests/util/run_summary.test.ts cases named FC-AUTH-CAUSE-ONLY-IN-IMPL-LOG. Red with the parser line, the event field or the reason suffix removed.
+
+## FC-AGENT-TEXT-FORGES-ENGINE-MARKER Agent-controlled text could write a line the engine trusts as its own, so plain assistant prose or a provider CLI's stdout could end a run as fatal:auth
+- User-visible vs raw: user-visible. An assistant text block (or any stdout line of a provider CLI) reading `[sdk-loop error: Failed to authenticate (authentication_failed): Invalid API key, ...]` plus exit 1 gave stop `fatal:auth`, and with the cause-in-Reason slice it was printed as the Reason with key advice. Reproduced by rev-c on main.
+- Law: the engine classifies only text the provider or the engine wrote, never the agent transcript (A-113); an engine-written marker must be unforgeable from agent text.
+- Cause (measured): sdk_stream_parser capture() appended assistant and result text verbatim to the iteration log, and providers.ts writeCaptured wrote a CLI provider's stdout verbatim; session.ts matches `^\[sdk-loop error: .*\]$` and retry_class SDK_ERR matches the marker anywhere in the same text.
+- Siblings swept: every line-anchored reader of the log text (session.ts parseMarkers reads LOKI_ALREADY_DONE and LOKI_SPEC_CONFLICT, which the agent is meant to write, so they are not engine markers; budget.ts isRateLimited is an unanchored keyword heuristic on prose by design, not a trusted marker). Engine-written markers in the log: `[sdk-loop error:` (parser frame line, providers.ts catch) and `[rate_limit]` (a keyword the heuristic already matches in prose, so a forgery gains nothing). Also covered: the claude, codex, cline, aider and opencode CLI paths (all four writeCaptured stdout sites) and the `said` text inside the real frame line.
+- Mechanism: retry_class.ts neutralizeEngineMarkers rewrites `[sdk-loop error:` to `[agent-text sdk-loop error:` anywhere in agent text (capture(), the frame's `said`, and every CLI stdout before writeCaptured). sdkAuthCause also returns redactSecrets(...) because provider_error goes into events.jsonl unredacted.
+- Fixture: sdk_stream_parser.test.ts cases named FC-AGENT-TEXT-FORGES-ENGINE-MARKER (forged assistant and result text at line start and mid-line, mid-line quote read as null by sdkAuthCause, real frame still classified and redacted for an sk-ant- value) and fatal_e2e.test.ts (forged stdout plus exit 1 is not fatal). Each is red with neutralizeEngineMarkers as identity, the `^` anchor dropped, or the redaction removed.