loki-mode 11.70.4 → 11.71.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.70.4
+# Loki Mode v11.71.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.70.4 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**
+**v11.71.1 | [Autonomi](https://www.autonomi.dev/) flagship product | core skill**

package/VERSION

@@ -1 +1 @@
-11.70.4
+11.71.1

package/dashboard/__init__.py

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

@@ -170,7 +170,7 @@ Tier follows docs/v10/OPERATING-MODEL.md: HIGH touches the moat, verifier, Seal,
 | 41 | R100-041 | team | Team login for the shared Control Plane | L | HIGH | #188 (existing) |
 | 42 | R100-042 | team | Bitbucket and Azure DevOps pull requests | M | MEDIUM | #390 |
 | 43 | R100-043 | team | Release notes written from sealed receipts | S | LOW | #391 |
-| 44 | R100-044 | ide | VS Code extension: run panel and receipt viewer | L | MEDIUM | #392 |
+| 44 | R100-044 | ide | VS Code access through the shipped MCP server: config doc and tool-list smoke test | S | LOW | #392 |
 | 45 | R100-045 | ide | Ready-made ACP configs for Zed and JetBrains | S | LOW | #393 |
 | 46 | R100-046 | ide | Start, status and seal commands in the Claude Code plugin | S | LOW | #394 |
 | 47 | R100-047 | ide | Full-screen terminal UI with approve, steer and pause keys | M | LOW | #395 |
@@ -255,6 +255,7 @@ Items that reuse an existing issue carry their acceptance criteria in that issue
 #### R100-003 In-place resume after a human answers a blocked question
 
 - Issue: #358. Area: autonomy. Size: L. Tier: MEDIUM. Deps: #278, #353, journal (#283, closed).
+- Already exists (corrected 2026-10-23): `loki answer [<run-id>]` already ships in `loki-ts/src/features/blocked_answer.ts` (D63-C4), but the answer starts a new run. This item is the in-place resume under the same run id.
 - Problem: Today a BLOCKED engine10 run is terminal; a Slack reply starts a new follow-up run (`loki-ts/src/contrib/slack_inbound.ts` lines 2-4), so completed work is re-done and users abandon blocked runs.
 - Feature: A blocked run parks with its journal intact. `loki answer <run> "<text>"`, a Slack thread reply, or a PR comment resumes the same run id and skips completed slices.
 - Acceptance:
@@ -301,6 +302,7 @@ Items that reuse an existing issue carry their acceptance criteria in that issue
 #### R100-007 Live run view: `loki status --follow` streams stages, edits, tests and cost
 
 - Issue: #361. Area: speed. Size: S. Tier: LOW. Deps: event log.
+- Already exists (corrected 2026-10-23): `loki cockpit --follow` already exists as an inline-image multi-repo view. This item is the text and JSONL stream for one run in `loki-ts/src/commands/status.ts`.
 - Problem: During a long run users see little; they cancel runs that were progressing.
 - Feature: `loki status --follow [--json]` prints one line per event (stage, file edited, test result, cost) and Ctrl-C detaches without stopping the run (extends `status.ts` and the event log).
 - Acceptance:
@@ -314,6 +316,7 @@ Items that reuse an existing issue carry their acceptance criteria in that issue
 #### R100-008 Background runs and one run list across repos
 
 - Issue: #362. Area: autonomy. Size: M. Tier: MEDIUM. Deps: #232.
+- Already exists (corrected 2026-10-23): `loki start --bg` and `--detach` already exist in `autonomy/loki`, and `loki projects` lists registered repos. This item is `loki runs`, `loki attach` and `loki runs stop` only.
 - Problem: A run ties up the terminal; users with several repos cannot see every running build in one place.
 - Feature: `loki start --bg` returns a run id, `loki runs` lists every run across registered projects (`loki projects`) with state, cost and verdict, and `loki attach <id>` re-joins one.
 - Acceptance:
@@ -416,6 +419,7 @@ Items that reuse an existing issue carry their acceptance criteria in that issue
 #### R100-017 Single-binary install with no node or python3 required
 
 - Issue: #369. Area: onboarding. Size: M. Tier: MEDIUM. Deps: FR-B.
+- Already exists (corrected 2026-10-23): `build:binary` (`bun build --compile`) already exists in `loki-ts/package.json`. This item is building and attaching the 5 targets in `.github/workflows/release.yml`.
 - Problem: Install needs node, python3, jq, git and curl plus a provider; each missing tool is a dead end.
 - Feature: Release attaches compiled binaries (Bun compile) so the v10 path needs only git and a provider CLI (extends FR-B).
 - Acceptance:
@@ -428,6 +432,7 @@ Items that reuse an existing issue carry their acceptance criteria in that issue
 #### R100-018 Automatic rollback on all four deploy providers
 
 - Issue: #370. Area: deploy. Size: M. Tier: MEDIUM. Deps: DEP-B, DEP-D.
+- Already exists (corrected 2026-10-23): `--auto-rollback` already exists on `loki start` and `loki deploy`, for Vercel and Fly only. This item adds Netlify, Cloudflare and a timed health watch.
 - Problem: `loki rollback deploy` prints the rollback command but never runs it; a bad deploy stays live until a human acts.
 - Feature: With `--auto-rollback`, a failed health watch after deploy runs the provider rollback, records it in the receipt, and notifies (DEP-B, DEP-D).
 - Acceptance:
@@ -527,6 +532,7 @@ Items that reuse an existing issue carry their acceptance criteria in that issue
 #### R100-027 Desktop and phone push notifications when a run needs you or finishes
 
 - Issue: #377. Area: speed. Size: S. Tier: LOW. Deps: notify.
+- Already exists (corrected 2026-10-23): Desktop notifications already exist on the legacy route (`send_notification` in `autonomy/run.sh`), and `loki notify` sends to slack, discord and webhook. This item adds a desktop channel and ntfy to `loki notify` and engine10.
 - Problem: Users miss a blocked question for hours because notify only covers Slack, Discord and webhooks.
 - Feature: Add `desktop` (macOS and Linux) and `ntfy` channels to `loki notify`, fired on blocked, done and failed.
 - Acceptance:
@@ -539,6 +545,7 @@ Items that reuse an existing issue carry their acceptance criteria in that issue
 #### R100-028 Best-of-N implement for small tasks
 
 - Issue: #378. Area: speed. Size: M. Tier: MEDIUM. Deps: M-17 scheduler.
+- Already exists (corrected 2026-10-23): Two parallel attempts already exist behind `LOKI_E10_ATTEMPTS=2` (default off) in `loki-ts/src/features/attempts.ts`. This item makes that the default for small tasks and records the arms in the receipt.
 - Problem: One unlucky attempt costs a whole retry round.
 - Feature: `LOKI_BEST_OF=2` runs 2 implementations in parallel worktrees on the cheap tier and keeps the first that seals (extends the modernize best-of-2 scheduler to start).
 - Acceptance:
@@ -551,6 +558,7 @@ Items that reuse an existing issue carry their acceptance criteria in that issue
 #### R100-029 Warm engine daemon for sub-second start
 
 - Issue: #379. Area: speed. Size: M. Tier: MEDIUM. Deps: SPD-B.
+- Already exists (corrected 2026-10-23): The warm engine already ships (D61): `loki-ts/src/features/warm.ts` and `warm_client.ts`, on by default. This item is limited to measuring startup overhead and a read-only `loki daemon status`; if warm p50 is already at or under 1 s, #379 closes as a duplicate of D61.
 - Problem: Each `loki start` pays engine boot, repo map and test map cost.
 - Feature: `loki daemon` keeps the Bun engine, repo map and test map warm per repo; `loki start` attaches when it is running.
 - Acceptance:
@@ -718,15 +726,15 @@ Items that reuse an existing issue carry their acceptance criteria in that issue
 - Metric and target: Teams using it per release; week-4 retention.
 - Competitor baseline: Claude Code: UNKNOWN. Codex CLI: UNKNOWN. Devin: UNKNOWN. Factory droid: UNKNOWN.
 
-#### R100-044 VS Code extension: run panel and receipt viewer
+#### R100-044 VS Code access through the shipped MCP server: config doc and tool-list smoke test
 
-- Issue: #392. Area: ide. Size: L. Tier: MEDIUM. Deps: R100-007.
+- Issue: #392. Area: ide. Size: S. Tier: LOW. Deps: none.
 - Problem: VS Code users must switch to a terminal to start, steer and read receipts.
-- Feature: An extension that starts runs, follows status, answers blocked questions and renders the receipt and clause matrix, talking to the CLI (no new engine).
+- Feature: Rescoped 2026-10-23 by team-lead ruling. The deprecated `vscode-extension/` is not revived. VS Code users reach Loki through the MCP server that already ships (`mcp/server.py`), registered by `loki mcp install --client vscode`. The work is a documented VS Code MCP config and one smoke test that lists the tools over that config.
 - Acceptance:
-  - The extension activates in VS Code and lists the current run from `loki status --json` within 2 s.
-  - Start, steer and answer buttons call the CLI; a fixture asserts 3 CLI invocations.
-  - Receipt view shows verdict and N of N clauses equal to `loki proof` output.
+  - docs/INSTALLATION.md shows the `.vscode/mcp.json` that `loki mcp install --client vscode --project` writes, and names `loki_v10_run`, `loki_v10_status` and `loki_v10_verify`.
+  - A smoke test launches the server from the written config and finds those 3 tools by name in `tools/list`.
+  - No file under `vscode-extension/` or `scripts/release.sh` changes.
 - Metric and target: Runs per user per week for VS Code users; week-2 return rate.
 - Competitor baseline: Claude Code: `--ide` connects to an IDE on startup (`claude --help`, Claude Code 2.1.309, run 2026-10-23). Codex CLI: Codex IDE extension (https://learn.chatgpt.com/docs/codex/cli (fetched 2026-10-23)). Devin: Embedded editor in Devin Session Tools; no VS Code page in the index (https://docs.devin.ai/work-with-devin/devin-session-tools.md, listed in https://docs.devin.ai/llms.txt, fetched 2026-10-23). Factory droid: IDE integrations page (https://docs.factory.com/cli/getting-started/overview (fetched 2026-10-23)).
 
@@ -1336,3 +1344,121 @@ Items that reuse an existing issue carry their acceptance criteria in that issue
 - Problem: Clauses from documents cannot point back to their source.
 - Metric and target: Clauses traced to source.
 - Competitor baseline: Claude Code: UNKNOWN. Codex CLI: UNKNOWN. Devin: UNKNOWN. Factory droid: UNKNOWN.
+
+## Lanes and waves
+
+This section is the dispatch source for Feature 100 (accepted by team-lead on 2026-10-23). It was built from the file set in every one of the 100 issue cards: the issue body for the 79 new issues, and the issue body plus comments for the 21 reused issues, all read on 2026-10-23. Test files are not counted as shared files.
+
+Where the "Parallel safety" line inside an issue card disagrees with this section, this section wins. Several of those lines were written before the file sets were narrowed. For example, #357, #339 and #396 name #359 and #362 as start.ts sharers, but neither #359 nor #362 edits start.ts.
+
+### Hot-spot lanes
+
+Rule: each hot-spot file has exactly one live writer. The next issue in a lane starts only after the previous one has merged to main, and it rebases on main before it starts. An issue that sits in two lanes waits until both lanes reach it.
+
+- `loki-ts/src/commands/start.ts`: #357, then #339, then #396, then #372.
+- `loki-ts/src/commands/status.ts`: #361, then #359, then #370, then #372, then #395, then #406.
+- `loki-ts/src/engine10/machine.ts`: #345, then #358, then #235. #345 waits for live branches pd/cw12 and pd/cw12-r2, which edit `machine.ts`, `cli.ts` and `mcp/server.py`. #358 also waits for branch pd/cw04d, which edits `blocked_answer.ts`.
+- `autonomy/loki` function `cmd_deploy`: #359, then #370, then #382, then #383, then #384, then #385, then #386.
+- `.github/actions/issue-to-pr/action.yml`: #360, then #365.
+
+19 issues edit at least one hot-spot file: #235, #339, #345, #357, #358, #359, #360, #361, #365, #370, #372, #382, #383, #384, #385, #386, #395, #396, #406.
+
+Three cards name a hot-spot file without editing it, so they are not in a lane. #351 says "do not touch machine.ts". #370 cites `start.ts` only as existing behavior; it is still in the status.ts and cmd_deploy lanes. #398 names `packages/control-plane/src/server/routes/start.ts`, which is a different file.
+
+### Parallel-safe with respect to the hot-spot files
+
+These 81 issues edit none of the five hot-spot files, in rank order: #342, #362, #363, #364, #249, #366, #367, #368, #369, #371, #351, #231, #373, #374, #375, #376, #377, #378, #379, #380, #279, #381, #387, #388, #389, #188, #390, #391, #392, #393, #394, #397, #398, #399, #248, #400, #401, #402, #403, #404, #405, #407, #408, #409, #410, #290, #411, #412, #413, #414, #267, #346, #347, #415, #416, #417, #418, #277, #278, #232, #419, #420, #421, #422, #423, #424, #425, #426, #427, #428, #429, #430, #431, #343, #432, #433, #434, #341, #340, #263, #435.
+
+Parallel-safe here means safe against the hot-spot lanes only. Two of these issues can still share another file. Before two of them run at the same time, check the other shared-file lanes below.
+
+### Other shared-file lanes
+
+One live writer per file, in the order given.
+
+- `loki-ts/src/commands/doctor.ts`: #357, #366, #290, #347, #390, #413, #414, #432.
+- `loki-ts/src/cli/registry.ts`: #362, #375, #379, #395, #400, #401, #430.
+- `loki-ts/src/engine10/events.ts`: #361, #358, #431.
+- `loki-ts/src/engine10/session.ts`: #358, #351, #406, #415. If pd/cw04d holds #358 up, #351 goes first.
+- `loki-ts/src/engine10/pr_body.ts`: #342, #359, #381, #387, #388.
+- `loki-ts/src/engine10/stages/pr.ts`: #231, #387, #390.
+- `loki-ts/src/engine10/verify_cmd.ts`: #380, #372, #434.
+- `loki-ts/src/engine10/supervisor.ts` and `loki-ts/src/util/slack_events.ts`: #427, #411, #406.
+- `loki-ts/src/runner/build_prompt.ts`: #366, #402, #432. New always-on text goes in the cache-stable prefix.
+- `.github/workflows/release.yml`: #369, #372.
+- `blocked_answer.ts`: branch pd/cw04d, #358, #363, #399, #412.
+- `loki-ts/src/commands/memory.ts`: #364, #389, #400, #401, #402.
+- `loki-ts/src/util/pr_lessons.ts`: #364, #389, #405.
+- `loki-ts/src/runner/router/cost_preview.ts`: #367, #374, #407, #412.
+- `loki-ts/src/commands/proof.ts`: #368, #434, #435.
+- `loki-ts/src/commands/kpis.ts` and `metrics/kpis.ts`: #371, #411, #424.
+- `loki-ts/src/features/visual_evidence.ts`: #249, #263, #383.
+- `loki-ts/src/util/redact.ts`: #384, #389, #421.
+- `loki-ts/src/runner/budget.ts`: #408, #411, #412.
+- `loki-ts/src/runner/providers.ts`: #279, #346, #277, #278.
+- `providers/model_routes.ts`: #267, #346, #414, #415.
+- `providers/model_catalog.json`: #267, #346, #416.
+- `providers/model_routes.sh`: #414, #415, #416.
+- `providers/price_table.ts`: #279, #411, #417.
+- `mcp/server.py`: #345, #290, #339.
+- Control Plane `App.tsx`: #363, #403, #423.
+- Control Plane `pages/run/index.tsx`: #422, #423, #425.
+- `autonomy/loki` dispatch rows: #367, #232, #379, #418, #419.
+- `autonomy/loki` `cmd_cost`: #407, #408, #409, #410.
+- `autonomy/loki` `cmd_next`: #374, #375.
+- `autonomy/loki` `cmd_template`: #404, #428.
+- `autonomy/loki` `cmd_notify`: #377, #424.
+- `autonomy/loki` `cmd_verify` and `fast_verify.py`: #380, #430.
+- `autonomy/notify.sh`: #377, #427, #406, #399, #424, #431.
+- Pairs, first one merges first: `decompose.ts` (#235, #419), `unit_mode.ts` (#235, #421), `slack_inbound.ts` (#358, #381), Control Plane `answer.ts` (#363, #399), `schemas/run-event.schema.json` (#431, #433).
+
+Different functions in `autonomy/loki` can be edited in parallel, because each lane above names its own function.
+
+### Waves
+
+Wave 1 can start now. Each issue heads every lane it is in, and no two share a file. Each one was checked against every live branch (remote pd/* and local branches with a commit in the last 48 hours) with `git cherry origin/main <branch>` and `git log origin/main..<branch> --name-only`, on 2026-10-23. Dispatch in this order as seats free up:
+
+- #357: already dispatched (pd/r100-001). `doctor_fix.ts` is touched only by its own branch. `doctor.ts` is also touched by 14 live branches (pd/286, pd/315, pd/316, pd/316-rb, pd/329, pd/330, pd/bunentry, pd/bunentry-rb, pd/bunsib, pd/mcpchain, pd/mcpchain-r2, pd/mcpchain-r3, pd/rq04, pd/w2-33), so rebase before review.
+- #342, #360, #364, #368, #231, #422: no live branch touches any of their files.
+- #361: no file overlap. Its card names `autonomy/loki` only as existing behavior (`cmd_cockpit`); its edits are in `status.ts` and `events.ts`.
+- #362: the only overlap is `autonomy/loki`. The live branches there edit `_loki_airgap_audit`, `cmd_bench` and `_loki_start_optval_consumes`. #362 adds dispatch rows and reads `cmd_projects`, so the hunks do not overlap.
+
+Wave 2. Each issue starts after the merges named:
+
+- #345: after pd/cw12 and pd/cw12-r2 (`machine.ts`, `cli.ts`, `mcp/server.py`), pd/328 (`cli.ts`), and pd/257p2, pd/257rb, pd/319e, pd/319fix (`mcp/server.py`).
+- #249: after the live `stages/verify.ts` branches: pd/237r10, pd/237r9, pd/partial-harness, pd/wallfile, pd/wallfile-r2, pd/wallgo, pd/wallgo-r2, pd/wallnorunner, pd/wallrust, pd/wallrust-r2, pd/weaktest.
+- #367: after the live `benchmarks/bench/run.sh` and `runner.py` branches: pd/246fix2, pd/claim, pd/claim-100x, pd/cw15, pd/fd1b, pd/resumecost, pd/resumecost2, pd/resumecost3, pd/traptasks2, pd/trusttime, pd/trusttime-r2, pd/verifyh2h.
+- #369: after pd/cw01b and pd/cw01c (`release.yml`).
+- #371: after pd/252b and pd/252b-r (`metrics/kpis.ts`).
+- #358: after #345, #361 and branch pd/cw04d.
+- #359: after #361 and #342.
+- #365: after #360.
+- #366: after #357.
+- #370: after #359.
+- #235: after #358.
+- #363: after #358.
+- #372: after #369, #357 and #370.
+
+Held: #398 depends on open issue #188 (dashboard authn/authz), so it is not a wave-1 head.
+
+Before dispatching any wave-2 issue, re-run the live-branch check for its files; branches named above may have merged or new ones may have started.
+
+After wave 2, pull any issue whose lanes are free, following the lane orders above.
+
+### Wave-1 assignments
+
+Checked on 2026-10-23 at 06:50Z against `gh issue view` comments and origin branches. None of these issues has a GitHub assignee, so claims come from issue comments or team-lead dispatch. "Behind" counts commits on origin/main that the branch lacks.
+
+| Issue | Item | Engineer | Branch | Reviewer | Tier | State |
+|---|---|---|---|---|---|---|
+| #357 | R100-001 | eng-mcpchain | pd/r100-001 9feace648 (1 ahead, 16 behind) | unset | MEDIUM | Needs rebase. Criterion 3 NOT MET on both the branch and its base 3f6e07547 (issue comment 06:39Z); the PARTIAL predates the change. |
+| #342 | R100-006 | eng-r237 | none | unset | HIGH | Waiting on CW-04 (#337), which is OPEN with no commit on main. Ruling comment 06:39Z. |
+| #360 | R100-005 | unowned | none | unset | HIGH | No claim comment, no branch. Free to assign. |
+| #364 | R100-011 | eng-tmo | pd/364a fee344a42 (1 ahead, 8 behind); pd/364b 808c40cab stacked on (a) | tl-324 | MEDIUM | In review. Criteria tally comment 06:45Z; merge-tree rc=0 against origin/main 0a6ae7cb6. |
+| #368 | R100-016 | eng-318r | none | rev-b | HIGH | Dispatched by team-lead. No claim comment or branch yet. |
+| #231 | R100-022 | eng-tmo | none | tl-324 | MEDIUM | Dispatched by team-lead. Only the slice card comment (06:14Z); no claim comment or branch yet. |
+| #422 | R100-082 | eng-351 | none | unset | LOW | Starts after the loadaware fix. No claim comment or branch yet. |
+| #361 | R100-007 | eng-cw01 | pd/361 ece154741 (1 ahead, 11 behind) | tl-324 | LOW | In review. No claim comment on the issue. |
+| #362 | R100-008 slice (a) | eng-mcpchain | pd/r100-008a 861656d44 (1 ahead, 8 behind) | unset | MEDIUM | Claimed in comment 06:46Z after eng-r237 released it. Slice (b) unowned. |
+| #249 | R100-013 slice (a) | eng-r237 | pd/249a 721db86f3 (1 ahead, 0 behind) | rev-c | HIGH | In review. Slice (a) edits only `visual_evidence.ts`, which team-lead cleared out of wave 2. Slice (b) stays in wave 2 behind the `stages/verify.ts` branches. |
+
+Unowned: #360, #362 slice (b) and #249 slice (b). No reviewer yet: #357, #342, #360, #362 and #422.