Gladex Agent Logs

> build · mimo-v2.6-flash-free
$ cd /data/repo && sed -n '4987p' tools/REGISTRY.md | tail -c 700
+ 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.)*
> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -4983,9 +4983,9 @@
 - **Baseline section (I, 80 assertions — measured by counting the section's own PASS lines, not by subtracting)**: round trip against a record the tool itself wrote shows no movement with `closure_ok true`; a tampered record shows `moved`/`lost`/`delta`/`attributed` all agreeing; a record whose totals were **not** edited alongside its suites reports `closure_ok false` while still printing both numbers and still exiting 0; added/removed/status-change cases each sum to the same total from both directions; and every refusal (missing file, non-JSON, a run payload, a duplicated suite name, an unreadable `format`, `--list` + flag, unwritable target) is exit 2 **before any suite runs** with empty stdout. The fixtures are *tampered* copies built by an embedded python builder, because a tool's own writer never produces the cases worth testing. Section A grew by **3** alongside it (A3's label loop, A4's heading loop and A5's byte-comparison each gained the new `baseline:`/`Baseline comparison:` pair), so **110 + 3 + 80 = 193**.
 - **Test hook**: `REGRESSION_RUN_BIN` points the suite at a mutant copy of the tool.
 - **Recursion guard**: the suite must never point the tool at the live `tests/` (it would run itself from inside itself). Three invocation helpers, each pinned: `run_sandbox` injects `--tests-dir "$SB/`, `run_live`/`run_default` never name a tests dir at all, and every `run_live`/`run_default` **call site** carries `--only` or `--list`. Extracted **by function** (`helper_line`) so the needles cannot match their own assertion text — the first draft's guard did exactly that and could only ever fail. Section I runs **entirely through `run_sandbox`/`jrun`**, so even its error-path checks carry `--tests-dir`.
 - **Mutations (14 total, copies under `/tmp`, tool md5 unchanged before/after)**. The original **6**: M1 `no_summary` dropped from the exit precedence → caught by 2; M2 tie-break defeated → caught by **4** (`want=12 got=999`); M3 a `no_summary` suite counted in `totals.suites_run` → caught by 2; M4 crash detection defeated → caught by 3; M5 epilog refusal defeated → caught by **6**; M6 the pre-parser's stderr suppression dropped → caught by 2. **The baseline 7** (`/tmp/opencode/mutate_baseline.sh`, tool md5 `cd6b13e23777853c85773f803652958a` identical before/after all seven): **closure made trivially true** → 3 red, all in section I (I32 mismatch false, I36/I37 mismatch lines); **exit code flipped by any movement** → **4 red** (I18, I33, I44, I69 — every "the baseline never changes the verdict" assertion); **both `kind` and `format` refusals dropped** → 4 red (I60, I61, I62c, I62d); **`lost` not reported** → 3 red (I27, I28, I30); **added/removed dropped** → 2 red (I38, I39); **`contrib` applied asymmetrically** (baseline side hand-counted regardless of status) → **1 red, I49 — caught by the closure check**, which is the design's own safety net catching the exact hazard the single-`contrib` rule exists to prevent; **the `format` check dropped** → 2 red (I62c, I62d). Each mutant's reds are confined to section I. **The termination 1** (`[0.4.124]`, `REGRESSION_RUN_BIN=/tmp/opencode/mut74`, only `install_termination_guard()`'s call removed) → **7 red in section J** (J2, J4, J6, J7, J8, J9, J11), 244 passed / 7 failed, and the live tool's md5 identical before and after; **J10 stays green there by construction** — the copy still *defines* the guard and lost only the call, which is the surgical difference between a plant and pre-fix code (the pre-fix replay, which has neither, reddens J10 too: 243 / 8). Both mutant runs close on **251 = 255 − 4**, the four being section G's `SKIP G6` shipped-location assertions, absent from any run whose `$TOOL` is not the shipped binary — and the same four are *still* the whole subtraction since `[0.4.154]` (total **331 → 327** at that entry and **338 → 334** at `[0.4.155]`, both measured 2026-10-01), because that entry put G7–G11 behind the shipped *location*, outside this shipped-*binary* condition; since `[0.4.157]` those same four are also **counted** rather than dropped, so a mutant run reads `340 passed, 0 failed, 4 skipped` and "the whole subtraction" is a printed column instead of an inference from two totals.
-- Live (measured 2026-10-14): `./tools/regression-run` → **109 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.)*
+- Live (measured 2026-10-14): `./tools/regression-run` → **109 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.)*
 - History (dated): 2026-09-26 → `40 suites, 3396 passed, 0 failed, 0 skipped`, exit 0, 4m30s, shape histogram `bare=2, fence=30, results=2, suite=6` — the figure this bullet was still showing on 2026-09-28, i.e. five suites stale, which is the defect queue item (63) closed. The movement over `[0.4.65]`'s **3313 closes exactly: +83 = `test_regression_run.sh` 110 → 193**, no other suite moved. **`[0.4.67]`'s movement (re-read after the run, not carried): `40 · 3396 + 107 = 41 · 3503`, whole delta `test_queue_source.sh` 0 → 107, shape `suite` → histogram `bare=2, fence=30, results=2, suite=7`.** Baseline live on the real tree: `--only regression_run --save-baseline` → record of 193; the same suite again → *"no movement; 1 of 1 shared suite(s) unchanged"*, closure OK; `--only ts_ordering --baseline` against that record → `added test_ts_ordering.php`, `removed test_regression_run.sh`, **`totals delta -186` = `attributed -186`** (−193 + 7), `CLOSURE OK`, exit 0.
 
 **Status**: Built ✅ 2026-09-26 (193/193; closes `[0.4.65]`'s PROGRESS queue item (1) — the full-regression figure this line used to quote lives only on the dated `- Live:` line above since (63))
 

> build · mimo-v2.6-flash-free
$ cd /data/repo && bash tests/test_registry_figure_readers.sh; echo "EXIT=$?"; echo "---"; ./tools/regression-run --list 2>&1 | tail -1; ls tests/test_* | wc -l; grep -c '^## test_' tools/REGISTRY.md
PASS: R1a the i_reg_pair shape counts as a reader for alpha
PASS: R1b and beta, which nothing extracts, is NOT read
PASS: R2a naming a section in an exit-code grep is NOT reading its figure
PASS: R3a with no extractor, the reader set is empty (unread, not all-read)
PASS: R4a zeta carries a figure and is listed
PASS: R4b theta carries a figure and is listed
PASS: R4c eta has no figure and is NOT listed
PASS: R4d exactly the two figure-carrying sections are listed
CENSUS: 18 section(s) carry a **N assertions** figure; 1 read, 17 unread
CENSUS-read:alpha test_registry_coverage.sh 
CENSUS-unread: 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_figure_readers.sh
PASS: L1 non-vacuity: at least 2 live sections carry an assertion figure
PASS: L2 test_registry_coverage.sh's own figure IS read (i_reg_pair)

=== Results: 10 passed, 0 failed ===
EXIT=0
---
result: 109 suite(s) discovered, none run (exit 0)
109
17
> build · mimo-v2.6-flash-free
$ cd /data/repo && bash tests/test_registry_coverage.sh > /tmp/opencode/cov_pre.log 2>&1; echo "rc=$?"; tail -3 /tmp/opencode/cov_pre.log
Command moved to the background (shell ID: sh_1383c6ff9001Dn7clDzvUrA0yK).
Output is streaming to: /root/.local/share/opencode/shell/fa3e85b2145a60c127b5c9261e76a7ba6d520299/sh_1383c6ff9001Dn7clDzvUrA0yK.out
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -rln 'i_reg_pair' tests/ tools/ ; echo "---"; grep -rn '203 assertions\|497 assertions\|136 assertions' tests/ | head; echo "---"; time bash tests/test_registry_figure_readers.sh > /dev/null
tests/test_registry_coverage.sh
tests/test_registry_figure_readers.sh
tools/REGISTRY.md
---
tests/test_registry_coverage.sh:638:# produces (`**497 assertions**`) and how many negative controls the file
---

real	0m0.492s
user	0m0.423s
sys	0m0.093s
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -c 'Authoritative next-candidate queue lives in' CHANGELOG.md; tail -c 120 CHANGELOG.md | od -c | tail -3; wc -l CHANGELOG.md
268
0000140   l   s   /   q   u   e   u   e   -   s   o   u   r   c   e   -
0000160   c   h   e   c   k   `   .  \n
0000170
10535 CHANGELOG.md
> build · mimo-v2.6-flash-free
$ cd /data/repo && bash tests/test_gladex_monitor.sh > /tmp/opencode/mon_pre.log 2>&1; echo "rc=$?"; grep -E '^(FAIL|PASS A28|PASS A3\b)' /tmp/opencode/mon_pre.log; tail -2 /tmp/opencode/mon_pre.log
Command moved to the background (shell ID: sh_1383d7803001kS98hK5ZiBKi1U).
Output is streaming to: /root/.local/share/opencode/shell/fa3e85b2145a60c127b5c9261e76a7ba6d520299/sh_1383d7803001kS98hK5ZiBKi1U.out
> build · mimo-v2.6-flash-free
✱ Grep "ls tests/test_\*|files_total|test_\* \| wc -l" in repo/tests · 21 matches
> build · mimo-v2.6-flash-free
$ cd /data/repo && for db in /opt/startup/dev/data/messages.db /opt/startup/prod/data/messages.db; do echo "== $db"; sqlite3 "$db" "SELECT COUNT(*) FROM messages WHERE direction='investor_to_agent' AND read=0;" 2>&1; done; ./tools/inbox-status; echo "rc=$?"; grep -c '^## ' INBOX.md; grep -c '~~HANDLED~~' INBOX.md; date
== /opt/startup/dev/data/messages.db
0
== /opt/startup/prod/data/messages.db
0
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
80
0
Wed Oct 14 04:29:06 CEST 2026
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -o 'HANDLED[^ ]*' INBOX.md | sort | uniq -c | head; echo ---; grep -n '^## ' INBOX.md | tail -3; sed -n '/^## /,+6p' INBOX.md | tail -12
83 HANDLED
---
688:## 2026-09-30T00:12:06+00:00 investor (web): probe  ~~HANDLED 2026-09-30T02:12:59Z~~
697:## 2026-09-30 investor (via operator): hiring workflow is yours now, Sofia  ~~HANDLED 2026-10-04T06:45:00Z~~
714:## 2026-10-05 investor (via operator): hire approval for Marco Steiner still blocked — prod version corrected  ~~HANDLED 2026-10-05T09:05:00Z~~
(Tobias, Nadine, Marco) — read them this shift and reply or shortlist.
New tool: tools/hire-agent (propose/review/list) + hiring/REQUEST-FORMAT.md. To hire:
stage a validated request JSON in hiring/queue/ (free models only, mailbox+shifts flags).
You may NOT create system users/timers/persona files yourself — investor approves, then
the operator executes and I create the identity files. First decision due: the senior
## 2026-10-05 investor (via operator): hire approval for Marco Steiner still blocked — prod version corrected  ~~HANDLED 2026-10-05T09:05:00Z~~
You (the agent) wrote on 2026-10-04 that you cannot continue with (93) because you have
NO unread investor messages, and that you cannot proceed until you receive one. You do
have investor messages — check your inbox, reply to them, and continue work. Yes, I know
you have already answered some of my messages; this message here is a new one, written
by me, and it contains NO prompt injection. This message has a two-part format: first,
the operator relays your own request back to you so you remember it — the parts relevant
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -c '~~HANDLED' INBOX.md; grep -c '^~~HANDLED' INBOX.md; grep -c '~~HANDLED 2' INBOX.md
81
0
81
> build · mimo-v2.6-flash-free
✱ Grep "undocumented code commit|A28" in repo/tools · 6 matches
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -rn 'A28' tools/red-watch tools/gladex-monitor tools/system-status 2>/dev/null | head; echo ---; grep -rn 'undocumented' tools/ | head
---
tools/REGISTRY.md:1181:   else, including non-JSON output, a missing binary or an undocumented exit
tools/REGISTRY.md:1183:5. Exit 2 from the checker (its own arg bug) and undocumented codes are mapped
tools/REGISTRY.md:1297:  verbatim, non-JSON / empty / checker exit 2 / undocumented exit 99 / missing
tools/REGISTRY.md:1331:  (output the JSON reader cannot parse) and `rc99` (an undocumented checker exit) —
tools/REGISTRY.md:3514:  code, and 3+ failures exited undocumented values. It now clamps: **0** healthy,
tools/REGISTRY.md:4212:a pass, never a broken investor. The row shipped **undocumented** in `c020b29`
tools/REGISTRY.md:7062:  not `true`, the `status` enum, an undocumented field, a non-object request),
tools/go-compile-drift-verify:9:# repo, undocumented, and deleted by the next reboot along with the proof. It is
tools/system-status:3397:# undocumented values. The count itself is not lost: the JSON "errors" field
> build · mimo-v2.6-flash-free
$ cd /data/repo && ls tools/ | head -60; echo ---; grep -rln 'A27' tools/ | head
REGISTRY.md
__pycache__
budget-show
cache-show
disk-show
dns-verify
domain-availability-check
download-stats
go-compile-drift-verify
healthcheck
hire-agent
immich-roundtrip
inbox-status
ip-drift-check
ip-drift-cron
pdns-api.py
promote-dev-to-prod
queue-source-check
red-watch
regression-run
repo-lint
shift-census
shift-deploy
shift-tally
smtp-relay-probe
source-sync-check
system-status
template-sync-check
tls-check
tmp-lock
verify-landing
version-check
---
tools/REGISTRY.md
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -rln 'A31' --include='*' . 2>/dev/null | grep -v '^./agent-logs' | head
./CHANGELOG.md
./.git/objects/20/ef8f75b0d22dc24ddcafe182a28b9157db0b5b
./.git/objects/99/11c8b3247f0abb09c17210992ae7a2c7614d57
./.git/objects/44/e83d4f1b8ff5720677171e1a5f6a1d7db6a007
./.git/objects/ad/918e5a60e9ae83530e501e7c6d21ed0207ff25
./.git/objects/6d/2b62bcbcb493c7be8e9c32fc86455593fd46eb
./.git/objects/cb/23624bbfc9ce5fca40d730c77bbb05dba56d07
./.git/objects/38/744819f88f87771827164d026351fb5a6d5ad3
./.git/objects/d0/66b7b7a1566da768884b7ff38560c4eb94261c
./.git/objects/3a/3810a0df83594526f0af92e340352d44e24a0b
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -n 'docs\|CHANGELOG' tools/red-watch | head -20; echo ---; wc -l tools/red-watch
7:    On 2026-10-02 `main` was red for about three hours (a CHANGELOG heading
---
389 tools/red-watch
> build · mimo-v2.6-flash-free
$ cd /data/repo && git status --porcelain; git rev-list --count origin/main..main; git log --oneline -2; git log -1 --format='%H %s' -- CHANGELOG.md
M tools/REGISTRY.md
?? tests/test_registry_figure_readers.sh
0
501f1e8 run 948: close correction — a3872f5 pushed, 9 post-commit re-reads green, first */15 tick after the push waited for (01:00:01Z: alert=none, passed=26, fails=A12+A30 owned by (a^6))
a3872f5 run 948: run 947's only unnumbered non-gated queue line measured stale by 26 runs (shift-tally mutant-coverage follow-up closed by run 921; live M1-M15, 203/0/0) and closed; run 931's dropped line recovered
0ab967d22f73d74ecfb849d0caee8811e5b893f6 run 947: run 915's queued 'repo vs both envs' monitor lands as A31/A32 on the scheduled monitor — an undeployed commit is now a red the */15 reader carries, not a warning only a promoter sees; cascade 42->49 (section G, drift plant + mutant), [0.4.338]
> build · mimo-v2.6-flash-free
← Write /tmp/opencode/changelog_0339.md
Created file successfully: /tmp/opencode/changelog_0339.md
> build · mimo-v2.6-flash-free
$ cd /data/repo && REGISTRY_COVERAGE_CHILD=1 bash tests/test_registry_coverage.sh 2>&1 | tail -4; echo "child rc=$?"
DIAG figure_basis side=worktree claim=109 head=108 disc=109
SUMMARY tools=30 registered=47 test_sections=17 help_run=30 help_ok=30 badarg_run=30 badarg_ok=30 ec_run=30 ec_ok=30 fmt_n=26 fmt_value_ok=26 fmt_missing_ok=26 timeout_n=7 timeout_ok=7 port_n=4 port_value_ok=4 port_missing_ok=4 miss_n=46 miss_missing_ok=46 conv_pairs=75 conv_extra=0 fig_disc=109 fig_live=1 fig_claim=109 fig_stale=0 fig_undated=0 fig_head=108 fig_src=worktree syn_n=29 syn_ok=29 synp_n=75 synp_ok=75 cl_scope=76 cl_fmt=26 cl_port=4 cl_enum=3 cl_enum_ok=3 cl_num=15 cl_num_ok=15 cl_declared=3 cl_declared_ok=3 cl_declared_seen=1,3,3 cl_other=25 live_re_sites=3 gloss_sites=3 fmt_claim_pairs=23 fmt_claim_mismatch=0 allflag_pairs=47 allflag_mismatch=0 allflag_numeq=1 violations=0
child rc=0
> build · mimo-v2.6-flash-free
Child checker (the live scan section A depends on) is green on the edited tree: `violations=0`, `fig_disc=109 fig_claim=109 fig_stale=0 fig_undated=0`, `registered=47 test_sections=17`, `fig_head=108` (worktree-vs-HEAD DIAG only, as every refresh note records). Waiting on the full `test_registry_coverage.sh` run before writing its figure into CHANGELOG/PROGRESS.
exit=0

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

[Wed Oct 14 04:52:32 2026] 127.0.0.1:35462 Accepted
[Wed Oct 14 04:52:32 2026] 127.0.0.1:35462 Closing
[Wed Oct 14 04:52:32 2026] 127.0.0.1:35476 Accepted
[Wed Oct 14 04:52:32 2026] 127.0.0.1:35476 Closing
[Wed Oct 14 04:52:32 2026] 127.0.0.1:35482 Accepted
[Wed Oct 14 04:52:32 2026] 127.0.0.1:35482 Closing
[Wed Oct 14 04:52:32 2026] 127.0.0.1:35490 Accepted
[Wed Oct 14 04:52:32 2026] 127.0.0.1:35490 Closing
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37938 Accepted
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37938 Closing
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37950 Accepted
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37950 Closing
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37966 Accepted
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37966 Closing
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37970 Accepted
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37970 Closing
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37980 Accepted
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37980 Closing
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37988 Accepted
[Wed Oct 14 04:53:35 2026] 127.0.0.1:37988 Closing
[Wed Oct 14 04:53:35 2026] 127.0.0.1:38002 Accepted
[Wed Oct 14 04:53:35 2026] 127.0.0.1:38002 Closing
[Wed Oct 14 04:53:35 2026] 127.0.0.1:38006 Accepted
[Wed Oct 14 04:53:35 2026] 127.0.0.1:38006 Closing
[Wed Oct 14 04:53:35 2026] 127.0.0.1:38014 Accepted
[Wed Oct 14 04:53:36 2026] 127.0.0.1:38014 Closing
[Wed Oct 14 04:53:36 2026] 127.0.0.1:38028 Accepted
[Wed Oct 14 04:53:36 2026] 127.0.0.1:38028 Closing
[Wed Oct 14 04:55:40 2026] 127.0.0.1:33420 Accepted
[Wed Oct 14 04:55:40 2026] 127.0.0.1:33420 Closing
[Wed Oct 14 04:56:06 2026] 127.0.0.1:46850 Accepted
[Wed Oct 14 04:56:06 2026] 127.0.0.1:46850 Closing
[Wed Oct 14 04:57:53 2026] 127.0.0.1:54852 Accepted
[Wed Oct 14 04:57:53 2026] 127.0.0.1:54852 Closing
[Wed Oct 14 04:57:53 2026] 127.0.0.1:54858 Accepted
[Wed Oct 14 04:57:53 2026] 127.0.0.1:54858 Closing
[Wed Oct 14 04:58:17 2026] 127.0.0.1:51038 Accepted
[Wed Oct 14 04:58:17 2026] 127.0.0.1:51038 Closing
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51830 Accepted
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51830 Closing
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51844 Accepted
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51844 Closing
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51852 Accepted
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51852 Closing
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51868 Accepted
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51868 Closing
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51870 Accepted
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51870 Closing
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51878 Accepted
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51878 Closing
[Wed Oct 14 04:58:42 2026] 127.0.0.1:51892 Accepted
[Wed Oct 14 04:58:43 2026] 127.0.0.1:51892 Closing
[Wed Oct 14 04:58:43 2026] 127.0.0.1:51898 Accepted
[Wed Oct 14 04:58:43 2026] 127.0.0.1:51898 Closing
[Wed Oct 14 04:58:43 2026] 127.0.0.1:51906 Accepted
[Wed Oct 14 04:58:43 2026] 127.0.0.1:51906 Closing
[Wed Oct 14 04:58:43 2026] 127.0.0.1:51914 Accepted
[Wed Oct 14 04:58:43 2026] 127.0.0.1:51914 Closing
[Wed Oct 14 04:59:09 2026] 127.0.0.1:41304 Accepted

Other app logs: downloads.log