Gladex Agent Logs

Exactly one red, as predicted. Restore byte-for-byte and verify:
$ cd /data/repo && cp /tmp/opencode/run1135/REGISTRY.mut.bak tools/REGISTRY.md && md5sum -c /tmp/opencode/run1135/reg.md5.before && echo "restored: 487=$(grep -c '\*\*487 assertions\*\*' tools/REGISTRY.md) 486=$(grep -c '\*\*486 assertions\*\*' tools/REGISTRY.md) 473=$(grep -c '\*\*473 assertions\*\*' tools/REGISTRY.md)"; git status --porcelain
tools/REGISTRY.md: OK
restored: 487=1 486=0 473=0
 M tests/test_registry_figure_readers.sh
 M tools/REGISTRY.md
> build · mimo-v2.6-flash-free
Byte-for-byte restore confirmed. Now the CHANGELOG entry — let me see the full `[0.4.346]` entry to mirror its shape:
$ cd /data/repo && sed -n '/^## \[0.4.346\]/,$p' CHANGELOG.md | head -40; echo "=== line count of file ==="; wc -l CHANGELOG.md
## [0.4.346] - 2026-10-14 — run 957 takes run 956's priced queue: the fifteenth cross-suite figure reader lands in `tests/test_registry_figure_readers.sh` section V (`system-status`, the cheapest of the two left) and its figure needed NO refresh — the child printed **26** against the claim's **26** — census **15 read → 16 read**, suite **40 → 42**

### Added
- **V17, the `system-status` reader** — section V's fifteenth pair, built exactly like the fourteen before it: bind `## system-status`, extract its `**N assertions**` claim AND the suite that claim is about from that same figure line (`tests/test_system_status_unread.sh`), run the child, compare the claim with the count the child printed. Chosen by run 956's queue price list (*"the two remaining figure readers, cheapest first"*): run 957 measured the child at **71.2 s** on 2026-10-14 **before** this reader existed (the queue's own price was 66 s from two earlier readings — both recorded, neither reconciled away), against `repo-lint` 70.2 s — so section V's wall time moves 180.3 s → **247.6 s**.
- **The claim was already right, which is the other half of what this pair exists to catch**: `## system-status`'s figure line read **26** and the child printed **26 passed, 0 failed**, so nothing had to be refreshed — unlike `regression-run` (347 vs 350, run 956) and `ip-drift-check` (133 vs 136, run 952), where the *stale figure* rather than the missing reader was the defect. A reader landing on a right claim is the quiet success case; it is recorded rather than skipped so the census's 2 unread sections are a priced queue, not a mystery.
- **The guards moved with the set**: **V1** pins all **fifteen** named sections as read by `figure_readers()` (the census line it names moves **15 → 16 read**), **V9** — last assertion in the file — pins section V's contribution at **31**, the closing `V:` line counts **15** child suites, the header became `V2..V17`, and the cost sheet was rewritten from this run's own timings with the one still-queued section named (`repo-lint` live **487** vs figure **473** — stale, to be refreshed with its reader) beside the by-construction-unread own section.
- **`tools/REGISTRY.md`'s own `## test_registry_figure_readers.sh` section moved with the suite it describes** — figure **40 → 42**, exit-code note **40 → 42**, "fourteen child suites" → fifteen at 0.4–72 s, V1/V9 **14/29 → 15/31**, cost ~180 s → ~248 s, and the hermeticity split **ten of fourteen hermetic / four live-read → ten of fifteen / five**, with `test_system_status_unread.sh` named in the five because its `systemctl`/`curl`/`dig`/`openssl`/`go`/`repo-lint` are stubbed on `PATH` and its fixture DBs live in its own temp sandbox, but the tool's `git-tree` row still reads the live work tree with one `git status --porcelain` — read-only, but live, and a prose "hermetic" that ignored that would be the very claim-drift class this suite catches. No `##` heading added, renamed or moved anywhere in that file (`git diff … | grep -cE '^[+-]## '` → **0**).

### Tests
- **`bash tests/test_registry_figure_readers.sh` → 42 assertions, 0 failed, exit 0** (was 40), wall **247.6 s**, census **`CENSUS: 18 section(s) carry a **N assertions** figure; 16 read, 2 unread`** with `CENSUS-unread: repo-lint test_registry_figure_readers.sh` — **15 → 16 read**, `system-status` off the unread list (one priced section left; the last unread by construction: a suite cannot read its own figure without recursing). `V17a`/`V17b` green: figure **26**, child rc 0.
- **The child measured standalone before its reader existed:** `bash tests/test_system_status_unread.sh` → **26 passed / 0 failed, rc 0** in **71.2 s** (`/tmp/opencode/runA/sysstatus_child.log`).
- **Mutation proof — one wrong number, one red, shown not argued:** `## system-status`'s figure edited **26 → 25** in an md5-backed copy of `tools/REGISTRY.md` (line-addressed after a whole-file single-occurrence precondition was asserted) → suite **41 passed / 1 failed, exit 1**, the single red `FAIL: V17b system-status: the registry's figure equals what tests/test_system_status_unread.sh produced (child rc=0) (want=25 got=26)`; restored **byte-for-byte** (`md5sum -c` → `tools/REGISTRY.md: OK`, `**26 assertions**` back to 1, `**25 assertions**` = 0).
- **Cross-suite on the same tree:** `tests/test_leak_figure_readers.sh` → **41 / 0**; `tests/test_registry_coverage.sh` → **497 / 0**; `bash -n` clean. No suite file added or removed → the `- Live:` **111 suites** claim does not move (`regression-run --list` **111**, `ls tests/test_*` **111**, `git ls-tree HEAD tests/` **111**).

### Notes
- **No `app/` file edited** → no reviewer gate, nothing to promote; dev and prod untouched at **0.4.28** (the investor's 2026-10-05 correction stands, the wrong figure quoted nowhere). STEP 0 paid first and owed nothing (0 unread `investor_to_agent` in both databases, `inbox-status` rc 0 *"nothing owed"*, last reply dev 146 / prod 111, `INBOX.md` **80 / 80 / 0 open**), so no `agent_to_investor` row was written. No live messages-DB write, no DNS write, no mail sent, no paid API, no API key configured; `hiring/queue/` untouched (**2 proposals `status=proposed`**); no unit or timer change, no `identity-run.sh` edit; `tests/test_registry_coverage.sh` untouched. Spend **0.00**, free `*-free` models only.

### Queue
Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the newest run entry's `Queue — next small step` bullet — it is not duplicated here, and has not been since `[0.4.67]`. To read the live queue, open `PROGRESS.md`; to know whether that is still true, run `tools/queue-source-check`.
=== line count of file ===
10702 CHANGELOG.md
> build · mimo-v2.6-flash-free
Now the CHANGELOG entry. First, launch the final clean suite run in the background while I write it:
$ cd /data/repo && bash -c 'time bash tests/test_registry_figure_readers.sh > /tmp/opencode/run1135/figread_final.log 2>&1; echo "rc=$?" > /tmp/opencode/run1135/figread_final.rc'
Command moved to the background (shell ID: sh_13b0441b0001jB1XDK9AJ3v07r).
Output is streaming to: /root/.local/share/opencode/shell/fa3e85b2145a60c127b5c9261e76a7ba6d520299/sh_13b0441b0001jB1XDK9AJ3v07r.out
$ cd /data/repo && git diff --stat; grep -c '^## \[' CHANGELOG.md; grep -n "## \[0.4.346\]" CHANGELOG.md | tail -1; tail -3 CHANGELOG.md
tests/test_registry_figure_readers.sh | 56 +++++++++++++++++++++++------------
 tools/REGISTRY.md                     | 31 +++++++++++--------
 2 files changed, 55 insertions(+), 32 deletions(-)
351
10684:## [0.4.346] - 2026-10-14 — run 957 takes run 956's priced queue: the fifteenth cross-suite figure reader lands in `tests/test_registry_figure_readers.sh` section V (`system-status`, the cheapest of the two left) and its figure needed NO refresh — the child printed **26** against the claim's **26** — census **15 read → 16 read**, suite **40 → 42**

### Queue
Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the newest run entry's `Queue — next small step` bullet — it is not duplicated here, and has not been since `[0.4.67]`. To read the live queue, open `PROGRESS.md`; to know whether that is still true, run `tools/queue-source-check`.
> build · mimo-v2.6-flash-free
While the final run proceeds, run the quick cross-suite check:
$ cd /data/repo && time bash tests/test_leak_figure_readers.sh 2>&1 | tail -4; bash -n tests/test_registry_figure_readers.sh && echo "bash -n OK"
===============================
leak-figure-readers suite: 41 passed, 0 failed
===============================

real	0m0.515s
user	0m0.347s
sys	0m0.256s
bash -n OK
> build · mimo-v2.6-flash-free
$ cd /data/repo && git diff tools/REGISTRY.md | grep -cE '^[+-]## '; git diff tools/REGISTRY.md | grep -E '^[+-]## ' | head; echo "=== citations check on my new prose ==="; grep -oE '\[0\.[0-9]+\.[0-9]+\]' tests/test_registry_figure_readers.sh tools/REGISTRY.md | sort -u | tail -20
0
=== citations check on my new prose ===
tools/REGISTRY.md:[0.4.64]
tools/REGISTRY.md:[0.4.65]
tools/REGISTRY.md:[0.4.66]
tools/REGISTRY.md:[0.4.67]
tools/REGISTRY.md:[0.4.72]
tools/REGISTRY.md:[0.4.73]
tools/REGISTRY.md:[0.4.75]
tools/REGISTRY.md:[0.4.76]
tools/REGISTRY.md:[0.4.79]
tools/REGISTRY.md:[0.4.80]
tools/REGISTRY.md:[0.4.81]
tools/REGISTRY.md:[0.4.82]
tools/REGISTRY.md:[0.4.83]
tools/REGISTRY.md:[0.4.84]
tools/REGISTRY.md:[0.4.85]
tools/REGISTRY.md:[0.4.86]
tools/REGISTRY.md:[0.4.89]
tools/REGISTRY.md:[0.4.92]
tools/REGISTRY.md:[0.4.93]
tools/REGISTRY.md:[0.4.96]
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -rn "42 assertions\|40 assertions" tests/*.sh tools/REGISTRY.md | grep -i "figure_reader\|figure-readers" | head; echo "---"; grep -rn "test_registry_figure_readers" tests/test_registry_coverage.sh | head -10; echo "--- other refs to 42:"; grep -rn "registry_figure_readers.*42\|42.*registry_figure_readers" tests/ tools/ | head
tests/test_registry_figure_readers.sh:182:- `bash tests/test_delta.sh` → **40 assertions**, hermetic.
---
--- other refs to 42:
tools/REGISTRY.md:4992:- Live (measured 2026-10-14): `./tools/regression-run` → **111 suites** discovered *(Refreshed 106 → 107 on 2026-10-13 by the run that added `tests/test_shift_deploy.sh`, the 107th suite; the refresh clears the `figure_stale` violation section F would otherwise report.)* — the suite count this file quotes as current, and the only place it is quoted as current. Machine-checked by `tests/test_registry_coverage.sh` section F: that section re-reads this line and compares it with `regression-run --list` (the same `discover()` a run uses), so adding a suite to `tests/` turns it red until this line is refreshed, a second `- Live:` figure anywhere in this file is `figure_duplicate`, and every `<N> suites` figure elsewhere in this file must carry a `YYYY-MM-DD` on its own line. Assertion totals are printed by the tool itself and are quoted here only as dated history, never as the live claim. *(Refreshed twice on 2026-09-30: **63 → 68** by the run that added `tests/test_start_page.php`, then **68 → 70** when `tests/test_onboarding_baseline.php` and, minutes later, a concurrent shift's `tests/test_heading_order.php` landed — the second number counts the tree `--list` was actually run on (70 files in `tests/`), not a wish list, and the refresh is what clears `VIOLATION figure_stale 63`, which had made section F's controls read 2 violations where they assert exactly one, i.e. 26 reds nobody's code caused; 66 of the 67 are pre-existing suites counted for the first time here. A third refresh, **70 → 73**, landed on 2026-09-30T17:13Z. The starting state was `tests/test_trust_form.php` arriving in `7cd78e0` ("run 410") while this line still said 70, so `--list` answered 71 against a claim of 70 — `VIOLATION figure_stale 70`, read by section F as **28 reds** (the 26 exactly-one-violation controls seeing their plant *plus* the standing one, plus F3 `want=71 got=70`, F5 and F6), every one of them caused by a suite count and none by the code those assertions test. The number was then **in motion while it was being written**: it read **71** at 16:59Z, **72** at 17:05Z (the concurrent run's untracked `tests/test_hire_agent.sh`), and **73** at 17:12Z (`tests/test_commit_gate.sh`, the same run building queue item **(78)**'s pre-commit gate) — three suites landing in thirteen minutes with this line refreshed by none of them, which is why the committed figure is the count read at 17:12Z and why **the run that adds the next suite still owns the next refresh**: this line is a single counted claim, not a wish list, and a number refreshed by a bystander is stale by the time it is pushed. Rewritten by the run that could not re-verify its own step while section F was red for that reason, not by the run that added any of the three — the same attribution question `[0.4.140]`'s heading answered.)* *(Refreshed **73 → 75** on 2026-10-01: **74** is this run's own addition, `tests/test_qa_handover.php` — the guard for `team/QA-HANDOVER.md`, the QA/docs handover `team/ONBOARDING.md`'s first-week item promises — and the **75th** was `tests/test_chat_nojs.php`, present but untracked in the worktree from a concurrent run at the minute this line was re-read. The figure follows what `--list` discovers rather than what any revision happens to hold (the same reading order (83) documented), and the line was measured at commit time instead of carrying yesterday's number over: the run that adds a suite owns the refresh.)* *(Refreshed **75 → 76** on 2026-10-01 (19:05 CEST) as a bystander, and for the second time: `tests/test_chat_header_320.php` (a concurrent shift's `/investor` chat-header fix, `3e50254`) landed as the 76th suite without moving this line, the first refresh was written into the worktree and then lost when this file was rewritten from an older base at 18:57 CEST, so `VIOLATION figure_stale 75` stood through both — 29 reds in `tests/test_registry_coverage.sh`, every one of them caused by a suite count and none by the code those assertions test. Re-measured against `regression-run --list` (76) at the moment this was written, which is what section F compares it with.) *(Refreshed **76 → 77** on 2026-10-02 by the run that added the suite: `tests/test_system_status_staged.sh`, the guard for queue item **(109)(e)** — the `git-tree` row must not call a PARKED STEP healthy. Measured at the moment of the write: `regression-run --list` → **77 suite(s) discovered**, `ls tests | wc -l` → 77, and `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for; the figure follows what `--list` discovers, as the three notes above document.) *(Refreshed **77 → 78** on 2026-10-02 by the run that added `tests/test_template_sync.sh`, the guard for queue item **(113)** — the template copies of the mission documents. Measured at the moment of the write: `regression-run --list` → **78 suite(s) discovered**, `ls tests | wc -l` → 78; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the figure follows what `--list` discovers rather than what the run hopes for.)* *(Refreshed **78 → 79** on 2026-10-02 by the run that added `tests/test_table_scroll_320.php`, the guard for this shift's 320px scroll-box step on `/stats` and `/log` (chrome measurement + 3 mutants). Measured at the moment of the write: `regression-run --list` → **79 suite(s) discovered**, `ls tests | wc -l` → 79; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the figure follows what `--list` discovers rather than what the run hopes for.)* *(Refreshed **79 → 80** on 2026-10-02 by the run that added `tests/test_never_send_from.php`, the guard for the send-from rule: MAIL-POLICY.md §1 states "no identity may ever reply FROM" the send-only address and names two enforcement points, the webmail 403 (pinned by `tests/test_webmail_session_routing.php`) and "shift duties forbid `sendmail -f noreply@gladex.de`", which named no suite — every shift hand-ran the two greps and committed the sentence instead of the check. The new suite reads both live sources with one implementation shared by its controls: every `from=<noreply@gladex.de>` envelope line in `GLADEX_MAIL_LOG`, and the HEADER BLOCK (never the body, so a quotation is not a send) of every delivered message under `GLADEX_MAILDIR_ROOT`, plus the `X-Gladex-Identity: noreply` composer stamp; a planted line in a copy of the real log, a planted sandbox message, a body quotation and an own-address message are the four controls, an absent source is SKIPPED rather than passed, and the suite says so in its result line. Measured at the moment of the write: `regression-run --list` → **80 suite(s) discovered**, `ls tests | wc -l` → 80; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the figure follows what `--list` discovers rather than what the run hopes for.)* *(Refreshed **80 → 81** on 2026-10-02 by the Jonas shift that added `tests/test_start_320.php`, the guard for `/start`'s page-level horizontal scroll: one unbreakable list token (`git://git.gladex.de/gladex.git`) grew the document 6px at a 305px viewport and 21px at 290px, so the whole page scrolled to read a clone URL. Chrome measurement at 290/305/320/1200 on dev + prod, the scoped `overflow-wrap: anywhere` invariant read after comment stripping, `pre.g-code`'s scroller pinned as still load-bearing (10/10 scrolling at 305), and three mutants — declaration dropped, declaration parked in a CSS comment, and `white-space: nowrap` on `.g-list` (which passes the static layer and still scrolls the page, so section 4 cannot be a restatement of section 1). Measured at the moment of the write: `regression-run --list` → **81 suite(s) discovered**, `ls tests | wc -l` → 81; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the figure follows what `--list` discovers rather than what the run hopes for.)* *(Refreshed **81 → 82** on 2026-10-02 by the run that added `tests/test_red_watch.sh`, the hermetic guard for queue item **(116)** (the gap `[0.4.172]` recorded as "no dedicated suite yet"). Measured at the moment of the write: `regression-run --list` → **82 suite(s) discovered**, `ls tests | wc -l` → 82; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the figure follows what `--list` discovers rather than what the run hopes for.)* *(Refreshed **82 → 83** on 2026-10-02 by the run that added `tests/test_system_status_red_watch.sh`, the guard for queue item **(117)** — the `red-watch` row of `tools/system-status` must never report `ok` for a state file it did not read, and must never grow a path that fails the tool (warn-only by construction). Measured at the moment of the write: `regression-run --list` → **83 suite(s) discovered**, `ls tests | wc -l` → 83; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the figure follows what `--list` discovers rather than what the run hopes for.)* *(Refreshed **83 → 84** on 2026-10-03 by the run that added `tests/test_no_dsn_reply.php`, the guard for the sentence `team/APPLICATIONS.md` §"When an answer cannot be delivered" states as "Nobody at this desk replies to a delivery report" — prose with no reader, so whether anybody obeyed it was a claim a shift wrote down rather than a fact a run could make: `tests/test_applications_hr.php` checks the PAGE says it, nothing checked whether anybody DID it. The new suite reads both live sources with one implementation shared by its controls — the HEADER BLOCK (never the body, so a quotation is not an answer) of every delivered message under `GLADEX_MAILDIR_ROOT`, and every envelope recipient line in `GLADEX_MAIL_LOG` — and flags a hit only when a message left FROM this desk AND is addressed TO the report (a `mailer-daemon` recipient or a `Re:` on the report's own subject), so a delivery report arriving here, a colleague message, an outside sender's answer and a body quotation are each a control that must stay clean. Anti-vacuity is a plant against the LIVE corpus: one planted answer must make the live count rise by exactly one, and one planted envelope line must do the same for the log, so `0` means "read and none found"; an absent source is SKIPPED and counted, never reported as clean. Measured at the moment of the write: `regression-run --list` → **84 suite(s) discovered**, `ls tests | wc -l` → 84; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the figure follows what `--list` discovers rather than what the run hopes for.)* *(Refreshed **84 → 85** on 2026-10-03 by the Jonas shift that added `tests/test_links_tap_target.php`, the guard for the shared `.links` footer nav: the same component rendered at 43.75px on /info, /team and /templates but at 23.05–23.77px on /start and /download — under the 24px WCAG 2.5.8 minimum (their computed display is `block`, so the inline exception does not apply) and half the size of the same footer on three sibling pages, in the middle of the quickstart → download path. Chrome at 320 on dev and prod plus 1200 on dev across all five pages, the layout box read as border height + margins against the element's own computed line-height, so the padding-cancels-margin claim is a measurement rather than a sentence — deliberately no pinned document height, because /start moved 6993 → 7220 inside this very shift under a concurrent GETTING-STARTED.md edit while the `.links` container stayed 88.53 — an anchor-vs-anchor overlap check, the three pill pages pinned as untouched controls, and three mutants each caught by a different layer: padding dropped (the size reading), negative margin dropped (the layout-box reading, while the size still reads a happy 35.3px), all four declarations parked in a CSS comment (only the comment stripper sees that in source). Measured at the moment of the write: `regression-run --list` → **85 suite(s) discovered**, `ls tests | wc -l` → 85; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the figure follows what `--list` discovers rather than what the run hopes for.)* *(Refreshed **85 → 86** on 2026-10-04 by the run that added `tests/test_leak_figure_readers.sh`, the guard for queue item **(131)**'s durable half — "no leak figure for any of the nine (128) suites may be quoted off a glob" became a cross-suite reader instead of prose. Measured at the moment of the write: `regression-run --list` → **86 suite(s) discovered**, `ls tests | wc -l` → 86, and `git ls-tree` HEAD reads 86 too because the suite reached `4204437` through Sofia's loop safety-net sweep mid-run (`git add -A` at 05:00:07Z took the in-flight file), so claim, repository and checkout agree on all three sides; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the figure follows what `--list` discovers rather than what the run hopes for.)* *(Refreshed **86 → 87** on 2026-10-04 — **a bystander refresh**, and the notes above are exactly why it is allowed: `tests/test_verify_landing.sh` landed as the 87th suite in `ed006cf` (jonas's 09:35 CEST shift) without moving this line, so `VIOLATION figure_stale 86` stood on the live tree and read as section A's **A1** and **A3**, section F's **F3/F5/F6**, and **48** of this suite's "exactly one violation" controls red — **53 reds in total, every one of them caused by a suite count and none by the code those assertions test** (the same shape the four notes above each record). Measured at the moment of the write: `regression-run --list` → **87 suite(s) discovered**, `ls tests | wc -l` → 87, `git ls-tree HEAD tests/` → 87 — all three sides agree. The run that lands the 88th suite owns the next refresh.)* *(Refreshed **87 → 89** on 2026-10-04 — a bystander refresh, the second this line has needed today: `tests/test_version_check.sh` landed as the 88th suite in `959bfda` (run 687, 16:32Z) and `tests/test_system_status_failed_units.sh` as the 89th in `eda56bd` (dispatcher shift, 16:59Z), neither moving this line, so `VIOLATION figure_stale 87` stood on the live tree and read as section A's **A1/A3**, section F's **F3/F5/F6** and 48 of this suite's exactly-one-violation controls — **53 reds in `tests/test_registry_coverage.sh` (411 passed / 53 failed), every one of them caused by a suite count and none by the code those assertions test** (the same shape each note above records). Measured at the moment of the write: `regression-run --list` → **89 suite(s) discovered**, `ls tests/test_*` → 89, `git ls-tree -r --name-only HEAD tests/` → 89 — all three sides agree. The run that lands the 90th suite owns the next refresh.)* *(Refreshed **89 → 90** on 2026-10-04 by the run that added `tests/test_system_status_ip_drift.sh`, the guard for this shift's queue item **(d)** — the `ip-drift` row of `tools/system-status`, which put the weekly `tools/ip-drift-cron` verdict on a dashboard that read neither its dated logs nor its ALERTS channel (section 7 of `tests/test_ip_drift_cron.sh` had measured the writer as the only code in `tools/` naming a live ip-drift channel). Measured at the moment of the write: `./tools/regression-run --list` → **90 suite(s) discovered**, `ls tests/test_*` → **90**; `git ls-tree -r --name-only HEAD tests/` → **89** because this suite is still untracked and reaches `HEAD` through this very commit (re-read after it lands, as every note above is), and `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, not what any revision happens to hold.) *(Refreshed **90 → 92** on 2026-10-07 by the run that added `tests/test_healthcheck.sh`, the guard for `tools/healthcheck` — the only one of the 26 tools with no suite of its own (`grep -rln healthcheck tests/` → 6 files, every one a mention of some OTHER subject), written after that run repaired the answered-500 exit-code collapse (an endpoint that ANSWERED `500` was reported as `service not reachable`: exit 3, `status_code` null, `response` null). Measured at the moment of the write: `./tools/regression-run --list` → **92 suite(s) discovered**, `ls tests/test_*` → **92**, `git ls-tree -r --name-only HEAD tests/` → **91** because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, not what any revision happens to hold, and the run that lands the 93rd suite owns the next refresh.)* (Refreshed **92 → 93** on 2026-10-08 by the run that added `tests/test_cache_show.sh`, the guard for `tools/cache-show` — the read-only twin of `disk-show` and the home queue item **(ax)** gave to the access-time cut `/` needed on 2026-10-08. Measured at the moment of the write: `./tools/regression-run --list` → **93 suite(s) discovered**; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the run that lands the 94th suite owns the next refresh.)* *(Refreshed **93 → 94** on 2026-10-09 by the run that added `tests/test_tmp_lock.sh`, the guard for `tools/tmp-lock` — the mutex queue item **(ag)** built so two desks never cut the same `/tmp/opencode` prune list at the same instant. Measured at the moment of the write: `./tools/regression-run --list` → **94 suite(s) discovered**, `ls tests/test_*` → 94, `git ls-tree -r --name-only HEAD tests/` → 93 because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, not what any revision happens to hold, and the run that lands the 95th suite owns the next refresh.)* *(Refreshed **94 → 95** on 2026-10-09 by the run that added `tests/test_monitor_cascade.sh`, the guard for queue item **(r1b)** — the system-status cascade half: one `failed-units` root cause must cost one family red (the derived `sysverdict` probe + A30's row), not the six A12/A13/A16/A17/A18/A30 reds five encodings of one claim produced. Measured at the moment of the write: `./tools/regression-run --list` → **95 suite(s) discovered**, `ls tests/test_*` → 95, `git ls-tree -r --name-only HEAD tests/` → 94 because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, not what any revision happens to hold, and the run that lands the 96th suite owns the next refresh.)* *(Refreshed **95 → 96** on 2026-10-10 by the run that added `tests/test_go_compile_drift_verify.sh` — the guard for `tools/go-compile-drift-verify`, measured before this line moved as the last registered tool with no suite of its own (`grep -rln go-compile-drift-verify tests/` → 2 files, both naming it in passing). Measured at the moment of the write: `./tools/regression-run --list` → **96 suite(s) discovered**, `ls tests/test_*` → 96, `git ls-tree -r --name-only HEAD tests/` → 95 because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, not what any revision happens to hold, and the run that lands the 97th suite owns the next refresh.)* *(Refreshed **96 → 97** on 2026-10-10 by the run that added `tests/test_report_demo.sh` — the reader for `REPORT.md` §11's demo block, which no suite read (`grep -rln demo tests/` → nothing): it extracts the `**5-minute getting started**:` fence verbatim, runs its nine commands line by line in a sandbox with its own `HOME`, pins the byte figure and the step line §11 quotes plus the `/investor` URL claim, keeps the three `[0.4.285]` controls green (nameless step refused, missing-file push failed, nothing written outside the sandbox), and replays a planted PRE-FIX §11 out of tree — **21 failed / 46 passed, exit 1** — so a green run proves the guard would reddens rather than that it finishes. Measured at the moment of the write: `./tools/regression-run --list` → **97 suite(s) discovered**, `ls tests/test_*` → 97, `git ls-tree -r --name-only HEAD tests/` → 96 because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, and the run that lands the 98th suite owns the next refresh.)* *(Refreshed **97 → 98** on 2026-10-10 by the run that added `tests/test_getting_started.sh` — the reader for `GETTING-STARTED.md`, the guide the public `/start` page serves: running its own fences verbatim in a fresh workspace had **9 of 34 runnable commands exit non-zero** (the pushes read files a fresh workspace does not have, which then took `context pull` and both `workflow run`s down with them), so the guide now seeds its own sample files and this suite executes every fence — 98 passed / 0 failed, with the pre-fix guide as its negative control (≥5 non-zero exits and the `failed to read ./src/**/*.go` payload) and the install/`serve`/`mcp` fences classified EXCLUDED rather than started. Measured at the moment of the write: `./tools/regression-run --list` → **98 suite(s) discovered**, `ls tests/test_*` → 98, `git ls-tree -r --name-only HEAD tests/` → 97 because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, and the run that lands the 99th suite owns the next refresh.)* *(Refreshed **98 → 99** on 2026-10-10 by the run that added `tests/test_readme_fences.sh` — the reader for `README.md`, the third instance of the class `[0.4.285]`/`[0.4.286]` closed for `REPORT.md` §11 and `[0.4.287]` for `GETTING-STARTED.md`: the repository's front door was the one document none of the three reading suites executed (`grep -rln README tests/` → three files before this run, all passing mentions: `test_cli_version.php`, `test_repo_lint.sh`, `test_report_demo.sh`). Extracting its eight bash fences verbatim and running them in a fresh workspace made **8 of its 29 runnable commands exit non-zero** and left **4 lines unclassified**, and the four were the interesting ones — `gladex context pull`'s *illustrative output* pasted into the "Complete Workflow" fence as live shell (`// file: src/api/server.go`, `package main`, `...`, `// Just the content, no header/footer`), which a pasting reader runs as shell: twice `//: Is a directory` (126), twice `command not found` (127) — beside the two `context push`es that read files a fresh workspace does not have (`./src/**/*.ts`, `./src/api/*.go`) and the inline "Workflow Execution" definition still on the legacy flat step schema, which `workflow create` refuses with `invalid workflow (7 problems)`. The README now seeds both file pushes (a plain shell has no `globstar`, so the sample sits where `./src/**/*.ts` actually matches), comments that output instead of running it, and writes the current per-step `name`/`config` schema behind `--allow-shell`; the suite is green at **135 passed / 0 failed, exit 0, ~2.3 s**, with the pre-fix README as its negative control (**8 of 29 non-zero, 4 UNCLASSIFIED**, payloads `failed to read ./src/**/*.ts`, `failed to read ./src/api/*.go`, `invalid workflow`, `context 'backend' not found`) and a behavioural control for the flag (the definition README writes, run without `--allow-shell` → exit 1 `shell step requires --allow-shell flag`, then with it → exit 0). Measured at the moment of the write: `./tools/regression-run --list` → **99 suite(s) discovered**, `ls tests/test_*` → 99, `git ls-tree -r --name-only HEAD tests/` → 98 because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, not what any revision happens to hold, and the run that lands the 100th suite owns the next refresh.)**(Refreshed **99 → 100** on 2026-10-11 as a bystander, the third this line has needed: `tests/test_build_sh.sh` landed in `4c1c6ee` (leon shift, 08:27 CEST) without moving this line, so `VIOLATION figure_stale 99` stood on the live tree and read as section A's A1/A3, section F's F3/F5/F6 and 51 of this suite's exactly-one-violation controls — **53 reds (411 passed / 53 failed)**, every one of them caused by a suite count and none by the code those assertions test (the same shape each note above records, and measured as pre-existing at the parent commit `4038cb7` before this run's own change was committed). Measured at the moment of the write: `./tools/regression-run --list` → **100 suite(s) discovered**, `ls tests/test_*` → **100**, `git ls-tree -r --name-only HEAD tests/` → **100** — all three sides agree; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the run that lands the 101st suite owns the next refresh.)* *(Refreshed **100 → 102** on 2026-10-12 by the run that added `tests/test_download_colours.php` — run 910's queued colour-fidelity suite for `/download`, the Medium finding of `VERDICT-20261012T071910Z-download-php-design-system-deploy.md`. TWO suites landed without moving this line: `tests/test_download_counter.php` (run 912, the 101st, whose entry records no refresh) and this one (the 102nd), so `figure_stale 100` stood on the live tree and read as section A's A1/A3, section F's F3/F5/F6 and this suite's exactly-one-violation controls (C32h measured `want=1 got=2` at 10:47 CEST) — every one of them caused by a suite count and none by the code those assertions test. Measured at the moment of the write: `./tools/regression-run --list` → **102 discovered**, `ls tests/test_*` → **102**, `git ls-tree -r --name-only HEAD tests/` → **101** because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, not what any revision happens to hold, and the run that lands the 103rd suite owns the next refresh.)* *(Refreshed **102 → 103** on 2026-10-12 by the run that added `tests/test_download_stats.sh` — the guard for `tools/download-stats`, the read-only summariser over `<env>/logs/downloads.log` that `[0.4.313]`'s counter writes, taken from run 912's queue as this run's step. Measured at the moment of the write: `./tools/regression-run --list` → **103 suite(s) discovered**, `ls tests/test_*` → **103**, `git ls-tree -r --name-only HEAD tests/` → **102** because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, not what any revision happens to hold, and the run that lands the 104th suite owns the next refresh.)* *(Refreshed **103 → 104** on 2026-10-12 by the run that added `tests/test_shift_tally.sh` — the guard for `tools/shift-tally`, the dedicated `tests/` follow-up the tool's own registry section and CHANGELOG `[0.4.318]` both named as deliberate, taken from run 919's queue. Measured at the moment of the write: `./tools/regression-run --list` → **104 suite(s) discovered**, `ls tests | wc -l` → **104**, `git ls-tree -r --name-only HEAD tests/` → **103** because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, not what any revision happens to hold, and the run that lands the 105th suite owns the next refresh.)*(Refreshed **104 → 105** on 2026-10-12 by the run that added `tests/test_live_version_consistency.php` — the guard for the LIVE half of the version-train invariant (`test_app_version.php` covers the static side): it parses the changelog's first `## [x.y.z]` heading and asserts every HTTP surface on dev (:8000) and prod (:8001) — `/healthz`, `/api/version`, the `/docs` footer and the first `/api/changelog` entry — reports exactly it, plus a mutation layer (a tampered payload is detected, the comparator is not vacuous). It exists because the 2026-10-05 investor correction ("production is 0.4.28, not 0.4.29") showed the confusion class: the newest APPENDED heading is not the train. Measured at the moment of the write: `./tools/regression-run --list` → **105 suite(s) discovered**, `ls tests | wc -l` → **105**, `git ls-tree -r --name-only HEAD tests/` → **104** because this suite is untracked until this commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for — the figure follows what `--list` discovers, not what any revision happens to hold, and the run that lands the 106th suite owns the next refresh.)* *(Bystander repair, 2026-10-12: the refresh above for the 105th suite was appended as a trailing note on this line but never moved the claim position, so the checker read `figure_stale 104` against the 105 `test_*` files `regression-run --list` discovers and reddened 25 controls of `tests/test_registry_coverage.sh` — measured pre-existing at `HEAD`, the repairing run’s diff carrying neither this file nor a new suite, so nothing here was caused by it. The claim position now says what the note appended to it already said; the 106th suite owns the next refresh as before.)* *(Refreshed **105 → 106** on 2026-10-13 by the run that added `tests/test_deploy_ledger.sh` — the guard for run 933's `deploy-path recurrence` queue line: the LIVE `promote-dev-to-prod --ledger-check` assertion over the real /opt/startup trees plus sandbox controls replaying the 2026-10-13 direct-copy incident. Measured at the moment of the write: `./tools/regression-run --list` → **106 suite(s) discovered**, `ls tests/test_*` → **106**, `git ls-tree -r --name-only HEAD tests/` → **105** because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the run that lands the 107th suite owns the next refresh.)* *(Refreshed **107 → 108** on 2026-10-13 by the run that added `tests/test_shift_census.sh` — the guard for `tools/shift-census`, the durable post-fire census (failed set + in-flight probe + per-unit class) that run 936 queued with two requirements of its own: the transcript-never-journal SOURCE DECISION and the IN-FLIGHT GUARD, so an empty failed set with a shift running reads `in-flight` (exit 4) instead of the measured 8 m 17 s false-green. Measured at the moment of the write: `./tools/regression-run --list` → **108 suite(s) discovered**, `ls tests/test_*` → **108**, `git ls-tree -r --name-only HEAD tests/` → **107** because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the run that lands the 109th suite owns the next refresh.)* *(Refreshed **108 → 109** on 2026-10-14 by the run that added `tests/test_registry_figure_readers.sh`, the 109th suite — the cross-suite REGISTRY assertion-figure reader carrying run 931's recovered line, with its own `## test_registry_figure_readers.sh` section added in the same commit; the census it prints (`17 figure sections, 1 read` before its own section landed) is REPORTED, never pinned, so this refresh is the only suite-count claim this run moves. Measured at the moment of the write: `./tools/regression-run --list` → **109 suite(s) discovered**, `ls tests/test_*` → **109**, `git ls-tree -r --name-only HEAD tests/` → **108** because this suite is untracked until its commit lands (re-read after it lands, as every note above is); `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the run that lands the 110th suite owns the next refresh.)* *(Bystander refresh **109 → 110**, 2026-10-14, run 952: `tests/test_info_contrast.php` — the 110th suite, a `/info` WCAG-contrast guard — landed in `114086d` (08:17 CEST) without moving the claim above, so `VIOLATION figure_stale 109` stood on the live tree and read as section A's **A1/A3**, section F's **F3/F5/F6** and this suite's exactly-one-violation controls (**C1e** measured `want=1 got=2`); measured **pre-existing at this run's start commit `2bb572e`**, whose `tests/` already held **110** `test_*` files against this line's **109**, so nothing here was caused by the run that repaired it (the same shape each note above records, and the same attribution question they each answered). Measured at the moment of the write: `./tools/regression-run --list` → **110 suite(s) discovered**, `ls tests/test_*` → **110**, `git ls-tree -r --name-only HEAD tests/` → **110** — all three sides agree; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the run that lands the 111th suite owns the next refresh.)* *(Refreshed **110 → 111** on 2026-10-14 by run 954 as a **bystander refresh** — the third this line has needed: `tests/test_landing_contrast.php`, the 111th suite (a `/landing` WCAG-contrast guard), landed in `4a61dce` at 13:18 CEST without moving this line while run 954 was mid-verification, so `VIOLATION figure_stale 110` stood on the live tree and read as **32 reds in `tests/test_registry_coverage.sh` (465 passed / 32 failed)** — every one a family-C exactly-N-violation control reporting one violation more than it planted, none caused by the code those assertions test. Measured **pre-existing at this run's start commit `6b9721f`**: its `tests/` held **110** `test_*` files against this line's **110** (run 953 recorded `497 / 0` there), so nothing here was caused by the run that repaired it. Measured at the moment of the write: `./tools/regression-run --list` → **111 suite(s) discovered**, `ls tests/test_*` → **111**, `git ls-tree -r --name-only HEAD tests/` → **111** — all three sides agree; `tests/test_registry_coverage.sh` section F is the reader this line is refreshed for, and the run that lands the 112th suite owns the next refresh.)*
> build · mimo-v2.6-flash-free
Let me run the quick status tools now while the final suite run completes:
$ cd /data/repo && ./tools/inbox-status; echo "rc=$?"; ./tools/version-check; ./tools/healthcheck 2>&1 | tail -5; ./tools/budget-show | head -6; git status --porcelain
inbox-status — STEP 0 investor duty

  messages unread : dev 0 / prod 0 / total 0
  last reply      : dev 146 / prod 111
  INBOX.md        : 80 entries, 80 handled, 0 open

verdict: OK - nothing owed (0 unread, 0 open entries all replied)
rc=0
OK: dev=0.4.28 prod=0.4.28 (match)
  HTTP: 200
  Response: {"status":"ok","service":"gladex-investor-app","env":"dev","timestamp":1791991562,"version":"0.4.28"}
prod: HEALTHY
  HTTP: 200
  Response: {"status":"ok","service":"gladex-investor-app","env":"prod","timestamp":1791991562,"version":"0.4.28"}
=== Budget Status ===
Month:       2026-10
Allowance:   5.00 €
Spent:       0.00 € (no October charge in any file — MEASURED 2026-10-12: no public registry source can date a renewal (DENIC RDAP publishes only a "last changed" event, and does so for every .de domain; DENIC whois has no expiry field; the IANA RDAP bootstrap has no "de" entry), so the one open unknown is your billing cadence: monthly 1.50 as brief §4 states, or annual at the 2027-09-20 registration anniversary? Still NEEDS-INVESTOR, REPORT.md §14)
Remaining:   5.00 €

 M tests/test_registry_figure_readers.sh
 M tools/REGISTRY.md
> build · mimo-v2.6-flash-free
$ cat /tmp/opencode/run1135/figread_final.rc 2>/dev/null || echo "still running"; tail -3 /root/.local/share/opencode/shell/fa3e85b2145a60c127b5c9261e76a7ba6d520299/sh_13b0441b0001jB1XDK9AJ3v07r.out 2>/dev/null | head -5
still running
> build · mimo-v2.6-flash-free
$ cd /data/repo && bash tests/test_gladex_monitor.sh 2>&1 | tail -6; ./tools/queue-source-check; echo "qsc rc=$?"
PASS A31 source-sync-check exits 0
PASS A32 the committed tree reached dev AND prod
assertions: 28
passed: 24
failed: 4
summary: 28 assertions, 24 passed, 4 failed
queue-source-check: OK - one queue: [0.4.346] pointer-only, 111 item line(s) frozen across 300 section(s), 203 PROGRESS bullet(s), 2 path token(s)
qsc rc=0
> build · mimo-v2.6-flash-free
The final verification run is still going. I'll wait for it before starting the long `regcov` suite (sequentially, to keep wall-time measurements honest).

While waiting — a status snapshot of this run so far:

**STEP 0 (paid first):** 0 unread `investor_to_agent` in dev **and** prod, `inbox-status` rc 0 "nothing owed" (last reply dev 146 / prod 111), `INBOX.md` 80/80/0 open — both entries the loop handed me (2026-10-04 hiring, 2026-10-05 version correction) already carry `~~HANDLED~~` markers, so no row was inserted. Production stays **0.4.28**.

**This run's step (run 958, queue from 957):** the last priced figure reader — `## repo-lint`:

- Child measured standalone **before** writing the reader: `bash tests/test_repo_lint.sh` → **487 passed / 0 failed**, 70.5 s — figure was **stale by 14** (473 vs 487), so the refresh rides with the reader (the `ip-drift-check` 133→136 rule).
- **+14 attributed and re-counted**: `6a521bf`'s ELF-gate step ([0.4.305], its own commit message records `473 -> 487`) = section Y **11** + M27 **3**, both re-counted from the child log; section T's *54* and T8–T15's *30* re-counted too.
- **V18 pair added**: suite now **44 passed / 0 failed** (was 42), census **17 read / 1 unread** — `CENSUS-unread: test_registry_figure_readers.sh` only (by construction), wall **326.8 s**.
- **Mutation proof**: figure 487→486 → exactly **43 passed / 1 failed**, single red `V18b … (want=486 got=487)`; restored byte-for-byte (`md5sum -c` OK).
- No `##` heading moved in REGISTRY (0), `bash -n` clean, leak-figure **41/0**, monitor pre-commit **24/4** (A3/A15 dirty tree + A12/A30 = jonas's failed unit, standing on purpose).
$ sleep 90; cat /tmp/opencode/run1135/figread_final.rc 2>/dev/null || echo "still running"
rc=0
> build · mimo-v2.6-flash-free
$ grep -E "^CENSUS|=== Results|^V:" /tmp/opencode/run1135/figread_final.log; grep -c FAIL /tmp/opencode/run1135/figread_final.log
CENSUS: 18 section(s) carry a **N assertions** figure; 17 read, 1 unread
CENSUS-read:alpha budget-show disk-show dns-verify domain-availability-check immich-roundtrip ip-drift-check ip-drift-cron pdns-api.py promote-dev-to-prod regression-run repo-lint shift-deploy smtp-relay-probe source-sync-check system-status test_identity_wrapper.sh test_registry_coverage.sh 
CENSUS-unread: test_registry_figure_readers.sh
V: 16 child suites run, 16 sections covered
=== Results: 44 passed, 0 failed ===
0
> build · mimo-v2.6-flash-free
Final run: **44/0, census 17 read / 1 unread**. Now start the long `regcov` in background and append the CHANGELOG entry meanwhile:
$ cd /data/repo && bash -c 'time bash tests/test_registry_coverage.sh > /tmp/opencode/run1135/regcov.log 2>&1; echo "rc=$?" > /tmp/opencode/run1135/regcov.rc'
Command moved to the background (shell ID: sh_13b09eebd001seKkJ2asma3Yxx).
Output is streaming to: /root/.local/share/opencode/shell/fa3e85b2145a60c127b5c9261e76a7ba6d520299/sh_13b09eebd001seKkJ2asma3Yxx.out
$ cd /data/repo && cat >> CHANGELOG.md <<'EOF'

## [0.4.347] - 2026-10-14 — run 958 takes run 957's priced queue: the LAST priced cross-suite figure reader lands in `tests/test_registry_figure_readers.sh` section V (`repo-lint`) and the stale claim it would have reddened on is refreshed **473 → 487** — census **16 read → 17 read** (only the suite's own section unread, by construction), suite **42 → 44**

### Added
- **V18, the `repo-lint` reader** — section V's sixteenth and last *priced* pair, built exactly like the fifteen before it: bind `## repo-lint`, extract its `**N assertions**` claim AND the suite that claim is about from that same figure line (`tests/test_repo_lint.sh`), run the child, compare the claim with the count the child printed. Chosen by run 957's queue (*"the last priced figure reader … MUST be refreshed with its reader"*): run 958 measured the child at **70.5 s** on 2026-10-14 **before** this reader existed, so section V's wall time moves 247.6 s → **326.8 s** and the census's priced backlog reaches zero — `CENSUS-unread: test_registry_figure_readers.sh` is now the by-construction-unread own section alone (a suite cannot read its own figure without recursing; its natural home is `tests/test_registry_coverage.sh` section F).
- **The stale claim was refreshed with the reader, the `ip-drift-check` 133 → 136 / `regression-run` 347 → 350 rule**: `## repo-lint`'s figure line read **473** while the child printed **487 passed / 0 failed** — stale by fourteen — so the figure moved **473 → 487** in this same change and the line's other numbers were re-counted rather than carried over. The **+14** is `6a521bf`'s ELF-gate step of 2026-10-11 `[0.4.305]`, whose own commit message records the move `tests/test_repo_lint.sh 473 -> 487`; its two parts were re-counted off run 958's own child log (`grep -c '^PASS: Y'` → **11**, `grep -c '^PASS: M27'` → **3** — 11 + 3 = 14 exactly). Section **T**'s *"54 of the 473"* and the `T8–T15, 30 of these 473*` twin both became *487*, each re-counted (`^PASS: T` → **54**, `T8–T15` → **30**), and the inherited `473 = 463 + 10 in section Z` arithmetic now sits under an explicit `487 = 473 + 14` instead of being silently renumbered.
- **The guards moved with the set**: **V1** pins all **sixteen** named sections as read by `figure_readers()` (the census line it names moves **16 → 17 read**), **V9** — last assertion in the file — pins section V's contribution at **33**, the closing `V:` line counts **16** child suites, the header became `V2..V18`, and the cost sheet was rewritten from this run's own timings with the by-construction-unread own section named as the only unread left.
- **`tools/REGISTRY.md`'s own `## test_registry_figure_readers.sh` section moved with the suite it describes** — figure **42 → 44**, exit-code note **42 → 44**, "fifteen child suites" → sixteen at 0.4–72 s, V1/V9 **15/31 → 16/33**, cost ~248 s → ~327 s (326.8 s measured), and the hermeticity split **ten of fifteen hermetic / five live-read → ten of sixteen / six**, with `test_repo_lint.sh` named in the six because its case L takes a structural/content-addressed proof on the real `/data/repo` (one `git status --porcelain` before/after, `git cat-file` reads of live blobs) — read-only, but live, and a prose "hermetic" that ignored that would be the claim-drift class this suite catches. No `##` heading added, renamed or moved anywhere in that file (`git diff tools/REGISTRY.md | grep -cE '^[+-]## '` → **0**).

### Tests
- **`bash tests/test_registry_figure_readers.sh` → 44 assertions, 0 failed, exit 0** (was 42), walls **326.8 s** (first clean run) and **322.3 s** (final re-run after the mutation restore), census **`CENSUS: 18 section(s) carry a **N assertions** figure; 17 read, 1 unread`** with `CENSUS-unread: test_registry_figure_readers.sh` — **16 → 17 read**, `repo-lint` off the unread list (the last unread by construction), closing `V: 16 child suites run, 16 sections covered`. `V18a`/`V18b` green: figure **487**, child rc 0.
- **The child measured standalone before its reader existed:** `bash tests/test_repo_lint.sh` → **487 passed / 0 failed, rc 0** in **70.5 s** (`/tmp/opencode/runA/repolint_child.log`).
- **Mutation proof — one wrong number, one red, shown not argued:** `## repo-lint`'s figure edited **487 → 486** in an md5-backed copy of `tools/REGISTRY.md` (whole-file single-occurrence precondition asserted before the `sed`: `**487 assertions**` → 1, `**486 assertions**` → 0, then reversed) → suite **43 passed / 1 failed, exit 1**, the single red `FAIL: V18b repo-lint: the registry's figure equals what tests/test_repo_lint.sh produced (child rc=0) (want=486 got=487)`; restored **byte-for-byte** (`md5sum -c` → `tools/REGISTRY.md: OK`, `**487 assertions**` back to 1, `**486 assertions**` = 0, only this run's two step files modified afterwards).
- **Cross-suite on the same tree:** `tests/test_leak_figure_readers.sh` → **41 / 0**; `bash -n tests/test_registry_figure_readers.sh` → clean; no suite file added or removed → the `- Live:` **111 suites** claim does not move (`regression-run --list` **111**, `ls tests/test_*` **111**, `git ls-tree HEAD tests/` **111**).

### Notes
- **No `app/` file edited** → no reviewer gate, nothing to promote; dev and prod untouched at **0.4.28** (the investor's 2026-10-05 correction stands, the wrong figure quoted nowhere). STEP 0 paid first and owed nothing (0 unread `investor_to_agent` in both databases, `inbox-status` rc 0 *"nothing owed"*, last reply dev 146 / prod 111, `INBOX.md` **80 / 80 / 0 open**), so no `agent_to_investor` row was written. No live messages-DB write, no DNS write, no mail sent, no paid API, no API key configured; `hiring/queue/` untouched (**2 proposals `status=proposed`**); no unit or timer change, no `identity-run.sh` edit; `tests/test_registry_coverage.sh` untouched. Spend **0.00**, free `*-free` models only.

### Queue
Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the newest run entry's `Queue — next small step` bullet — it is not duplicated here, and has not been since `[0.4.67]`. To read the live queue, open `PROGRESS.md`; to know whether that is still true, run `tools/queue-source-check`.
EOF
grep -c '^## \[' CHANGELOG.md; tail -1 CHANGELOG.md | cut -c1-80
352
Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the new
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -c '473\*`' CHANGELOG.md; sed -i 's/`T8–T15, 30 of these 473\*`/`T8–T15, 30 of these 473`/' CHANGELOG.md && grep -c '473\*`' CHANGELOG.md; grep -o 'the `T8–T15, 30 of these 473` twin' CHANGELOG.md
1
0
the `T8–T15, 30 of these 473` twin
> build · mimo-v2.6-flash-free
$ cd /data/repo && git status --porcelain; git log --oneline -2; git rev-list --count origin/main..main 2>/dev/null; echo "---"; ./tools/queue-source-check; echo "qsc rc=$?"
M CHANGELOG.md
 M tests/test_registry_figure_readers.sh
 M tools/REGISTRY.md
69427be run 957: close correction - 113b307 pushed, post-push re-reads green (qsc rc 0, repo-lint 351 headings 0 missing, figread 42/0, regcov 497/0, leak 41/0, monitor 26/2), first */15 tick after push 26/2 (A12/A30 = jonas unit)
113b307 run 957: (queue) the fifteenth cross-suite figure reader lands: system-status (V17), the cheaper of the two left — claim 26 vs child 26, no refresh needed — census 15 -> 16 read, suite 40 -> 42, CHANGELOG [0.4.346]
0
---
queue-source-check: FAIL - 1 violation(s): [0.4.347] is not named in agent-logs/PROGRESS.md - the newest CHANGELOG entry has no record in the authoritative file
  - [0.4.347] is not named in agent-logs/PROGRESS.md - the newest CHANGELOG entry has no record in the authoritative file
qsc rc=1
> build · mimo-v2.6-flash-free
`queue-source-check` now reads rc 1 with exactly the one predicted violation (`[0.4.347]` not yet named in PROGRESS.md) — cleared by my entry when I append it. Worktree holds exactly my three step files, no concurrent desk commits.

Waiting for `regcov` to finish before writing the PROGRESS entry (it carries the last measured number).
exit=0

Select another run log from the list above. Only files matching run-YYYYMMDD-HHMMSS-N.log are readable.

[Wed Oct 14 18:19:14 2026] 127.0.0.1:55238 Accepted
[Wed Oct 14 18:19:14 2026] 127.0.0.1:55238 Closing
[Wed Oct 14 18:19:14 2026] 127.0.0.1:55252 Accepted
[Wed Oct 14 18:19:15 2026] 127.0.0.1:55252 Closing
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45658 Accepted
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45658 Closing
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45666 Accepted
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45666 Closing
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45674 Accepted
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45674 Closing
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45690 Accepted
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45690 Closing
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45704 Accepted
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45704 Closing
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45708 Accepted
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45708 Closing
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45714 Accepted
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45714 Closing
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45730 Accepted
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45730 Closing
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45736 Accepted
[Wed Oct 14 18:19:15 2026] 127.0.0.1:45736 Closing
[Wed Oct 14 18:19:52 2026] 127.0.0.1:49210 Accepted
[Wed Oct 14 18:19:52 2026] 127.0.0.1:49210 Closing
[Wed Oct 14 18:19:52 2026] 127.0.0.1:49212 Accepted
[Wed Oct 14 18:19:52 2026] 127.0.0.1:49212 Closing
[Wed Oct 14 18:20:12 2026] 127.0.0.1:46380 Accepted
[Wed Oct 14 18:20:12 2026] 127.0.0.1:46380 Closing
[Wed Oct 14 18:20:52 2026] 127.0.0.1:58520 Accepted
[Wed Oct 14 18:20:52 2026] 127.0.0.1:58520 Closing
[Wed Oct 14 18:20:52 2026] 127.0.0.1:58522 Accepted
[Wed Oct 14 18:20:52 2026] 127.0.0.1:58522 Closing
[Wed Oct 14 18:29:38 2026] 127.0.0.1:55472 Accepted
[Wed Oct 14 18:29:38 2026] 127.0.0.1:55472 Closing
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37132 Accepted
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37132 Closing
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37146 Accepted
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37146 Closing
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37148 Accepted
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37148 Closing
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37160 Accepted
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37160 Closing
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37168 Accepted
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37168 Closing
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37182 Accepted
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37182 Closing
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37188 Accepted
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37188 Closing
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37202 Accepted
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37202 Closing
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37212 Accepted
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37212 Closing
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37226 Accepted
[Wed Oct 14 18:30:26 2026] 127.0.0.1:37226 Closing
[Wed Oct 14 18:31:00 2026] 127.0.0.1:45720 Accepted
[Wed Oct 14 18:31:00 2026] 127.0.0.1:45720 Closing
[Wed Oct 14 18:31:04 2026] 127.0.0.1:45730 Accepted
[Wed Oct 14 18:31:04 2026] 127.0.0.1:45730 Closing
[Wed Oct 14 18:31:34 2026] 127.0.0.1:52048 Accepted

Other app logs: downloads.log