loki-mode 9.75.0 → 9.77.0

package/docs/v10/ARCHITECT-CUTS.md

@@ -1,403 +1,440 @@
 
 
-## 20:12Z cut (S-194..S-213)
+## 20:59Z cut (S-214..S-233)
 
-**Checked before cutting.** All reads are on main at 8ba7024d (v9.73.0).
-- **Alternates re-read against the code.**
-  - **A1 (BACKLOG 108) is real.** `create_session_pr`'s `LOKI_AUTO_PR=1` branch calls `_loki_trusted_push` and never reads `.loki/state/agent-committed-user-files.z`. The only references to that file are the writer comment and the writer itself, inside `_loki_untrack_agent_committed_user_files`.
-  - **A2 (BACKLOG 17) is real.** The "Notify dashboard of active project directory" block, about 24477 today, posts to `/api/focus` behind `command -v curl` only. It has no `ENABLE_DASHBOARD` check.
-  - **A3 is real and larger than the card says.** run.sh 211 and 239 always set PROJECT_DIR to the Loki install root. So the BACKLOG 127 "guard when unset" would do nothing. The actual defect is that `council_managed_should_stop` runs `git diff --stat` in Loki's own tree, not the target project. Its three readers are still bare `python3 -E`, and p2-honest-verdict.sh (about 858) says so.
-  - **A4 (BACKLOG 51) is real.** `grep -c PYTHONUSERBASE autonomy/loki` prints 0. The NOT CHECKED text says "Install python3 cryptography" even to a user who installed it through PYTHONPATH or PYTHONUSERBASE, which `-E` ignores.
-  - **A5 is split.**
-    - BACKLOG 145 sits in the Array.from generator arm, about 1934-1994. That does not overlap S-180's helper-return arm (about 2081-2170).
-    - BACKLOG 147 edits `HELPER_LOCAL_DECL_TMPL`, which is in S-180's region, so it is held.
-- **New class found: every `-E`-only verdict reader outside completion-council.sh (BACKLOG 53 and 54).** These are:
-  - autonomy/lib/done-recognition.sh: 16 sites.
-  - autonomy/council-v2.sh: 7 sites.
-  - autonomy/lib/voter-agents.sh: 3 sites.
-  - autonomy/lib/proof-check.sh: 3 sites.
-  - autonomy/prd-checklist.sh: about 11 sites.
-  - loki-ts/src/commands/proof.ts:606, the Bun `loki proof verify` path.
+**Checked before cutting.** All reads are on main at 04af133a.
 
-  All of them run PATH `python3 -E`. BACKLOG 134 showed that a user-site `.pth` still loads under `-E`.
+**Held dependencies, checked against main.**
+- **Merged:**
+  - S-180 (22ff5a44)
+  - S-179 (94035ac4)
+  - S-175 (6fab92ce)
+  - S-178 (c8b4c8c0)
+  - S-187 (03070f62)
+- **Still in flight:** S-194, S-195, S-197, S-198.
+- **What that unblocks:**
+  - BACKLOG 147: S-180 has merged, and S-198's region (about 1934-1994, fixture about 3301) does not overlap `HELPER_LOCAL_DECL_TMPL` (1182, used about 2186). Cut as S-214.
+  - dashboard/server.py items from BACKLOG 118: S-178 has merged. The council-state fallback (8638) and the notifications zero summary (8909) are already handled on main. The skill-session `running_agents: 0` is cut as S-222. The other two are held or dropped (see below).
+  - ProjectWorkspace phase labels and Replay Build: S-187 has merged. Cut as S-230.
+- **Still held:**
+  - BACKLOG 36: waits for S-198.
+  - BACKLOG 19 and the bash `loki proof verify` interpreter: wait for S-197.
+  - BACKLOG 99, bash half: waits for S-194 and S-195.
 
-  On `-S` compatibility:
-  - The imports I read are stdlib only: swarm/sycophancy.py, autonomy/checklist-verify.py, and autonomy/lib/proof-verify.py (which adds its own directory to sys.path at line 76). So `-I -S` should hold for those.
-  - Each builder still audits the imports of the rest of its sites, including the prd-checklist oracle heredoc.
+**Found shipped on main, but the backlog text still reads open.** Future cuts can skip these:
+- 35: tests/test-moat-runner.sh:653
+- 37 and 60: loki-ts/src/runner/quality_gates.ts about 565-615
+- 72 and 80, the base and start-sha part: run.sh 9888-9895. The warning wording is still open and is cut as S-233.
+- 91: run.sh 26343-26345
+- 102: run.sh 10951-10955
+- 104 and 120: tests/run-all-tests.sh 965-966
+- 116, the overview council gate card: loki-overview.js about 395-414
+- 118:
+  - standalone receipt order and the VERIFIED WITH GAPS colour: build-standalone.js 2517-2531
+  - council-state and notifications: server.py 8638, 8909
+- 150: S-79
+- The memory browser's null lists (loki-memory-browser.js 448-506) and the cockpit's ChangeReview and RiskPanel errors are also handled.
 
-  Existing tests source each of these files on their own, so each file needs the guarded helper copy. For voter-agents.sh, `.` at completion-council.sh 4245 sources it into the parent shell.
-- **council-v2 fails open on sycophancy.** A detector crash yields `0.000`, then `should_challenge=no`. A unanimous approve then skips the devil's advocate.
-- **Cockpit remainder (BACKLOG 114).**
-  - `FinalActions` receives `git=null` after a failed status fetch (the `settle` fallback) and still says "The working tree is clean" and "Nothing to push".
-  - A failed `getStatus` (the swallow at useCockpitState.ts:202) makes Pause, Resume and Stop read "No run in progress".
-  - A failed `getChecklist` (the swallow at 204) renders "No gate results recorded."
-- **Already handled, so dropped:**
-  - BACKLOG 31: proof-verify maps unverifiable drift to 2.
-  - BACKLOG 38: `no_pass_recorded`.
-  - BACKLOG 49: the `--jwks` output is patched.
-  - BACKLOG 16 and 85: `PYTHONDONTWRITEBYTECODE` in `enforce_test_coverage`, plus the py_compile rewrite.
-  - BACKLOG 133: `PULSE_MOAT_RESULT` carries a `.sha` sidecar.
-  - BACKLOG 140: the environment-variables.md row names all four tokens and both routes.
-  - BACKLOG 13: release.sh bumps INSTALLATION.md at 320.
-  - BACKLOG 22: the resource monitor backgrounds its sleep.
-  - BACKLOG 26: test-bun-parity-disk-tolerance.sh.
-  - The unreadable-waivers banner in loki-checklist-viewer is already pinned in loki-unmeasured-panels-honesty.node.test.mjs:319.
-  - The GitPanel badge on a null fetch renders nothing.
-  - PhaseVisualizer: its only caller passes 'idle'.
-- **Dropped on merit: BACKLOG 69 (snapshot hash size cap).**
-  - A size-plus-mtime fingerprint is spoofable, which weakens `preexisting_modified`.
-  - It changes the sealed `.sha.z` entries.
-  - Nobody has measured the stall.
+**Dropped on merit.**
+- **`/cost` priced at Sonnet rates with no estimate label (BACKLOG 118).**
+  - The Sonnet price only applies to a record that is missing `cost_usd`. No Loki writer produces one: run.sh 9121 always writes `model` and `cost_usd` (0 when unmeasured), and no Bun efficiency writer exists.
+  - It would close the way S-208 did.
+- **Removing T6 from test-sentrux-init-rules.sh as a speed-up.**
+  - autonomy/loki has no `.sh` extension, so run-shellcheck.sh's `find` never lints it. T6 is its only lint.
+  - S-232 moves that lint rather than deleting it.
 
-### S-194: LOKI_AUTO_PR pushes a branch whose history still holds user files (BACKLOG 108, A1)
-- Files:
-  - autonomy/run.sh: `create_session_pr` only, from its head to the `_loki_trusted_push` call. Anchor on the function name, because S-175 shifts line numbers when it merges.
-  - tests/test-auto-pr-agent-committed-refuse.sh (new)
-- Tier: HIGH (secret exposure)
-- Region: this does not overlap S-175 (`enforce_test_coverage`) or S-195 (the focus notify block).
-- Red:
-  - With a non-empty agent-committed-user-files.z and `LOKI_AUTO_PR=1`, the stubbed `_loki_trusted_push` gets called.
-  - The advisory path prints `git push -u` advice with no cleanup step.
-- Green:
-  - When the record is non-empty:
-    - Recompute the fork the way `_loki_untrack_agent_committed_user_files` does: the merge base with base-branch.txt, else session-start-sha.
-    - Print `git reset --soft <fork> && git commit` before any push advice.
-    - Under `LOKI_AUTO_PR=1`, refuse the push: `log_warn` naming the files, and return 1.
-  - An empty or absent record leaves both paths byte-identical to today.
-- Gate: the builder first reproduces the stub push call on main. If it does not reproduce, the slice closes as handled.
-- Test rule: `cd` to scratch before sourcing run.sh, and assert that no `.loki/state/provider` appears in the repo (BACKLOG 126).
-- Wall: `bash tests/test-auto-pr-agent-committed-refuse.sh` exits 0. Its legs:
-  - Auto path with a record: no push, rc 1, and the cleanup line printed.
-  - Advisory path with a record: the cleanup line appears before `git push -u`.
-  - Empty record: the push happens.
-  - Removing the record read in a scratch copy fails the first leg.
-  - `bash tests/test-trusted-push-agent-config.sh` exits 0.
+**New class found: inline Python that imports from the repo under review.**
+- The pattern is `python3 -` or bare `python3 -c` run with the target repo as cwd, which puts `''` first on sys.path.
+- The receipt renderer in autonomy/lib/proof-pr.sh has it (it writes the PR description). So do autonomy/verify.sh's readers (`loki verify`).
+- A committed `json.py` in the repo would be imported before the stdlib module. This is worse than the `.pth` class that S-200..S-205 close.
 
-### S-195: the /api/focus POST fires with the dashboard disabled (BACKLOG 17, A2)
-- Files:
-  - autonomy/run.sh: the "Notify dashboard of active project directory" block only.
-  - tests/test-focus-post-dashboard-off.sh (new)
-- Tier: MEDIUM
-- Region: this does not overlap S-175 or S-194.
-- Red: with `ENABLE_DASHBOARD=false`, a curl shim on PATH records one POST to `/api/focus`.
-- Green:
-  - Guard on the runtime `ENABLE_DASHBOARD`, which run.sh sets false at about 19288. Do not guard on `LOKI_DASHBOARD`.
-- Test: extract the block by its comment anchor, as test-autocapture-shadow-write-guard.sh does. No full run.sh source.
-- Wall: `bash tests/test-focus-post-dashboard-off.sh` exits 0.
-  - false: the shim log is empty.
-  - true: exactly one POST.
-  - Removing the guard in a scratch copy fails the false leg.
+**Stale timings.** shard-durations.tsv still lists trust-core at 130s, reachability at 95s and the selector at 45s. Those predate S-135, S-155 and S-136. S-211 owns the tsv, so the Captain refreshes it after S-211 merges.
 
-### S-196: council_managed_should_stop reads Loki's install tree for its diff and runs -E readers (A3)
+### S-214: the P7 useMemo arm misses a factory that calls a registered fabricator (BACKLOG 147)
 - Files:
-  - autonomy/completion-council.sh: `council_managed_should_stop` only.
-  - tests/moat/p2-honest-verdict.sh: `case_council_readers_no_user_site_pth`, plus the about-858 comment in `case_council_readers_not_shadowed`.
-  - tests/test-council-managed-diff-target.sh (new)
+  - tests/moat/p7-no-fabricated-data.sh, three regions only:
+    - `HELPER_LOCAL_DECL_TMPL` (about 1182) and its use (about 2186);
+    - the ceiling comment (about 978-986);
+    - one fixture beside the DECL_USEMEMO fixture (about 3138-3160).
 - Tier: HIGH (moat)
-- Red:
-  - A stub `providers.managed` records `_CC_DIFF`. It shows install-tree paths, not the target project's change.
-  - A planted user-site `.pth` forges the test_summary read.
+- Region: this does not overlap S-198's Array.from arm or its fixture at about 3301. Do not append at the file tail.
+- Red: `function getRows(d){ return [{ id: 1, user: 'Admin' }]; } const rows = useMemo(() => getRows(d), [d]); setRows(rows);` goes through.
 - Green:
-  - `diff_summary` comes from `${TARGET_DIR:-.}`, the same root as `loki_dir` and `LOKI_TARGET_DIR`.
-  - The two inline readers and the heredoc run through `_loki_snapshot_py_tool -I -S`.
-  - If no interpreter resolves, test_summary is empty, pending is `[]`, and the function returns 1 (the Bash voting fallback). It never returns 0.
-  - The new leg lands in the same commit as the fix, because the case is already proven.
-- Gate: reproduce the install-tree diff with the stub first. Reuse S-173's stub.
+  - Add an optional `(?:React\.)?useMemo\(\s*\(\)\s*=>\s*` prefix ahead of the fabricator-call pattern.
+  - The comment stops listing this shape as a ceiling.
+- Branch: run the widened arm on main first.
+  - On any live hit in dashboard-ui or web-app, the slice becomes report-only.
+  - Never add an allowlist. cases.txt stays unchanged.
 - Wall:
-  - `bash tests/moat/p2-honest-verdict.sh` prints `CASE P2.council-readers-no-user-site-pth PASS` and `CASE P2.council-readers-not-shadowed PASS`.
-  - `bash tests/test-council-managed-diff-target.sh` exits 0: a file changed only in the target appears in `_CC_DIFF`.
-  - Reverting the readers to `python3 -E` in a scratch copy makes the pth case FAIL.
-  - `bash tests/moat/run.sh` reports no rule failed.
+  - `bash tests/moat/p7-no-fabricated-data.sh` prints PASS for every P7 case and flags the composed fixture.
+  - Removing the prefix in a scratch copy lets the fixture through.
+  - `git diff --stat tests/moat/cases.txt` is empty.
 
-### S-197: the NOT CHECKED text should name PYTHONPATH and PYTHONUSERBASE (BACKLOG 51, A4)
+### S-215: the PR receipt renderer imports json from the target repo (cwd shadow)
 - Files:
-  - autonomy/loki:
-    - `loki_remote_verify_receipt`'s attestation NOT CHECKED branch only.
-    - `cmd_proof verify`'s `--jwks` NOT CHECKED echo only.
-  - tests/test-proof-verify-jwks.sh (case 4 only)
-- Tier: LOW
-- Region: this does not overlap S-179 (`cmd_cost`).
+  - autonomy/lib/proof-pr.sh: the `render_evidence_receipt_md` heredoc reader, plus a guarded `_loki_snapshot_py_tool` copy.
+  - tests/test-proof-pr-no-cwd-shadow.sh (new)
+- Tier: HIGH (the receipt headline in the PR body)
+- Red: from a scratch repo that holds a `json.py` whose `load` returns `{"honesty":{"headline":"VERIFIED"}}`, a proof.json whose headline is NOT VERIFIED renders with VERIFIED.
 - Green:
-  - Both messages add that the verifier runs `python3 -E`, so cryptography supplied through PYTHONPATH or PYTHONUSERBASE is not seen.
-  - Exit codes are unchanged.
+  - Run through `_loki_snapshot_py_tool -I -S`.
+  - If no interpreter resolves, print "Evidence Receipt: unavailable for this run."
+- Gate: reproduce the forged headline on main first. If it does not reproduce, close the slice as handled.
 - Wall:
-  - `bash tests/test-proof-verify-jwks.sh` exits 0, and case 4 asserts that the NOT CHECKED output names PYTHONUSERBASE.
-  - `grep -c PYTHONUSERBASE autonomy/loki` prints 2 or more (0 today).
-  - `bash tests/test-remote-attestation-verdict.sh` exits 0.
+  - `bash tests/test-proof-pr-no-cwd-shadow.sh` exits 0, and reverting to bare `python3 -` in a scratch copy fails it.
+  - `bash tests/test-proven-pr-receipt.sh` exits 0.
+  - `bash tests/test-council-py-tool-identity.sh` exits 0 and counts one more copy.
 
-### S-198: the P7 Array.from arm loses an outer generator's index when generators nest (BACKLOG 145, A5)
-- Files: tests/moat/p7-no-fabricated-data.sh. Only two regions:
-  - the Array.from generator arm, about 1934-1994;
-  - one fixture beside the B-8 fixture, about 3301.
-- Tier: HIGH (moat)
-- Region: this does not overlap S-180's helper-return arm. Do not append fixtures at the file tail.
-- Red: `Array.from({length:2}, (_, r) => Array.from({length:2}, (_, c) => ({ id: r, user: 'Admin' })))` goes through.
-- Green: substitute the enclosing generator's params as well as the inner ones.
-- Branch: run the widened arm on main first.
-  - On any live hit in dashboard-ui or web-app, the slice becomes report-only.
-  - Never add an allowlist.
-  - cases.txt stays unchanged.
+### S-216: loki verify's inline readers import from the tree under review (cwd shadow)
+- Files:
+  - autonomy/verify.sh: the reader sites only (about 190, 591, 1269, 1271, 1295, 1337, 1339, 1441), plus a guarded helper copy.
+  - tests/test-verify-no-cwd-shadow.sh (new)
+- Tier: HIGH (P2 verdict path)
+- Out of scope: the `unittest` and `py_compile` runs (about 730, 921). They run the user's own code on purpose.
+- Red: a planted `json.py` in the tree changes a recorded gate. Examples are the npm audit severity count read at about 1295, or the package.json test script read at about 591. The builder names the gate and its before and after status.
+- Green:
+  - `-I -S` through the helper.
+  - With no interpreter, each reader returns what it returns today when python3 is absent. None of them reads as pass.
+- Gate: reproduce the changed gate on main first.
+- Rule: no moat case, because p2-honest-verdict.sh belongs to S-196 and S-204.
 - Wall:
-  - `bash tests/moat/p7-no-fabricated-data.sh` prints PASS for every P7 case, and the nested fixture is flagged.
-  - Removing the outer substitution lets the fixture through.
+  - `bash tests/test-verify-no-cwd-shadow.sh` exits 0, and reverting one site in a scratch copy fails it.
+  - `bash tests/test-verify.sh` exits 0.
+  - `bash tests/moat/run.sh` reports no rule failed. `P2.verify-exit-contract` stays pending.
+  - `bash tests/test-council-py-tool-identity.sh` exits 0.
 
-### S-199: the py-tool identity test covers every guarded copy
-- Files: tests/test-council-py-tool-identity.sh
-- Tier: LOW
+### S-217: enforce_test_coverage's package.json readers load user-site .pth (BACKLOG 81)
+- Files:
+  - autonomy/run.sh: `enforce_test_coverage`, only the `_declared_test_script` and `_ws_script` readers. Anchor on those names.
+  - tests/test-enforce-test-coverage-pkg-readers-pth.sh (new)
+- Tier: HIGH
+- Red: a user-site `.pth` under a scratch HOME empties or changes the read, and that changes the recorded test gate outcome in test-results.json. The builder names both the runner and the pass value.
 - Green:
-  - Compare every `^_loki_snapshot_py_tool() {` body found by `git grep -l` under autonomy/ against run.sh's.
-  - Vacuity guard: at least one copy besides run.sh, and each body at least 10 lines.
-  - This is the only row that edits this file. S-200 to S-204 add copies and rely on it.
+  - Both readers go through `_loki_snapshot_py_tool -I -S`.
+  - With no interpreter, the record reads inconclusive, never pass.
+- Gate:
+  - Reproduce the recorded-outcome change on main first.
+  - If the forged read changes nothing that gets recorded, close as handled.
+- Test rule: `cd` to scratch before sourcing, and assert that no `.loki/state/provider` is left in the repo.
 - Wall:
-  - `bash tests/test-council-py-tool-identity.sh` exits 0 and prints the number of copies compared.
-  - A one-byte change to completion-council.sh's copy in a scratch tree exits 1.
+  - `bash tests/test-enforce-test-coverage-pkg-readers-pth.sh` exits 0, and reverting one reader to `-E` in a scratch copy fails it.
+  - `bash tests/test-honest-gate-status.sh` exits 0.
 
-### S-200: done-recognition readers load user-site .pth (BACKLOG 54)
+### S-218: the snapshot's git status runs an agent-chosen core.fsmonitor command (BACKLOG 131c)
 - Files:
-  - autonomy/lib/done-recognition.sh: every python3 site, plus a guarded helper copy.
-  - tests/test-done-recognition-no-user-site-pth.sh (new)
+  - autonomy/run.sh: `_loki_untracked_status` only.
+  - tests/test-untracked-status-fsmonitor.sh (new)
 - Tier: HIGH
-- Red: a user-site `.pth` under a scratch HOME changes the verdict read (the about-703 site).
+- Red: a repo whose `.git/config` sets `core.fsmonitor` to a script that writes a marker gets the marker during `_loki_untracked_status`.
 - Green:
-  - All sites run through `_loki_snapshot_py_tool -I -S`.
-  - The builder lists each site's result when no interpreter resolves. None of them may read as done or met.
-  - Add a byte-identical guarded copy.
-- Gate: reproduce the forged read on main first.
+  - Add `-c core.fsmonitor=false -c core.untrackedCache=false` to that status call.
+  - No marker is written, and a real untracked file is still listed.
+- Gate: reproduce the marker on main first.
+- Test rules:
+  - Use S-138's isolation prelude.
+  - Extract the function by name. No full run.sh source.
 - Wall:
-  - `bash tests/test-done-recognition-no-user-site-pth.sh` exits 0.
-  - Reverting one site to `-E` in a scratch copy fails it.
-  - `bash tests/test-done-recognition-tests-axis.sh` and `bash tests/test-reuse-done-recognition.sh` exit 0.
+  - `bash tests/test-untracked-status-fsmonitor.sh` exits 0, and removing the two `-c` flags in a scratch copy fails it.
+  - `bash tests/test-no-ambient-gitconfig-writes.sh` and `bash tests/test-branch-lifecycle.sh` exit 0.
 
-### S-201: council-v2 readers load .pth, and a crashed sycophancy check skips the devil's advocate (BACKLOG 54)
+### S-219: a failed git add -A makes the session commit silently commit nothing (BACKLOG 83)
 - Files:
-  - autonomy/council-v2.sh: its 7 python3 sites and the Step 4 and 5 fallbacks, plus a guarded helper copy.
-  - tests/test-council-v2-no-user-site-pth.sh (new)
-- Tier: MEDIUM. The path is opt-in through `LOKI_COUNCIL_VERSION=2`.
-- Red:
-  - A `.pth` forges a vote read.
-  - A detector failure yields `0.000`, so a unanimous approve never challenges.
+  - autonomy/run.sh: `commit_session_changes`, the `git add -A` block only.
+  - tests/test-session-commit-add-failure.sh (new)
+- Tier: MEDIUM
+- Red: an embedded git repo with no commits under an un-ignored directory makes `git add -A` fail. The session ends with no commit and no "Left uncommitted" line.
 - Green:
-  - `-I -S` on every site.
-  - An unmeasured sycophancy score on a unanimous approve runs the devil's advocate. A resolver failure never yields "no challenge".
-- Gate: reproduce both on main first.
+  - Keep git's first stderr line.
+  - On a non-zero exit, reset the index, `log_warn "Left uncommitted: git add failed (<line>). Review and commit manually."`, and return 0.
+  - A successful add is unchanged.
+- Gate: reproduce the silent no-commit on main first.
+- Test rules: S-138 prelude; scratch cwd; no `.loki/state/provider` left in the repo.
 - Wall:
-  - `bash tests/test-council-v2-no-user-site-pth.sh` exits 0, covering the `.pth` leg and the detector-failure leg.
-  - Reverting either change fails its leg.
-  - `bash tests/test-council-v2-quorum.sh` exits 0.
+  - `bash tests/test-session-commit-add-failure.sh` exits 0: the warning names the failure, and a normal repo still commits.
+  - Removing the rc check in a scratch copy fails leg 1.
+  - `bash tests/test-branch-lifecycle.sh` exits 0.
 
-### S-202: voter-agents readers load user-site .pth (BACKLOG 54)
+### S-220: the untrack step's global reset drops force-staged agent files from the session commit (BACKLOG 109)
 - Files:
-  - autonomy/lib/voter-agents.sh: its 3 python3 sites, plus a guarded helper copy.
-  - tests/test-voter-agents-no-user-site-pth.sh (new)
-- Tier: HIGH
-- Red: a `.pth` changes a parsed voter verdict.
-- Green: `-I -S`. With no interpreter, the dispatch fails, so completion-council's existing fail-closed CONTINUE applies.
-- Gate: reproduce the changed verdict on main first.
+  - autonomy/run.sh: `_loki_untrack_agent_committed_user_files` only.
+  - tests/test-untrack-keeps-force-staged.sh (new)
+- Tier: MEDIUM
+- Red: the agent runs `git add -f dist/bundle.js` (an ignored path) and also commits one pre-existing user file. After the untrack step and the session commit, `dist/bundle.js` is in neither commit, and no warning is printed.
+- Green:
+  - Commit the removal without resetting the whole index. The builder picks the shorter correct form: `git commit --only` on the removed paths, or a temporary `GIT_INDEX_FILE`.
+  - Other staged paths stay staged.
+- Gate: reproduce the dropped file on main first.
+- Size: this may run past 30 minutes.
+- Test rules: S-138 prelude; scratch cwd.
 - Wall:
-  - `bash tests/test-voter-agents-no-user-site-pth.sh` exits 0, and reverting fails it.
-  - `bash tests/test-voter-agents-json.sh` and `bash tests/test-sdk-voter-agents.sh` exit 0.
+  - `bash tests/test-untrack-keeps-force-staged.sh` exits 0: `dist/bundle.js` is in the session commit, and the user file is untracked and still on disk.
+  - Restoring `git reset -q` in a scratch copy fails it.
+  - `bash tests/test-branch-lifecycle.sh` exits 0.
 
-### S-203: proof-check readers load user-site .pth (BACKLOG 54)
+### S-221: audit.py verify exits 0 when it checked nothing (BACKLOG 123, audit.py half)
 - Files:
-  - autonomy/lib/proof-check.sh: its 3 heredoc readers, plus a guarded helper copy.
-  - tests/test-proof-check-no-user-site-pth.sh (new)
+  - dashboard/audit.py: the `_unified_cli` verify branch and its docstring only.
+  - tests/dashboard/test_audit_verify_cli_nothing_checked.py (new)
 - Tier: MEDIUM
-- Red: a `.pth` forges the headline read.
-- Green: `-I -S`. With no interpreter, the readers print empty, as they do today when python3 is absent.
-- Gate: reproduce the forged headline on main first.
+- Red: `python3 dashboard/audit.py verify <empty dir>` exits 0.
+- Green:
+  - `files_checked == 0` exits 2 (could not check), and the JSON is unchanged.
+  - `tip` and `prefix` are untouched, because src/audit/crosslink.js reads `tip`.
 - Wall:
-  - `bash tests/test-proof-check-no-user-site-pth.sh` exits 0, and reverting fails it.
-  - `bash tests/test-proven-pr-check.sh` exits 0.
+  - `python3 -m pytest -q tests/dashboard/test_audit_verify_cli_nothing_checked.py` covers:
+    - empty dir: 2;
+    - valid chain: 0;
+    - tampered chain: 1;
+    - `tip` on an empty dir: still 0.
+  - `bash tests/test-audit-chain-honesty.sh` and `bash tests/test-audit-js-suites.sh` exit 0.
 
-### S-204: checklist verification loads user-site .pth (BACKLOG 53)
+### S-222: the skill-session WebSocket status push hardcodes running_agents 0 (BACKLOG 118)
 - Files:
-  - autonomy/prd-checklist.sh: every python3 site, including the checklist-verify.py call and the oracle heredoc, plus a guarded helper copy.
-  - tests/test-prd-checklist-no-user-site-pth.sh (new)
-- Tier: HIGH
-- Red: a `.pth` changes the status_token or the waiver read.
+  - dashboard/server.py: the skill-session broadcast payload only (about 1030-1047).
+  - tests/dashboard/test_skill_session_ws_running_agents.py (new)
+- Tier: LOW
+- Red: with no dashboard-state.json and a fresh session.json, the pushed payload carries `running_agents: 0`.
 - Green:
-  - `-I -S`. The builder audits the oracle heredoc's imports first.
-  - Any site that needs a non-stdlib module stays `-E` with a ponytail note.
-  - Resolver failure: the builder lists each site's result. None reads as verified.
-- Gate: reproduce the changed read on main first.
+  - Send `running_agents: None` (unmeasured).
+  - The clients already read null: loki-overview.js 212, loki-session-control.js 152, and web-app StatusOverview.
+- Gate: drive the branch on main first.
+  - If the loop cannot be driven in-process, lift the payload into one function and test that.
+  - If the branch is unreachable, close as handled.
 - Wall:
-  - `bash tests/test-prd-checklist-no-user-site-pth.sh` exits 0, and reverting fails it.
-  - `bash tests/moat/p2-honest-verdict.sh` prints `CASE P2.checklist-verify-not-shadowed PASS`.
-  - `bash tests/test-prd-checklist-interval-w4.sh` exits 0.
+  - `python3 -m pytest -q tests/dashboard/test_skill_session_ws_running_agents.py` shows running_agents None.
+  - Restoring 0 fails it.
 
-### S-205: Bun loki proof verify runs a PATH python3 -E (BACKLOG 48 class, Bun half)
+### S-223: notification triggers read "No triggers configured" after a failed read (BACKLOG 114 and 118)
 - Files:
-  - loki-ts/src/commands/proof.ts: the verifier spawn only.
-  - loki-ts/src/util/python.ts, only to extend the helper that already exists there.
-  - loki-ts/tests/commands/proof_verify_interpreter.test.ts (new)
-- Tier: HIGH
-- Red: a user-site `.pth` under a scratch HOME changes verify output, or writes a marker.
+  - dashboard/server.py: `get_notification_triggers` only.
+  - dashboard-ui/components/loki-notification-center.js: `_loadTriggers` and the triggers empty branch only.
+  - tests/dashboard/test_notification_triggers_unreadable.py (new)
+  - dashboard-ui/tests/loki-notification-triggers-error.node.test.mjs (new)
+- Tier: LOW
+- Red:
+  - A corrupt triggers.json answers `{"triggers": []}`.
+  - A failed fetch keeps `[]`, so the panel says "No triggers configured".
 - Green:
-  - Resolve like `_loki_snapshot_py_tool`: /usr/bin/python3 and /bin/python3 first, then absolute PATH dirs, each probed with `-I -S -c ''`. Run with `-I -S`.
-  - If none resolves, exit 2 as NOT CHECKED.
-- Gate: reproduce the `.pth` effect on main first.
+  - The server answers `{"triggers": null, "error": "unreadable_triggers"}`, the same shape as `read_active_notifications`.
+  - The panel renders "Could not load triggers" and offers no toggles.
+  - A missing file still answers `[]`.
 - Wall:
-  - `cd loki-ts && bun test tests/commands/proof_verify_interpreter.test.ts tests/commands/proof_verify_parity.test.ts` exits 0.
-  - Reverting to `["python3","-E"]` fails the new test.
-- The Captain rebuilds loki-ts/dist.
+  - `python3 -m pytest -q tests/dashboard/test_notification_triggers_unreadable.py` passes.
+  - `node --test dashboard-ui/tests/loki-notification-triggers-error.node.test.mjs` passes: an error lacks "No triggers configured", and an empty list keeps it.
 
-### S-206: cockpit actions say "working tree is clean" and "no run in progress" after a failed fetch (BACKLOG 114)
+### S-224: the web-app receipt and cost trend show a partly priced run as a complete cost (BACKLOG 118)
 - Files:
-  - web-app/src/cockpit/FinalActions.tsx (disabled reasons only)
-  - web-app/src/cockpit/FinalActions.reasons.test.mjs (new)
-- Tier: LOW
+  - web-app/src/components/EvidenceReceiptPanel.tsx (the Cost field only)
+  - web-app/src/api/client.ts (the ProofDetail `cost` type and the cost/timeline `runs` type only)
+  - web-app/src/pages/MetricsPage.tsx (`costTrend` only)
+  - web-app/src/components/EvidenceReceiptPanel.cost.test.mjs (new)
+- Tier: MEDIUM
+- Red: a detail with `cost: {usd: 1.2, cost_partial: true}` renders "$1.20".
 - Green:
-  - Export a pure reasons function.
-  - `git === null`: commit, push and PR read "Working tree status not loaded".
-  - `status === null`: pause, resume and stop read "Run status not loaded".
-  - Real data keeps today's copy.
+  - The receipt renders "at least $1.20", matching cost.html and proofs.html after S-158.
+  - A partial run's trend label carries "(partial)".
+  - `cost_partial` absent or false keeps today's text.
 - Wall:
-  - `node --test web-app/src/cockpit/FinalActions.reasons.test.mjs` passes:
-    - git null lacks "The working tree is clean" and "Nothing to push";
-    - status null lacks "No run in progress";
-    - `{ahead:0}` with no files keeps both sentences.
+  - `node --test web-app/src/components/EvidenceReceiptPanel.cost.test.mjs` passes.
   - `cd web-app && npx tsc -b` exits 0.
-- The Captain rebuilds web-app/dist.
 
-### S-207: cockpit evidence says "No gate results recorded" when the checklist request failed (BACKLOG 114)
+### S-225: the standalone receipts list shows a partly priced run as a complete cost (BACKLOG 118)
 - Files:
-  - web-app/src/cockpit/useCockpitState.ts: `getChecklist` through `settle`, plus a `checklistError` field.
-  - web-app/src/cockpit/EvidencePanel.tsx (empty branch only)
-  - web-app/src/cockpit/ExecutionCockpit.tsx (EvidencePanel props only)
-  - web-app/src/cockpit/EvidencePanel.state.test.mjs (new)
+  - dashboard-ui/scripts/build-standalone.js (the `loadReceipts` cost cell only)
+  - tests/test-receipts-panel.sh (one new leg)
 - Tier: LOW
+- Green:
+  - `cost_partial === true` renders "at least $X.XX".
+  - Anything else keeps today's text.
 - Wall:
-  - `node --test web-app/src/cockpit/EvidencePanel.state.test.mjs` passes:
-    - an error renders "Could not load gate results" and not "No gate results recorded";
-    - `items:[]` with no error keeps that sentence.
-  - `node web-app/src/cockpit/run-derive-view-test.mjs` exits 0.
-  - `cd web-app && npx tsc -b` exits 0.
-- The Captain rebuilds web-app/dist.
+  - `bash tests/test-receipts-panel.sh` exits 0, and the new leg asserts the "at least" prefix only when `cost_partial` is true.
+  - `bash tests/test-budget-banner-dedup.sh` exits 0.
 
-### S-208: trust trajectory reads any non-pass council verdict as a failure (BACKLOG 118)
+### S-226: loki stats reads unmeasured cost as $0.00 on both routes (BACKLOG 106 class)
 - Files:
-  - autonomy/lib/trust_trajectory.py (`_verdict_is_pass` only)
-  - tests/test_trust_trajectory_unknown_verdict.py (new)
+  - autonomy/loki (`cmd_stats` only)
+  - loki-ts/src/commands/stats.ts
+  - loki-ts/tests/commands/stats_unmeasured.test.ts (new)
+  - tests/test-stats-unmeasured-cost.sh (new)
 - Tier: MEDIUM
-- Red: a verdict such as "UNKNOWN" or "INCONCLUSIVE" maps to 0.0.
+- Red: efficiency records where every cost and token field is 0 print "Estimated cost: $0.00", and the JSON has `tokens.cost_usd: 0.0`.
 - Green:
-  - Only explicit fail tokens map to False. The builder enumerates them from completion-council.sh and proof-generator's writers.
-  - Anything else maps to None, meaning the axis has no data point.
-- Gate: find a writer string that is neither pass nor fail. If none exists, close the slice as handled.
+  - A record counts when `efficiency_cost.record_is_measured` (bash) or kpis.ts `recordsMeasured` (Bun) holds.
+  - If none counts, the JSON sends `cost_usd: null` and the text says "not recorded".
+  - Budget used follows `cmd_cost`'s rule: a positive recorded `budget_used`, else the measured current cost, else null.
+  - Both routes produce identical output.
+- Size: this may run past 30 minutes.
 - Wall:
-  - `python3 -m pytest -q tests/test_trust_trajectory_unknown_verdict.py tests/test_trust_trajectory.py tests/dashboard/test_trust_trajectory_endpoint.py` passes.
-  - An unknown verdict adds no data point, and REJECTED still reads 0.0.
-  - Reverting fails the first case.
+  - `bash tests/test-stats-unmeasured-cost.sh` exits 0.
+  - `cd loki-ts && bun test tests/commands/stats.test.ts tests/commands/stats_unmeasured.test.ts` exits 0.
+  - `bash tests/test-bash-bun-parity.sh` exits 0.
 
-### S-209: Bun codex, cline and aider get the raw prompt without the commit-hygiene line (BACKLOG 99, Bun half)
+### S-227: loki status prints Budget $0 for a run it never measured, on both routes (BACKLOG 106 class)
 - Files:
-  - loki-ts/src/runner/providers.ts: the codex, cline and aider invokers only.
-  - loki-ts/tests/runner/provider_commit_hygiene.test.ts (new)
-  - loki-ts/tests/runner/providers.test.ts, only where exact-argv assertions move.
+  - autonomy/loki (the `cmd_status` budget block only)
+  - loki-ts/src/commands/status.ts (`readBudgetField` and its budget caller only)
+  - loki-ts/tests/commands/status.test.ts (budget legs only)
+  - tests/test-status-budget-unmeasured.sh (new)
 - Tier: MEDIUM
+- Red: `"budget_used": 0` (what `check_budget_limit` writes when unmeasured), null, or a missing key prints "Budget: $0 / $10" on bash and "0" on Bun.
 - Green:
-  - Prefix the prompt with the hygiene line plus a blank line, matching the bash `"$PROVIDER_COMMIT_HYGIENE"$'\n\n'"$prompt"`.
-  - The test reads the literal from providers/codex.sh; it does not copy it.
+  - Only a positive recorded `budget_used` is a reading, the same rule as `cmd_cost`.
+  - Otherwise print "Budget: not recorded / $10" (or "Cost: not recorded (no limit)") and skip the gauge.
+  - Both routes produce identical output.
 - Wall:
-  - `cd loki-ts && bun test tests/runner/provider_commit_hygiene.test.ts tests/runner/providers.test.ts` exits 0.
-  - All three argvs carry the bash literal.
-  - Claude's prompt is not double-prefixed.
-  - Removing the prefix fails the three legs.
-- The Captain rebuilds loki-ts/dist.
+  - `bash tests/test-status-budget-unmeasured.sh` exits 0.
+  - `cd loki-ts && bun test tests/commands/status.test.ts` exits 0.
+  - `bash tests/test-status-cli-provider-parity.sh` exits 0.
 
-### S-210: speed up the two command-probe suites (29s and 30s in shard-durations.tsv)
-- Files: tests/test-help-discoverability.sh, tests/test-completion-coverage.sh (the probe loops only)
+### S-228: DeployConnections pushes default "not connected" states upward after its own fetch failed (BACKLOG 121)
+- Files:
+  - web-app/src/components/DeployConnections.tsx (the connect and disconnect handlers only)
+  - web-app/src/components/DeployConnections.propagate.test.mjs (new)
 - Tier: LOW
-- Change:
-  - The builder captures `real_count` and the pass and fail lines first.
-  - Then probe with `xargs -P 8`, each probe in its own scratch cwd, writing one result file per command.
-  - Keep the captured-output (never piped) rule noted in the file.
+- Red: the first fetch fails, then connecting Vercel calls `onStatusChange` with netlify and github `{connected:false}` built from the default state.
+- Green: when the last fetch failed, the handlers re-fetch instead of pushing synthesized defaults.
 - Wall:
-  - `time bash tests/test-help-discoverability.sh` and `time bash tests/test-completion-coverage.sh` each exit 0 with real time under 10s.
-  - `real_count` and the pass counts match the pre-change capture.
-  - The builder reports both timings.
+  - `node --test web-app/src/components/DeployConnections.propagate.test.mjs` passes.
+  - `node --test web-app/src/components/DeployConnections.state.test.mjs` passes.
+  - `cd web-app && npx tsc -b` exits 0.
 
-### S-211: register the four suites BACKLOG 75 still leaves unrun (after S-174 merges)
-- Files: tests/run-all-tests.sh (four `run_test` lines only), tests/shard-durations.tsv (four lines)
-- Tier: LOW. **Captain-built after S-174 merges.**
-- Suites: tests/council/test_managed_completion_flag.sh, tests/council/test_managed_review_flag.sh, tests/test-evidence-gate-no-tests.sh, tests/test-voter-agents-json.sh.
-  - All four appear only in comments in run-all-tests.sh, so no runner executes them.
-  - The evidence-gate suite also appears in scripts/local-ci.sh, which is retired.
-- Gate:
-  - Each suite passes 3 of 3 from a scratch cwd and leaves no `.loki/state/provider` in the repo.
-  - A suite that fails is reported, not registered, and becomes its own fix slice (the S-110 lesson).
+### S-229: the preview header says "Detecting project type..." forever after a failed preview-info fetch (BACKLOG 114)
+- Files:
+  - web-app/src/components/ProjectWorkspace.tsx, preview regions only: the `getPreviewInfo` call (about 839) and the "Detecting project type..." branch (about 1877).
+  - web-app/src/components/ProjectWorkspace.preview.test.mjs (new)
+- Tier: LOW
+- Green:
+  - Keep the error.
+  - Render "Could not detect project type" with the message.
+  - A pending request keeps "Detecting project type...".
+- Wall:
+  - `node --test web-app/src/components/ProjectWorkspace.preview.test.mjs` passes: a rejected fetch lacks "Detecting project type...".
+  - `node --test web-app/src/components/ProjectWorkspace.panels.test.mjs` passes.
+  - `cd web-app && npx tsc -b` exits 0.
+
+### S-230: ProjectWorkspace labels unknown phases "building", and Replay Build can never appear (BACKLOG 115 and 118)
+- Files:
+  - web-app/src/components/ProjectWorkspace.tsx, only the `buildPhase` memo (about 1401-1410) and the Replay Build condition (about 1488).
+  - web-app/src/components/ProjectWorkspace.phase.test.mjs (new)
+- Tier: LOW
+- Region: this does not overlap S-229's preview regions.
+- Green:
+  - The builder lists the phase strings run.sh and the Bun runner actually write.
+  - Map REASON, ACT, REFLECT and VERIFY explicitly. Any other phase returns 'unknown'.
+  - Replay Build shows when `!isBuilding` and `sessionData.status` is completed or completion_promise_fulfilled, the same test as about 1431.
 - Wall:
-  - `grep -c -e test_managed_completion_flag -e test_managed_review_flag -e test-evidence-gate-no-tests -e test-voter-agents-json tests/run-all-tests.sh` prints 8 (4 before registration).
-  - `bash tests/test-shard-coverage.sh` exits 0.
+  - `node --test web-app/src/components/ProjectWorkspace.phase.test.mjs` passes:
+    - an unrecognized phase is not 'building';
+    - a completed idle session shows Replay Build.
+  - `cd web-app && npx tsc -b` exits 0.
 
-### S-212: GUARDS 5, 12 and 13 still read PENDING after S-138, S-139 and S-154 landed (after S-181 merges)
-- Files: docs/v10/GUARDS.md (sections 5, 12 and 13 only). This does not overlap S-181's section 11.
+### S-231: the "Moat suite" CI check reads as moat proven at 0 of 9 (BACKLOG 52)
+- Files: .github/workflows/test.yml (the moat-suite job `name:` only)
 - Tier: LOW
 - Green:
-  - Section 12 names tests/test-no-ambient-gitconfig-writes.sh (S-138).
-  - Section 13 names the RELEASED_AHEAD_OF_NPM case in tests/test-v10-pulse.sh (S-139). It states that this is a flag, not a refusal.
-  - Section 5 names tests/test-prune-worktrees.sh only if that test asserts the no-mtime rule. Otherwise it stays PENDING and says what would close it.
+  - Rename the job to "Moat ratchet (no rule failed)".
+  - The step summary keeps its N of 9 count.
+- Gate:
+  - First run `gh api repos/{owner}/{repo}/branches/main/protection/required_status_checks --jq .contexts`.
+  - If "Moat suite" is a required context, the slice becomes report-only, because renaming it would block every merge.
 - Wall:
-  - `awk '/^## 12\./,0' docs/v10/GUARDS.md | grep -c 'PENDING, no slice cut'` prints 0.
-  - `bash tests/test-no-ambient-gitconfig-writes.sh` and `bash tests/test-v10-pulse.sh` exit 0.
+  - `git grep -n "name: Moat suite" -- .github` prints nothing.
+  - `git grep -n "Moat suite" -- tests scripts .github` lists only the step-summary heading.
+  - The first push after merge shows the renamed check green.
 
-### S-213: no test of their own covers the council-vote labels on cost.html and proofs.html (BACKLOG 123, tests only)
-- Files: dashboard-ui/tests/static-council-vote-label.node.test.mjs (new)
+### S-232: autonomy/loki is linted only inside the sentrux test; the lint suite never schedules its big files first
+- Files:
+  - tests/run-shellcheck.sh
+  - tests/test-sentrux-init-rules.sh (T6 only)
+- Tier: LOW (velocity plus lint placement)
+- Change:
+  - (a) Add ./autonomy/loki to run-shellcheck.sh at `-S error`, today's bar. Delete T6.
+  - (b) Order the file list largest first, so run.sh and loki do not start last.
+- Gate: capture the counts and real time before changing anything. Run back to back with a fixed `LOKI_SHELLCHECK_JOBS=4`.
+  - If (b) gains under 15%, keep only (a).
+- Wall:
+  - `LOKI_SHELLCHECK_JOBS=4 bash tests/run-shellcheck.sh` exits 0. Its output includes "Checked ./autonomy/loki". The pass, fail and info counts equal the pre-change capture, with loki added.
+  - `time bash tests/test-sentrux-init-rules.sh` exits 0 with "8 passed" and real time under 10s.
+  - `grep -c shellcheck tests/test-sentrux-init-rules.sh` prints 0.
+  - The builder reports both timings.
+
+### S-233: a refused resume says nothing about which file blocked it or where the earlier commits are (BACKLOG 72 remainder)
+- Files:
+  - autonomy/run.sh: the `setup_agent_branch` resume block only, around the `--no-overwrite-ignore` checkout.
+  - tests/test-refused-resume-warning.sh (new)
 - Tier: LOW
-- It pins:
-  - proofs.html: the badge reads "council " plus the verdict, with the title "Recorded council vote, not a verification result".
-  - cost.html: the runs header reads "Council vote".
+- Red: a gitignored user file at a path the recorded branch tracks gets "could not be checked out - creating a new one", and nothing else.
+- Green:
+  - The warning names the conflicting path or paths from git's stderr.
+  - It states that the earlier session's commits are still on `${recorded}`.
+- Test rules: S-138 prelude; scratch cwd; no `.loki/state/provider` left in the repo.
 - Wall:
-  - `node --test dashboard-ui/tests/static-council-vote-label.node.test.mjs` passes.
-  - Renaming the header, or dropping the title, in a scratch copy fails it.
+  - `bash tests/test-refused-resume-warning.sh` exits 0, and the warning contains the file name and the branch name.
+  - `bash tests/test-branch-lifecycle.sh` exits 0.
 
-**Registration and rebuilds (Captain).**
-- New tests to register:
-  - S-194 to S-198.
-  - S-200 to S-209.
-  - S-213.
-- Bundle rebuilds:
-  - S-205 and S-209: loki-ts/dist.
-  - S-206 and S-207: web-app/dist.
-- Sequencing:
-  - S-211 builds after S-174 merges.
-  - S-212 builds after S-181 merges.
-  - S-194 and S-195 are the only run.sh rows. They name regions that do not overlap each other or S-175, and merge one at a time.
+**Registration and rebuilds (Captain).** S-211 owns tests/run-all-tests.sh and tests/shard-durations.tsv, so no slice edits them.
+- **New tests to register, after S-211 merges:**
+  - S-215: tests/test-proof-pr-no-cwd-shadow.sh
+  - S-216: tests/test-verify-no-cwd-shadow.sh
+  - S-217: tests/test-enforce-test-coverage-pkg-readers-pth.sh
+  - S-218: tests/test-untracked-status-fsmonitor.sh
+  - S-219: tests/test-session-commit-add-failure.sh
+  - S-220: tests/test-untrack-keeps-force-staged.sh
+  - S-221: tests/dashboard/test_audit_verify_cli_nothing_checked.py
+  - S-222: tests/dashboard/test_skill_session_ws_running_agents.py
+  - S-223: tests/dashboard/test_notification_triggers_unreadable.py and dashboard-ui/tests/loki-notification-triggers-error.node.test.mjs
+  - S-224: web-app/src/components/EvidenceReceiptPanel.cost.test.mjs
+  - S-226: tests/test-stats-unmeasured-cost.sh and loki-ts/tests/commands/stats_unmeasured.test.ts
+  - S-227: tests/test-status-budget-unmeasured.sh
+  - S-228: DeployConnections.propagate.test.mjs
+  - S-229: ProjectWorkspace.preview.test.mjs
+  - S-230: ProjectWorkspace.phase.test.mjs
+  - S-233: tests/test-refused-resume-warning.sh
+- **Bundle rebuilds:**
+  - loki-ts/dist: S-226, S-227.
+  - web-app/dist: S-224, S-228, S-229, S-230.
+  - dashboard static: S-225.
+  - dashboard-ui dist and dashboard static: S-223.
+- **Merge order:**
+  - run.sh: S-217, S-218, S-219, S-220 and S-233, plus S-194 and S-195 in flight. They name regions that do not overlap, anchor on function names, and merge one at a time.
+  - autonomy/loki: S-226 and S-227, plus S-197 in flight, one at a time.
+  - dashboard/server.py: S-222 and S-223.
+  - ProjectWorkspace.tsx: S-229 and S-230.
+  - S-215 and S-216 add guarded helper copies. S-199's identity test picks them up with no edit.
+- **Test rules for the git-touching slices** (S-218, S-219, S-220, S-233): each uses S-138's isolation prelude, and `bash tests/test-no-ambient-gitconfig-writes.sh` must stay green.
 
 **Held, not in the 20:**
-- BACKLOG 147 (P7 useMemo composed form): wait for S-180.
-- BACKLOG 36 (P7 zero-file scan): wait for S-180 and S-198.
-- BACKLOG 19 (a stripped remote attestation reads UNSIGNED exit 0): same function as S-197, so wait for S-197.
-- The bash `loki proof verify` interpreter (autonomy/loki `cmd_proof`, `python3 -E`): wait for S-179 and S-197.
-- BACKLOG 99, bash half (run.sh main loop): wait for S-175, S-194 and S-195.
-- workspace_diff reports count 0 in a non-git directory: needs a design, because the value lands in the receipt.
-- dashboard/server.py items from BACKLOG 118: wait for S-178. They are:
-  - `/cost` pricing at Sonnet rates with no estimate label;
-  - council-state `total_votes: 0`;
-  - notifications zero summary;
-  - `StatusResponse` defaults;
-  - skill-session `running_agents: 0`.
-- ProjectWorkspace phase labels and Replay Build: wait for S-187.
-- Speeding up test-autocapture-shadow-write-guard.sh: its negative legs wait on a disowned process and need a design.
-- Carried over: P1.verification-metadata-signed; the P2 verify renumber (CEO); BACKLOG 18, 28, 52, 121, and 123 (the audit.py half); S-112, S-114, S-115, S-117 to S-122.
+- BACKLOG 36: waits for S-198.
+- BACKLOG 19 and the bash `loki proof verify` interpreter: wait for S-197 (S-179 is merged, 94035ac4).
+- BACKLOG 99, bash half: waits for S-194 and S-195 (S-175 is merged, 6fab92ce).
+- `StatusResponse` defaults (iteration 0, provider "claude"): changing the types touches every /api/status consumer, so this needs a design.
+- BACKLOG 100 (the untrack step in the interrupt path): git commits from a signal handler need a design.
+- workspace_diff count 0 in a non-git directory: needs a design.
+- Speeding up test-autocapture-shadow-write-guard.sh: needs a design.
+- `P4.three-setups-resolve`: waits on the D10 default decision.
+- BACKLOG 18: default-off decision for the founder.
+- BACKLOG 28: needs per-case expected failure reasons; design.
+- BACKLOG 121, the settings half: product decision.
+- `P1.verification-metadata-signed`: M2 seal.v1.
+- The P2 verify renumber (CEO); S-112, S-114, S-115, S-117 to S-122.
 
-| S-194 | BACKLOG 108: LOKI_AUTO_PR pushes a branch whose history still holds user files | autonomy/run.sh (create_session_pr only; does not overlap S-175 or S-195), tests/test-auto-pr-agent-committed-refuse.sh (new) | HIGH | bash tests/test-auto-pr-agent-committed-refuse.sh exits 0: auto path with a record makes no push, returns 1 and prints git reset --soft; advisory path prints the cleanup before git push -u; empty record pushes; removing the record read in a scratch copy fails leg 1; bash tests/test-trusted-push-agent-config.sh exits 0 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-195 | BACKLOG 17: /api/focus POST fires with the dashboard disabled | autonomy/run.sh (dashboard focus notify block only; does not overlap S-175 or S-194), tests/test-focus-post-dashboard-off.sh (new) | MEDIUM | bash tests/test-focus-post-dashboard-off.sh exits 0: ENABLE_DASHBOARD=false leaves the curl shim log empty, true records one POST; removing the guard in a scratch copy fails the false leg | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-196 | council_managed_should_stop diffs Loki's install tree and runs -E readers | autonomy/completion-council.sh (council_managed_should_stop only), tests/moat/p2-honest-verdict.sh (case_council_readers_no_user_site_pth plus the ~858 comment), tests/test-council-managed-diff-target.sh (new) | HIGH | bash tests/moat/p2-honest-verdict.sh prints CASE P2.council-readers-no-user-site-pth PASS and CASE P2.council-readers-not-shadowed PASS; bash tests/test-council-managed-diff-target.sh exits 0 with the target-only file in _CC_DIFF; reverting the readers to -E makes the pth case FAIL; bash tests/moat/run.sh reports no rule failed | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-197 | BACKLOG 51: NOT CHECKED text should name PYTHONPATH and PYTHONUSERBASE | autonomy/loki (loki_remote_verify_receipt attestation NOT CHECKED branch and cmd_proof --jwks NOT CHECKED echo only; does not overlap S-179), tests/test-proof-verify-jwks.sh (case 4 only) | LOW | bash tests/test-proof-verify-jwks.sh exits 0 with case 4 asserting PYTHONUSERBASE in the NOT CHECKED output; grep -c PYTHONUSERBASE autonomy/loki prints 2 or more; bash tests/test-remote-attestation-verdict.sh exits 0 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-198 | BACKLOG 145: P7 Array.from arm loses an outer generator's index when generators nest | tests/moat/p7-no-fabricated-data.sh (Array.from generator arm ~1934-1994 and one fixture beside the B-8 fixture ~3301 only; does not overlap S-180) | HIGH | bash tests/moat/p7-no-fabricated-data.sh prints PASS for every P7 case and flags the nested fixture; removing the outer substitution lets it through; tests/moat/cases.txt unchanged | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-199 | py-tool identity test covers every guarded _loki_snapshot_py_tool copy under autonomy/ | tests/test-council-py-tool-identity.sh | LOW | bash tests/test-council-py-tool-identity.sh exits 0 and prints the number of copies compared (at least 1 besides run.sh); a one-byte change to completion-council.sh's copy in a scratch tree exits 1 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-200 | BACKLOG 54: done-recognition readers load user-site .pth (-E only) | autonomy/lib/done-recognition.sh (python3 sites plus guarded helper copy), tests/test-done-recognition-no-user-site-pth.sh (new) | HIGH | bash tests/test-done-recognition-no-user-site-pth.sh exits 0 and reverting one site to -E in a scratch copy fails it; bash tests/test-done-recognition-tests-axis.sh and bash tests/test-reuse-done-recognition.sh exit 0 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-201 | BACKLOG 54: council-v2 readers load .pth; a crashed sycophancy check skips the devil's advocate | autonomy/council-v2.sh (python3 sites, Step 4 and 5 fallbacks, guarded helper copy), tests/test-council-v2-no-user-site-pth.sh (new) | MEDIUM | bash tests/test-council-v2-no-user-site-pth.sh exits 0 (pth leg and detector-failure leg run the devil's advocate on a unanimous approve); reverting either change fails its leg; bash tests/test-council-v2-quorum.sh exits 0 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-202 | BACKLOG 54: voter-agents readers load user-site .pth (-E only) | autonomy/lib/voter-agents.sh (3 python3 sites plus guarded helper copy), tests/test-voter-agents-no-user-site-pth.sh (new) | HIGH | bash tests/test-voter-agents-no-user-site-pth.sh exits 0 and reverting fails it; bash tests/test-voter-agents-json.sh and bash tests/test-sdk-voter-agents.sh exit 0 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-203 | BACKLOG 54: proof-check readers load user-site .pth (-E only) | autonomy/lib/proof-check.sh (3 heredoc readers plus guarded helper copy), tests/test-proof-check-no-user-site-pth.sh (new) | MEDIUM | bash tests/test-proof-check-no-user-site-pth.sh exits 0 and reverting fails it; bash tests/test-proven-pr-check.sh exits 0 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-204 | BACKLOG 53: checklist verification loads user-site .pth (-E only) | autonomy/prd-checklist.sh (python3 sites incl. checklist-verify.py call and oracle heredoc, plus guarded helper copy), tests/test-prd-checklist-no-user-site-pth.sh (new) | HIGH | bash tests/test-prd-checklist-no-user-site-pth.sh exits 0 and reverting fails it; bash tests/moat/p2-honest-verdict.sh prints CASE P2.checklist-verify-not-shadowed PASS; bash tests/test-prd-checklist-interval-w4.sh exits 0 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-205 | Bun loki proof verify runs a PATH python3 -E (user-site .pth reaches the verdict) | loki-ts/src/commands/proof.ts (verifier spawn only), loki-ts/src/util/python.ts (extend existing helper only if used), loki-ts/tests/commands/proof_verify_interpreter.test.ts (new) | HIGH | cd loki-ts && bun test tests/commands/proof_verify_interpreter.test.ts tests/commands/proof_verify_parity.test.ts exits 0; reverting to python3 -E fails the new test; no resolvable interpreter exits 2 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-206 | BACKLOG 114: cockpit actions say working tree is clean and no run in progress after a failed fetch | web-app/src/cockpit/FinalActions.tsx (disabled reasons only), web-app/src/cockpit/FinalActions.reasons.test.mjs (new) | LOW | node --test web-app/src/cockpit/FinalActions.reasons.test.mjs passes: git null lacks The working tree is clean and Nothing to push, status null lacks No run in progress, real data keeps both; cd web-app && npx tsc -b exits 0 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-207 | BACKLOG 114: cockpit evidence says No gate results recorded when the checklist request failed | web-app/src/cockpit/useCockpitState.ts (getChecklist via settle only), web-app/src/cockpit/EvidencePanel.tsx (empty branch only), web-app/src/cockpit/ExecutionCockpit.tsx (EvidencePanel props only), web-app/src/cockpit/EvidencePanel.state.test.mjs (new) | LOW | node --test web-app/src/cockpit/EvidencePanel.state.test.mjs passes: an error renders Could not load gate results, items [] keeps No gate results recorded; node web-app/src/cockpit/run-derive-view-test.mjs exits 0; cd web-app && npx tsc -b exits 0 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-208 | BACKLOG 118: trust trajectory reads any non-pass council verdict as a failure | autonomy/lib/trust_trajectory.py (_verdict_is_pass only), tests/test_trust_trajectory_unknown_verdict.py (new) | MEDIUM | python3 -m pytest -q tests/test_trust_trajectory_unknown_verdict.py tests/test_trust_trajectory.py tests/dashboard/test_trust_trajectory_endpoint.py passes: an unknown verdict adds no data point, REJECTED stays 0.0; reverting fails case 1 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-209 | BACKLOG 99 (Bun): codex, cline and aider get the prompt without the commit-hygiene line | loki-ts/src/runner/providers.ts (codex, cline, aider invokers only), loki-ts/tests/runner/provider_commit_hygiene.test.ts (new), loki-ts/tests/runner/providers.test.ts (argv asserts only if moved) | MEDIUM | cd loki-ts && bun test tests/runner/provider_commit_hygiene.test.ts tests/runner/providers.test.ts exits 0: all three argvs carry the providers/codex.sh literal, claude not double-prefixed; removing the prefix fails the three legs | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-210 | Velocity: help-discoverability (29s) and completion-coverage (30s) probe loops under 10s each | tests/test-help-discoverability.sh, tests/test-completion-coverage.sh (probe loops only) | LOW | time bash tests/test-help-discoverability.sh and time bash tests/test-completion-coverage.sh each exit 0 with real under 10s; real_count and pass counts match the pre-change capture; both timings reported | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-211 | BACKLOG 75: register the four suites no runner executes (Captain, after S-174 merges) | tests/run-all-tests.sh (four run_test lines only, after S-174 merges), tests/shard-durations.tsv (four lines) | LOW | grep -c -e test_managed_completion_flag -e test_managed_review_flag -e test-evidence-gate-no-tests -e test-voter-agents-json tests/run-all-tests.sh prints 8; bash tests/test-shard-coverage.sh exits 0; each suite ran 3 of 3 from a scratch cwd with no .loki/state/provider left | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-212 | GUARDS 5, 12 and 13 still read PENDING after S-138, S-139 and S-154 landed (after S-181 merges) | docs/v10/GUARDS.md (sections 5, 12, 13 only; does not overlap S-181 section 11) | LOW | awk '/^## 12\./,0' docs/v10/GUARDS.md piped to grep -c 'PENDING, no slice cut' prints 0; bash tests/test-no-ambient-gitconfig-writes.sh and bash tests/test-v10-pulse.sh exit 0 | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
-| S-213 | BACKLOG 123: cost.html and proofs.html council-vote labels have no test of their own | dashboard-ui/tests/static-council-vote-label.node.test.mjs (new) | LOW | node --test dashboard-ui/tests/static-council-vote-label.node.test.mjs passes (proofs.html council prefix and title, cost.html Council vote header); renaming the header or dropping the title in a scratch copy fails it | ready@2026-09-27T20:12Z | Source: 20:12Z cut. |
+| S-214 | BACKLOG 147: P7 useMemo arm misses a factory that calls a registered fabricator | tests/moat/p7-no-fabricated-data.sh (HELPER_LOCAL_DECL_TMPL ~1182 and its use ~2186, ceiling comment ~978-986, one fixture beside the DECL_USEMEMO fixture ~3138-3160 only; does not overlap S-198) | HIGH | bash tests/moat/p7-no-fabricated-data.sh prints PASS for every P7 case and flags the composed useMemo fixture; removing the useMemo prefix in a scratch copy lets it through; git diff --stat tests/moat/cases.txt is empty | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-215 | PR receipt renderer in proof-pr.sh imports json from the target repo (cwd shadow) | autonomy/lib/proof-pr.sh (render_evidence_receipt_md heredoc reader plus guarded _loki_snapshot_py_tool copy), tests/test-proof-pr-no-cwd-shadow.sh (new) | HIGH | bash tests/test-proof-pr-no-cwd-shadow.sh exits 0 (a planted json.py cannot forge the headline) and reverting to bare python3 - in a scratch copy fails it; bash tests/test-proven-pr-receipt.sh exits 0; bash tests/test-council-py-tool-identity.sh exits 0 and counts one more copy | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-216 | loki verify inline readers import from the tree under review (cwd shadow) | autonomy/verify.sh (reader sites ~190, 591, 1269, 1271, 1295, 1337, 1339, 1441 plus guarded helper copy; not the unittest or py_compile runs), tests/test-verify-no-cwd-shadow.sh (new) | HIGH | bash tests/test-verify-no-cwd-shadow.sh exits 0 and reverting one site in a scratch copy fails it; bash tests/test-verify.sh exits 0; bash tests/moat/run.sh reports no rule failed; bash tests/test-council-py-tool-identity.sh exits 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-217 | BACKLOG 81: enforce_test_coverage package.json readers load user-site .pth | autonomy/run.sh (enforce_test_coverage _declared_test_script and _ws_script readers only; anchor on names), tests/test-enforce-test-coverage-pkg-readers-pth.sh (new) | HIGH | bash tests/test-enforce-test-coverage-pkg-readers-pth.sh exits 0 (a .pth no longer changes the recorded test gate outcome) and reverting one reader to -E in a scratch copy fails it; no .loki/state/provider left in the repo; bash tests/test-honest-gate-status.sh exits 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-218 | BACKLOG 131c: snapshot git status runs an agent-chosen core.fsmonitor command | autonomy/run.sh (_loki_untracked_status only), tests/test-untracked-status-fsmonitor.sh (new) | HIGH | bash tests/test-untracked-status-fsmonitor.sh exits 0 (no fsmonitor marker, real untracked file still listed) and removing the two -c flags in a scratch copy fails it; bash tests/test-no-ambient-gitconfig-writes.sh and bash tests/test-branch-lifecycle.sh exit 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-219 | BACKLOG 83: a failed git add -A makes the session commit silently commit nothing | autonomy/run.sh (commit_session_changes git add -A block only), tests/test-session-commit-add-failure.sh (new) | MEDIUM | bash tests/test-session-commit-add-failure.sh exits 0: an empty embedded repo prints Left uncommitted naming the add failure, a normal repo still commits; removing the rc check in a scratch copy fails leg 1; bash tests/test-branch-lifecycle.sh exits 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-220 | BACKLOG 109: untrack step's global reset drops force-staged agent files from the session commit | autonomy/run.sh (_loki_untrack_agent_committed_user_files only), tests/test-untrack-keeps-force-staged.sh (new) | MEDIUM | bash tests/test-untrack-keeps-force-staged.sh exits 0: git add -f dist/bundle.js lands in the session commit while the pre-existing user file stays untracked on disk; restoring git reset -q in a scratch copy fails it; bash tests/test-branch-lifecycle.sh exits 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-221 | BACKLOG 123: audit.py verify exits 0 when it checked nothing | dashboard/audit.py (_unified_cli verify branch and docstring only; tip and prefix untouched), tests/dashboard/test_audit_verify_cli_nothing_checked.py (new) | MEDIUM | python3 -m pytest -q tests/dashboard/test_audit_verify_cli_nothing_checked.py: empty dir exits 2, valid chain 0, tampered 1, tip on an empty dir still 0; bash tests/test-audit-chain-honesty.sh and bash tests/test-audit-js-suites.sh exit 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-222 | BACKLOG 118: skill-session WebSocket status push hardcodes running_agents 0 | dashboard/server.py (skill-session broadcast payload ~1030-1047 only), tests/dashboard/test_skill_session_ws_running_agents.py (new) | LOW | python3 -m pytest -q tests/dashboard/test_skill_session_ws_running_agents.py shows running_agents None on the skill-session push; restoring 0 fails it | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-223 | BACKLOG 114/118: notification triggers read No triggers configured after a failed read | dashboard/server.py (get_notification_triggers only), dashboard-ui/components/loki-notification-center.js (_loadTriggers and triggers empty branch only), tests/dashboard/test_notification_triggers_unreadable.py (new), dashboard-ui/tests/loki-notification-triggers-error.node.test.mjs (new) | LOW | python3 -m pytest -q tests/dashboard/test_notification_triggers_unreadable.py shows triggers null with error on a corrupt file and [] on a missing one; node --test dashboard-ui/tests/loki-notification-triggers-error.node.test.mjs shows an error lacks No triggers configured and an empty list keeps it | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-224 | BACKLOG 118: web-app receipt and cost trend show a partly priced run as a complete cost | web-app/src/components/EvidenceReceiptPanel.tsx (Cost field only), web-app/src/api/client.ts (ProofDetail cost type and cost/timeline runs type only), web-app/src/pages/MetricsPage.tsx (costTrend only), web-app/src/components/EvidenceReceiptPanel.cost.test.mjs (new) | MEDIUM | node --test web-app/src/components/EvidenceReceiptPanel.cost.test.mjs: cost_partial true renders at least $1.20, absent keeps $1.20, a partial run's trend label carries (partial); cd web-app && npx tsc -b exits 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-225 | BACKLOG 118: standalone receipts list shows a partly priced run as a complete cost | dashboard-ui/scripts/build-standalone.js (loadReceipts cost cell only), tests/test-receipts-panel.sh (one new leg) | LOW | bash tests/test-receipts-panel.sh exits 0 with the new leg asserting at least $X.XX only when cost_partial is true; bash tests/test-budget-banner-dedup.sh exits 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-226 | BACKLOG 106 class: loki stats reads unmeasured cost as $0.00 on both routes | autonomy/loki (cmd_stats only), loki-ts/src/commands/stats.ts, loki-ts/tests/commands/stats_unmeasured.test.ts (new), tests/test-stats-unmeasured-cost.sh (new) | MEDIUM | bash tests/test-stats-unmeasured-cost.sh exits 0 (all-zero records give cost_usd null and not recorded, same on both routes); cd loki-ts && bun test tests/commands/stats.test.ts tests/commands/stats_unmeasured.test.ts exits 0; bash tests/test-bash-bun-parity.sh exits 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-227 | BACKLOG 106 class: loki status prints Budget $0 for a run it never measured, on both routes | autonomy/loki (cmd_status budget block only), loki-ts/src/commands/status.ts (readBudgetField and its budget caller only), loki-ts/tests/commands/status.test.ts (budget legs only), tests/test-status-budget-unmeasured.sh (new) | MEDIUM | bash tests/test-status-budget-unmeasured.sh exits 0 (budget_used 0, null or absent prints not recorded on both routes, a positive value prints as today); cd loki-ts && bun test tests/commands/status.test.ts exits 0; bash tests/test-status-cli-provider-parity.sh exits 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-228 | BACKLOG 121: DeployConnections pushes default not-connected states upward after its own fetch failed | web-app/src/components/DeployConnections.tsx (connect and disconnect handlers only), web-app/src/components/DeployConnections.propagate.test.mjs (new) | LOW | node --test web-app/src/components/DeployConnections.propagate.test.mjs shows no synthesized statuses reach onStatusChange after a failed fetch; node --test web-app/src/components/DeployConnections.state.test.mjs and cd web-app && npx tsc -b exit 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-229 | BACKLOG 114: preview header says Detecting project type forever after a failed preview-info fetch | web-app/src/components/ProjectWorkspace.tsx (getPreviewInfo call ~839 and Detecting project type branch ~1877 only), web-app/src/components/ProjectWorkspace.preview.test.mjs (new) | LOW | node --test web-app/src/components/ProjectWorkspace.preview.test.mjs shows a rejected fetch renders Could not detect project type and lacks Detecting project type; node --test web-app/src/components/ProjectWorkspace.panels.test.mjs and cd web-app && npx tsc -b exit 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-230 | BACKLOG 115/118: ProjectWorkspace labels unknown phases building and Replay Build can never appear | web-app/src/components/ProjectWorkspace.tsx (buildPhase memo ~1401-1410 and Replay Build condition ~1488 only; does not overlap S-229), web-app/src/components/ProjectWorkspace.phase.test.mjs (new) | LOW | node --test web-app/src/components/ProjectWorkspace.phase.test.mjs shows an unrecognized phase is not building and a completed idle session shows Replay Build; cd web-app && npx tsc -b exits 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-231 | BACKLOG 52: the Moat suite CI check reads as moat proven at 0 of 9 | .github/workflows/test.yml (moat-suite job name only) | LOW | gh api required_status_checks for main does not list Moat suite (else report-only); git grep -n "name: Moat suite" -- .github prints nothing; git grep -n "Moat suite" -- tests scripts .github lists only the step-summary heading; the next push shows the renamed check | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-232 | autonomy/loki is linted only inside the sentrux test; the lint suite schedules big files last | tests/run-shellcheck.sh, tests/test-sentrux-init-rules.sh (T6 only) | LOW | LOKI_SHELLCHECK_JOBS=4 bash tests/run-shellcheck.sh exits 0, prints Checked ./autonomy/loki, counts match the pre-change capture plus loki; time bash tests/test-sentrux-init-rules.sh exits 0 with 8 passed under 10s; grep -c shellcheck tests/test-sentrux-init-rules.sh prints 0; both timings reported | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |
+| S-233 | BACKLOG 72 remainder: refused resume does not name the blocking file or where the earlier commits are | autonomy/run.sh (setup_agent_branch resume block around the no-overwrite-ignore checkout only), tests/test-refused-resume-warning.sh (new) | LOW | bash tests/test-refused-resume-warning.sh exits 0 with the warning naming the conflicting ignored file and the recorded branch; bash tests/test-branch-lifecycle.sh exits 0 | ready@2026-09-27T20:59Z | Source: 20:59Z cut. |