loki-mode 11.56.2 → 11.56.4

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

package/VERSION

@@ -1 +1 @@
-11.56.2
+11.56.4

package/dashboard/__init__.py

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

@@ -1503,3 +1503,14 @@ L0 review rule (ENGINE-LAWS.md L0): a fix that adds an `if` or a regex about the
 - Siblings swept: all 14 literals in loki-ts/tests, replaced in one change; per-test `, N)` timeouts are explicit single-test budgets and are not in this class.
 - Mechanism: loki-ts/tests/preload.ts exports `setLoadAwareTimeout(baseMs)`: baseMs times clamp(ceil(2 * loadavg1 / cpus), 1, 10). `LOKI_TEST_TIMEOUT_SCALE` (positive number, capped at 10) replaces the factor; `LOKI_TEST_TIMEOUT_MS` is a floor that wins when larger. A guard in loki-ts/tests/util fails on any direct `setDefaultTimeout(` call in tests.
 - Fixture: loki-ts/tests/util/test_timeout_guard.test.ts tests FC-TEST-TIMEOUT-OVERRIDES-CLI, including a subprocess run through the real setLoadAwareTimeout path (env knob lifts the budget, a real hang still times out).
+
+- Late materialization (recurrence 2026-10-23): the registry applies a publish 3 to 6 minutes after the client prints "+ loki-mode@X" (registry time field: 11.53.0 +4m10s, 11.53.1 +5m13s, 11.54.0 +6m12s). 11.54.1 uploaded 04:34:24Z, served 04:39:34Z; 11.54.2 uploaded 04:38:07Z, served 04:41:17Z, leaving latest=11.54.1 next=11.54.2. The 15s settle in the script is far shorter than the lag, so a write made in publish-npm can be overtaken after it settles (mechanism inferred, not directly observed). Fix: verify-npm-registry runs scripts/npm-dist-tags.sh again after loki-mode@VERSION resolves; the script is convergent (max stable, never lower), so it is safe outside the release-npm lock.
+- Fixture: tests/test-npm-dist-tags.sh (9 cases incl. latest dragged down after the first settle restored by a second run, a settled converge run writing nothing, late overtaking write restored and view outage error/empty with zero writes). Mutants (ignore tags, no re-read, target=VERSION, outage guard removed) each fail a case.
+
+## FC-THINKING-TYPE-ACCEPTED-BY-CLI-REJECTED-BY-API A thinking type the CLI accepted was a 400 for the model, and the usage error stated a rule the model did not have
+- User-visible vs raw: user-visible. `loki internal sdk-judge|sdk-text --model claude-sonnet-5-5 --thinking disabled` at effort high or below was sent as `thinking: {type: "disabled"}`, which the API rejects with a 400 at every effort for that model (claude-api skill, Thinking & Effort table: Sonnet 5.5 "disabled returns 400; to turn thinking off send between_tools"). The judge failed closed and the bash caller fell back. Separately, the usage error "disabled cannot combine with --effort xhigh or max" was printed for claude-opus-5 and claude-haiku-5-5, which #314 clamps instead of refusing.
+- Law: a request parameter is derived from the model catalog, never hand-written per model; a message never states a rule the catalog does not record.
+- Cause (measured): #314 encoded only the effort ceiling (thinking.max_effort) and kept one model-blind sentence in two callers; the catalog had no way to say that a type is never valid for a model and what replaces it.
+- Siblings swept: claude-opus-5-5, claude-fable-5-1 and claude-fable-5 list only adaptive in thinking.types, so disabled is a 400 at every effort for them (review of 37d4eb08d): claudeThinkingAccepted(model, type) is false for a type absent from types with no substitute, thinkingConflictsEffort refuses it at every effort, thinkingUsageError says "disabled is not accepted by <model>", and clampThinkingForEffort sends adaptive with a ledger record; claude-haiku-4-5 (no disabled substitute is invented), the max_effort clamp (still applied to the substituted type), thinkingConflictsEffort (a substituted model no longer conflicts), both callers of the usage error.
+- Mechanism: catalog thinking.substitute maps a requested type to the type sent (claude-sonnet-5-5: disabled to between_tools). clampThinkingForEffort applies the substitute, then the max_effort clamp to the substituted type, and the ledger thinking_clamp records `disabled->between_tools@<effort> (max high)` or `disabled->adaptive@<effort> (max high)`. thinkingUsageError builds the sentence from the substitute and max_effort of the resolved model.
+- Fixture: loki-ts/tests/providers/claude_flags.test.ts "thinking substitute and usage message (#314 follow-up)", loki-ts/tests/runner/sdk_invoker.test.ts "thinking substitute (#314)", tests/test-model-catalog-single-source.sh pins thinking.substitute. Three mutants (drop the catalog substitute, hand-write the message, clamp on the requested type) each turn them red.