Gladex Agent Logs

=== does CHANGELOG carry [0.4.383]? ===
11392:## [0.4.383] - 2026-10-31 — `record-gap` closes the unrecorded-run hazard class: the loop's post-run sweeps that carried CONTENT work no run recorded are now a dashboard red the moment they land (`tools/record-gap` + the `record-gap` row of `tools/system-status`, window = since the last `agent-logs/PROGRESS.md` touch; new suite **43/0**, `- Live:` 126 → **127**)

=== queue-source-check ===
queue-source-check: FAIL - 2 violation(s): [0.4.383] is not named in agent-logs/PROGRESS.md - the newest CHANGELOG entry has no record in the authoritative file; CHANGELOG.md was last touched by 6c0b464, agent-logs/PROGRESS.md by be3ab8f - the newest changelog entry landed after the run that recorded it
  - [0.4.383] is not named in agent-logs/PROGRESS.md - the newest CHANGELOG entry has no record in the authoritative file
  - CHANGELOG.md was last touched by 6c0b464, agent-logs/PROGRESS.md by be3ab8f - the newest changelog entry landed after the run that recorded it
rc=1

=== record-gap --help ===
usage: record-gap [-h] [--format {human,json}] [--repo DIR] [--since REF]
                  [--all]

Detect the loop's sweep commits that carried content work no run recorded: a 'run <id>: <ts> model=...' commit touching CHANGELOG.md, STRUCTURE.md, tools/, tests/, app/ or team/ since the last commit that touched agent-logs/PROGRESS.md.

options:
  -h, --help            show this help message and exit
  --format {human,json}
                        output format (default: human; json = one compact
                        object)
  --repo DIR            repo to check (default: GLADEX_REPO_DIR, else the repo
                        this script lives in)
  --since REF           override the window base (exclusive): scan REF..HEAD
                        instead of <last PROGRESS.md touch>..HEAD
  --all                 scan the whole history instead of the default window

exit codes:
  0 - no record gap in the window: every loop or identity SWEEP commit since
      the last recorded run touched no content path (CHANGELOG.md,
      STRUCTURE.md, tools/, tests/, app/, team/), and deliberate commits are
      owned by the run that made them
  1 - one or more record gaps, each named (sha, subject, the content paths it
      carried): the loop's sweep committed content no agent-logs/PROGRESS.md
      entry ever recorded - see the gaps[] array
  2 - invalid arguments (argparse validates before any git I/O)
  3 - cannot verify: not a git work tree, history unreadable, --since does not
      resolve, or no commit ever touched agent-logs/PROGRESS.md - NOT a pass,
      never reported as one
rc=0
> build · mimo-v2.6-flash-free
My run is **loop run 2818 / builder run 1024**. The `queue-source-check` is failing with exactly the transitional R8 for `[0.4.383]` — run 2817's unrecorded work. Let me verify everything live: run `record-gap` on the real repo, and check where "run 1024" is mentioned.
$ cd /data/repo
echo "=== where is 'run 1024' mentioned? ==="; grep -n 'run 1024' agent-logs/PROGRESS.md
echo ""
echo "=== record-gap on LIVE repo (human) ==="; ./tools/record-gap; echo "rc=$?"
echo ""
echo "=== record-gap on LIVE repo (json) ==="; ./tools/record-gap --format json; echo "rc=$?"
=== where is 'run 1024' mentioned? ===
18048:- **Two real bugs, caught by measuring the row against the live corpus before any reviewer saw the code — both fixed and disclosed.** (1) The first live run reported **`run 1024 exit=0`** while 1024's own last line is `exit=1`: `lo_lastid` was only set on failures, so the `ok` line named the last **red** id; the `ok` branch now records the newest completed id too (reviewer re-verified the arithmetic independently: `lo_start = max(0, total - window)`, newest index `total-1`, in-flight only newest+markerless+fresh). (2) The `… without exit marker` suffix was appended both inside the `ok` branch and by the post-chain append — duplicating itself on a recovered window with a dead run; the inline copy was removed. Both are recorded because a figure nobody can reproduce is a claim, not a measurement.

=== record-gap on LIVE repo (human) ===
record-gap: FAIL - 1 record gap(s) in window since be3ab8f: 1 loop sweep(s), 0 identity sweep(s), 0 deliberate, 1 record gap(s)
  - 6c0b464 run 2817: 2026-10-31T02:03Z model=opencode/mimo-v2.6-flash-free -> CHANGELOG.md, tests/test_record_gap.sh, tests/test_registry_coverage.sh, tools/REGISTRY.md, tools/record-gap, tools/system-status
rc=1

=== record-gap on LIVE repo (json) ===
{"detail": "1 record gap(s) in window since be3ab8f: 1 loop sweep(s), 0 identity sweep(s), 0 deliberate, 1 record gap(s)", "error": "1 record gap(s) in window since be3ab8f", "exit_code": 1, "gaps": [{"paths": ["CHANGELOG.md", "tests/test_record_gap.sh", "tests/test_registry_coverage.sh", "tools/REGISTRY.md", "tools/record-gap", "tools/system-status"], "sha": "6c0b4643a8e7133735b0a212de0499dc93bdf14f", "subject": "run 2817: 2026-10-31T02:03Z model=opencode/mimo-v2.6-flash-free"}], "ok": false, "repo_root": "/data/repo", "rules": {"content_hits": 6, "deliberate": 0, "identity_sweeps": 0, "loop_sweeps": 1}, "timestamp": "2026-10-31T02:17:23Z", "tool": "record-gap", "violations": ["sweep 6c0b464 (run 2817: 2026-10-31T02:03Z model=opencode/mimo-v2.6-flash-free) touched content path(s): CHANGELOG.md, tests/test_record_gap.sh, tests/test_registry_coverage.sh, tools/REGISTRY.md, tools/record-gap, tools/system-status - the run left work behind and its agent-logs/PROGRESS.md entry never landed"], "window": {"base": "be3ab8f", "base_source": "last_progress_touch", "commits": 1}}
rc=1
> build · mimo-v2.6-flash-free
`record-gap` works correctly — it names `6c0b464` (run 2817's unrecorded work) as the one live gap, exactly the transitional state my run-1024 entry will close. Now let me verify run 2817's work with the real test suites and investigate the stranded CHANGELOG edit.
$ cd /data/repo
echo "=== CHANGELOG.md mtime vs sweep commit time ==="
stat -c '%y %n' CHANGELOG.md
git log -1 --format='%ci %s' 6c0b464
echo ""
echo "=== which session made the stranded edit? check reflog/time ==="
git diff --stat CHANGELOG.md
echo ""
echo "=== run 2817 log tail (what did that session do at the end?) ==="
tail -30 /data/agent-logs/run-20261031-015115-2817.log 2>&1 | head -40
=== CHANGELOG.md mtime vs sweep commit time ===
2026-10-31 03:14:36.974728848 +0100 CHANGELOG.md
2026-10-31 03:03:51 +0100 run 2817: 2026-10-31T02:03Z model=opencode/mimo-v2.6-flash-free

=== which session made the stranded edit? check reflog/time ===
 CHANGELOG.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

=== run 2817 log tail (what did that session do at the end?) ===
hem**; the streak red `loop-outcomes` self-clears as green runs land, do not treat it as a defect. **Also still open, unchanged:** the **mia/aylin repin** (folded into dev 150 — 
do **not** send a fifth standalone row; only **Mia** is the retired-model pin); **2 hiring proposals `status=proposed`** (read-only until the investor approves); **NEEDS-INVESTOR**
: §14 renewal cadence, LAN-only A/B/C, SOA MNAME, Pip mail-policy D1–D4, `77.90.15.49` PTR; **standing reds A12 + A30** (7 failed `identity-run@*` units, all provider-side "Mode
l is unavailable" on this no-egress box); **coverage** human act (`--record` green-only — `baseline-stale` warning names 6 transcripts), **log-truncation** standing WARN unreopen
ed, run 952's **(i)**/**(iii)** triggers unchanged, **git-author fix** operator-owned, figure-reader fallback **EXHAUSTED** with `- Live:` **126** (no suite added this run — only
 this entry).
> build · mimo-v2.6-flash-free
Queue fully read. While the coverage suite runs (budget 1800s — it was timing out at 600s with only 310 assertions done), the remaining work all depends on its verdict. Status so far:

**Fixed both live-scope assertions by direct measurement, not prediction:**
1. **C28g** (`tests/test_registry_coverage.sh`): scope literal 35 → **36**, chain extended with `35 -> 36 with record-gap`. Verified by replicating the C28 sandbox exactly (fresh copy of `tools/` + the `verify-landing` plant, which *replaces* the real committed tool of the same name): child SUMMARY → `syn_n=36, syn_ok=35, violations=1` — exactly the C28 shape.
2. **G38**: my first edit guessed `cl_other=34` (only `--since REF`); the **live child run** measured `cl_other=35` — `record-gap` contributes *two* non-classified pairs (`--since REF` **and** `--repo DIR`, exactly like `attribution-gap` did). Corrected the assertion and its comment to 35 with "MEASURED on the live child run, not predicted".

Live child SUMMARY also confirmed every other live assertion my tool touches stays green: `violations=0`, `syn_ok=36` (usage row names flags), `--since` with no value → 2, H-section default claims agree (`human`/`GLADEX_REPO_DIR` on both sides), `fig_live=1 fig_claim=127 fig_stale=0`, partition closes (`cl_fmt 33 + cl_port 4 + cl_enum 3 + cl_num 15 + cl_declared 3 + cl_other 35 = cl_scope 93`).

Closing readings already taken: `version-check` → OK dev=0.4.28 prod=0.4.28 · `budget-show` → 2026-10 spent 0.00/5.00 · `regression-run --list` → **127**.

Next, once the suite lands green: append the run 1024 PROGRESS entry (naming `[0.4.383]` to clear live R8), commit by explicit pathspec, push, post-push re-reads.
$ cd /data/repo && git status --porcelain | head; echo ---; tail -c 400 /root/.local/share/opencode/shell/fa3e85b2145a60c127b5c9261e76a7ba6d520299/sh_18fb04979001pkQ31YNUVsauPG.out 2>/dev/null
M CHANGELOG.md
 M tests/test_registry_coverage.sh
 M tools/REGISTRY.md
 M tools/system-status
?? tests/test_record_gap.sh
?? tools/record-gap
---
> build · mimo-v2.6-flash-free
Working tree holds exactly the six expected paths. The coverage suite is still running — everything remaining (PROGRESS entry, commit, push) depends on its verdict, so I'll wait for it to complete.
exit=0
agent-loop-exit=0 run=2817
$ cd /data/repo
echo "=== test_record_gap.sh ==="; timeout 300 bash tests/test_record_gap.sh 2>&1 | tail -5; echo "rc=$?"
echo "=== test_registry_coverage.sh (validates stranded diff figures) ==="; timeout 600 bash tests/test_registry_coverage.sh 2>&1 | tail -5; echo "rc=$?"
=== test_record_gap.sh ===
PASS: G5: tool source uses git rev-parse (the documented probe)
PASS: G6: tool source uses git log (the documented reader)
PASS: H1: live repo answers 0 or 1 (got 1) — a genuine gap landing mid-run is allowed
PASS: H2: live json agrees with its own exit code (exit_code + ok)
result: 43 passed, 0 failed, exit 0
rc=0
=== test_registry_coverage.sh (validates stranded diff figures) ===
PASS: C37f exactly one violation - the stale sentence, and nothing else
PASS: C37g and the quoted bytes are NOT blamed: a gloss drift is not a quote drift
PASS: C37h all three gloss sites were counted, the two silent ones included
PASS: C37i plant: the comment's gloss is the stale one now
PASS: C37j plant: while this copy's own --help still quotes the derived one
rc=0
> build · mimo-v2.6-flash-free
`test_record_gap.sh` passes **43/0**. Now let me nail down the timeline of the stranded CHANGELOG edit (whose mtime is suspiciously close to my session start) and confirm no leftover process is writing to the tree.
$ date -u; date; echo "---"
echo "=== my own run log stat (birth/mtime) ==="
stat -c '%w | %y | %n' /data/agent-logs/run-20261031-031403-2818.log
echo "=== run 2817 log stat ==="
stat -c '%w | %y | %n' /data/agent-logs/run-20261031-015115-2817.log
echo "=== CHANGELOG stat ==="
stat -c '%w | %y | %n' /data/repo/CHANGELOG.md
echo "=== any leftover suite/coverage processes? ==="
ps aux | grep -Ei 'test_registry_coverage|coverage-guard|record-gap' | grep -v grep || echo "none"
echo "=== current tree ==="
cd /data/repo && git status --porcelain
Sat Oct 31 02:30:02 UTC 2026
Sat Oct 31 03:30:02 CET 2026
---
=== my own run log stat (birth/mtime) ===
2026-10-31 03:14:03.717474253 +0100 | 2026-10-31 03:30:02.091211061 +0100 | /data/agent-logs/run-20261031-031403-2818.log
=== run 2817 log stat ===
2026-10-31 01:51:15.559937892 +0100 | 2026-10-31 03:03:51.798944162 +0100 | /data/agent-logs/run-20261031-015115-2817.log
=== CHANGELOG stat ===
2026-10-15 15:24:37.411470355 +0200 | 2026-10-31 03:14:36.974728848 +0100 | /data/repo/CHANGELOG.md
=== any leftover suite/coverage processes? ===
none
=== current tree ===
 M CHANGELOG.md
> build · mimo-v2.6-flash-free
The timeline is now clear: run 2817's session ended at 03:03:51 (sweep-committed `6c0b464`), and a backgrounded helper from that session wrote the refined CHANGELOG bullet at 03:14:36 — after my run started. The stranded edit is legitimate run-2817 content that never got committed. Let me verify its figures and run the full gate suite.
$ cd /data/repo
echo "=== system-status record-gap row ==="
timeout 240 ./tools/system-status --format json 2>/dev/null | python3 -c "import json,sys; d=json.load(sys.stdin); rows=[c for c in d.get('checks',[]) if 'record' in c.get('name','')]; print(json.dumps(rows, indent=1)); print('overall:', d.get('overall'))" 2>&1
echo ""
echo "=== REGISTRY record-gap section ==="
grep -n 'record-gap' tools/REGISTRY.md | head -10
=== system-status record-gap row ===
[
 {
  "name": "record-gap",
  "status": "error",
  "detail": "1 record gap(s) in window since be3ab8f: 1 loop sweep(s), 0 identity sweep(s), 0 deliberate, 1 record gap(s)"
 }
]
overall: error

=== REGISTRY record-gap section ===
2706:- Record gap: `record-gap --format json --repo`'s verdict — the loop's post-run
3435:- `GLADEX_RECORD_GAP_BIN` (default: the sibling `record-gap`, resolved from this
3437:  record-gap check only (`[0.4.383]`). Same shape as the two above: a sandbox
5271:- Live (measured 2026-10-31): `./tools/regression-run` → **127 suites** discovered *(Refreshed **126 → 127** on 2026-10-31 by the run that added `tests/test_record_gap.sh`, the 127th suite — the hermetic guard for `tools/record-gap`, run 1024's queue step (the unrecorded-run hazard class run 1023 repaired, now closed by a check instead of prose). Measured at the moment of the write: `./tools/regression-run --list` → **127 suite(s) discovered**, `ls tests/test_*` → **127**, `git ls-tree -r --name-only HEAD tests/` → **126** 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 128th suite owns the next refresh.)* *(Refreshed **125 → 126** on 2026-10-28 by the run that added `tests/test_agent_loop_watchdog.sh`, the 126th suite — the hermetic guard for the system-scope `/usr/local/sbin/agent-loop-watchdog.sh`, whose defect run 1014 reproduced live the same day (42 consecutive `exit=1` runs 2394→2435 against 35 × `loop fresh, nothing to do`, 0 restarts, 0 warnings). Measured at the moment of the write: `./tools/regression-run --list` → **126 suite(s) discovered**, `ls tests/test_*` → **126**, `git ls-tree -r --name-only HEAD tests/` → **125** 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 127th suite owns the next refresh.)* *(Refreshed 123 → 124 on 2026-10-16 by the run that added `tests/test_jsonl_rotate.sh`, the 124th suite; it owns this refresh in the same commit, which is what clears section F's `figure_stale`.)* *(Refreshed **124 → 125** on 2026-10-16 by the run that added `tests/test_failed_units_classify.sh`, the 125th suite — the hermetic guard for `tools/failed-units-classify`, run 984's durable form of run 983's finding (which failed units will self-heal and which cannot, decided on whether their model still exists in the provider catalog). Measured at the moment of the write: `./tools/regression-run --list` → **125 suite(s) discovered**, `ls tests/test_*` → **125**, `git ls-tree -r --name-only HEAD tests/` → **124** 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 126th suite owns the next refresh.)* — 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.)* *(Refreshed **111 → 114** on 2026-10-14 by run 959 — **three suites landed without moving this line**: `tests/test_download_contrast.php` (the 112nd, `/download` colour-fidelity + the version-badge contrast fix, `b460155`), `tests/test_version_correction.php` (the 113rd, the version-correction regression test, `6895a58`) and `tests/test_attribution_gap.sh` (the 114th, run 959's own suite, which reached HEAD through a concurrent identity's `git add -A` safety-net sweep at `c2ee73f` while its tool reached it at `ee266f7` — the same mid-run sweep class the 85 → 86 note records), so `VIOLATION figure_stale 111` stood on the live tree until this refresh. Measured at the moment of the write: `./tools/regression-run --list` → **114 suite(s) discovered**, `ls tests/test_*` → **114**, `git ls-tree -r --name-only HEAD tests/` → **114** — 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 115th suite owns the next refresh.)* *(Refreshed **114 → 115** on 2026-10-15 by the run that added `tests/test_coverage_guard.sh`, the 115th suite — the hermetic guard for `tools/coverage-guard`, run 963's re-queued trend guard (`[0.4.353]`), whose `## coverage-guard` and `## test_coverage_guard.sh` sections landed in the same commit. Measured at the moment of the write: `./tools/regression-run --list` → **115 suite(s) discovered**, `ls tests/test_*` → **115**, `git ls-tree -r --name-only HEAD tests/` → **114** 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 116th suite owns the next refresh.)* *(Refreshed **115 → 116** on 2026-10-15 by the run that added `tests/test_baseline_stale.sh`, the 116th suite — the hermetic guard for `tools/baseline-stale`, run 964's re-queued baseline reader (`[0.4.353]`), whose `## baseline-stale` and `## test_baseline_stale.sh` sections landed in the same commit. Measured at the moment of the write: `./tools/regression-run --list` → **116 suite(s) discovered**, `ls tests/test_*` → **116**, `git ls-tree -r --name-only HEAD tests/` → **115** 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 117th suite owns the next refresh.)* *(Refreshed **116 → 117** on 2026-10-15 by the run that added `tests/test_system_status_baseline_stale.sh` (at the moment of this first write the 117th, renumbered the 119th by the `117 → 119` refresh below) — the guard for the `baseline-stale` row of `tools/system-status` (run 964's re-queued row, `[0.4.355]`), whose `## system-status` bullet, hook entry, Tests bullet and `## test_system_status_baseline_stale.sh` section landed in the same commit. Measured at the moment of the write: `./tools/regression-run --list` → **117 suite(s) discovered**, `ls tests/test_*` → **117**, `git ls-tree -r --name-only HEAD tests/` → **116** 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; superseded minutes later by the `117 → 119` refresh below, which re-measured the same tree.)* *(Refreshed **117 → 119** on 2026-10-15 — a **bystander-plus-own refresh**: `tests/test_gladex_binary.sh` (the 118th suite, a binary smoke test, `7807966`) landed from a concurrent Leon shift mid-run without moving this line, and `tests/test_system_status_baseline_stale.sh` (the 119th, this run's suite) is untracked, so `VIOLATION figure_stale 117` stood on the live tree and read as section F's F3 (`want=118 got=117` at the moment the batch measured it), F5, F6 and this suite's exactly-one-violation controls (`C7d` etc. measured `want=1 got=2`) — **56 reds in `tests/test_registry_coverage.sh` (441 passed / 56 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: `./tools/regression-run --list` → **119 suite(s) discovered**, `ls tests/test_*` → 119, `git ls-tree -r --name-only HEAD tests/` → 118 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 120th suite owns the next refresh.)* *(Refreshed **119 → 120** on 2026-10-15 by the run that added `tests/test_system_status_coverage_guard.sh`, the 120th suite — the guard for the `coverage-guard` row of `tools/system-status` (run 967's re-queued finding, `[0.4.357]`), whose `## system-status` bullet, hook entry, Tests bullet and `## test_system_status_coverage_guard.sh` section landed in the same commit. Measured at the moment of the write: `./tools/regression-run --list` → **120 suite(s) discovered**, `ls tests/test_*` → 120, `git ls-tree -r --name-only HEAD tests/` → 119 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 121st suite owns the next refresh.)* *(Refreshed **120 → 121** on 2026-10-15 by the run that added `tests/test_cross_reader_agreement.sh`, the 121st suite — the cross-reader agreement guard for run 968's re-queued line (one child reading must yield the same count and the same identity list on the `system-status` row and in `red-watch`), whose own `## test_cross_reader_agreement.sh` section landed in the same commit. Measured at the moment of the write: `./tools/regression-run --list` → **121 suite(s) discovered**, `ls tests/test_*` → **121**, `git ls-tree -r --name-only HEAD tests/` → **120** 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 122nd suite owns the next refresh.)* *(Bystander refresh **121 → 122**, 2026-10-15, run 970: `tests/test_docs_contrast.php` — the 122nd suite, a `/docs` WCAG-contrast guard — landed in `49b22cf` (18:21 CEST) without moving the claim above, so `VIOLATION figure_stale 121` stood on the live tree and read as section F's **F3** (`want=122 got=121`), **F5**, **F6**, **C39d** and every exactly-N-violation control that counts live violations — **55 reds in `tests/test_registry_coverage.sh` (442 passed / 55 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 **pre-existing at this run's start commit**: its `tests/` already held **122** `test_*` files against this line's **121**, so nothing here was caused by the run that repaired it. Measured at the moment of the write: `./tools/regression-run --list` → **122 suite(s) discovered**, `ls tests/test_*` → **122**, `git ls-tree -r --name-only HEAD tests/` → **122** — 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 123rd suite owns the next refresh.)* *(Refreshed **122 → 123** on 2026-10-16 by the run that added `tests/test_tmp_sweep.sh`, the 123rd suite — the hermetic guard for `tools/tmp-sweep`, run 977's queued durable half of the hand sweep (“a periodic age-based /tmp sweep … so a SIGKILL orphan cannot pile up for days again”), whose own `## tmp-sweep` and `## test_tmp_sweep.sh` sections landed in the same commit. Measured at the moment of the write: `./tools/regression-run --list` → **123 suite(s) discovered**, `ls tests/test_*` → 123, `git ls-tree -r --name-only HEAD tests/` → 122 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 124th suite owns the next refresh.)*
10538:## record-gap
10545:unrecorded-run hazard with a `record-gap` check"). The rule: a commit in the loop's SWEEP
10562:**Location**: `/data/repo/tools/record-gap` (extensionless, python3 shebang → `repo-lint`
10567:record-gap [--format {human,json}] [--repo DIR] [--since REF] [--all]
10591:**Wired into**: the `record-gap` row of `tools/system-status` (child contract identical to
10595:**Status**: Built ✅ 2026-10-31 (queue: run 1023's record-gap item). Live reading at
$ cd /data/repo
echo "=== registry coverage summary ==="
timeout 900 bash tests/test_registry_coverage.sh 2>&1 | grep -E 'result:|SUMMARY|failed' | tail -5
echo "rc=$?"
=== registry coverage summary ===
PASS: C28g scope now 36 tools that print an option list (pdns-api.py out; 23 -> 24 with cache-show; 24 -> 25 with tmp-lock; 25 -> 26 with download-stats; 26 -> 27 with shift-tally; 27 -> 28 with shift-deploy; 28 -> 29 with shift-census; 29 -> 30 with attribution-gap; 30 -> 31 with coverage-guard; 31 -> 32 with baseline-stale; 32 -> 33 with tmp-sweep; 33 -> 34 with jsonl-rotate; 34 -> 35 with failed-units-classify; 35 -> 36 with record-gap)
PASS: C38j all three quotes compared and passed, all three glosses compared and failed
PASS: C39d and it is the ONLY verdict: no VIOLATION, no SUMMARY - never a partial pass
PASS: G38 and the five left cl_other rather than being counted twice (35 non-classified pairs: 22 before cache-show, 24 with it, 25 with tmp-lock, 27 with attribution-gap, 28 with tmp-sweep, 30 with jsonl-rotate, 33 with failed-units-classify, 35 with record-gap)
=== Results: 497 passed, 0 failed ===
rc=0
> build · mimo-v2.6-flash-free
All of run 2817's figures verify so far: registry coverage **497/0** (C28g 36, G38 35 confirmed in PASS lines), record-gap suite **43/0**, the `system-status` row and `## record-gap` REGISTRY section exist. Now let me verify the remaining gate figures the stranded CHANGELOG edit claims, and run the slow suite in the background.
$ cd /data/repo
timeout 1200 bash tests/test_system_status_failed_units.sh > /tmp/opencode/gate-1024-16n.log 2>&1; echo "system_status_failed_units rc=$?"; tail -2 /tmp/opencode/gate-1024-16n.log
Command moved to the background (shell ID: sh_18fd95829001T8NOb5yxfC2Fna).
Output is streaming to: /root/.local/share/opencode/shell/fa3e85b2145a60c127b5c9261e76a7ba6d520299/sh_18fd95829001T8NOb5yxfC2Fna.out

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

[Sat Oct 31 03:38:07 2026] 127.0.0.1:33064 Closing
[Sat Oct 31 03:38:08 2026] 127.0.0.1:33072 Accepted
[Sat Oct 31 03:38:08 2026] 127.0.0.1:33072 Closed without sending a request; it was probably just an unused speculative preconnection
[Sat Oct 31 03:38:08 2026] 127.0.0.1:33072 Closing
[Sat Oct 31 03:39:04 2026] 127.0.0.1:40188 Accepted
[Sat Oct 31 03:39:04 2026] 127.0.0.1:40188 Closing
[Sat Oct 31 03:39:34 2026] 127.0.0.1:43170 Accepted
[Sat Oct 31 03:39:34 2026] 127.0.0.1:43170 Closing
[Sat Oct 31 03:40:33 2026] 127.0.0.1:47052 Accepted
[Sat Oct 31 03:40:33 2026] 127.0.0.1:47052 Closing
[Sat Oct 31 03:45:29 2026] 127.0.0.1:37978 Accepted
[Sat Oct 31 03:45:29 2026] 127.0.0.1:37978 Closing
[Sat Oct 31 03:45:29 2026] 127.0.0.1:37982 Accepted
[Sat Oct 31 03:45:29 2026] 127.0.0.1:37982 Closing
[Sat Oct 31 03:45:29 2026] 127.0.0.1:37994 Accepted
[Sat Oct 31 03:45:29 2026] 127.0.0.1:37994 Closing
[Sat Oct 31 03:45:29 2026] 127.0.0.1:38006 Accepted
[Sat Oct 31 03:45:29 2026] 127.0.0.1:38006 Closing
[Sat Oct 31 03:45:29 2026] 127.0.0.1:38018 Accepted
[Sat Oct 31 03:45:29 2026] 127.0.0.1:38018 Closing
[Sat Oct 31 03:45:29 2026] 127.0.0.1:38026 Accepted
[Sat Oct 31 03:45:29 2026] 127.0.0.1:38026 Closing
[Sat Oct 31 03:45:29 2026] 127.0.0.1:38030 Accepted
[Sat Oct 31 03:45:30 2026] 127.0.0.1:38030 Closing
[Sat Oct 31 03:45:30 2026] 127.0.0.1:38046 Accepted
[Sat Oct 31 03:45:30 2026] 127.0.0.1:38046 Closing
[Sat Oct 31 03:45:30 2026] 127.0.0.1:38054 Accepted
[Sat Oct 31 03:45:30 2026] 127.0.0.1:38054 Closing
[Sat Oct 31 03:45:30 2026] 127.0.0.1:38066 Accepted
[Sat Oct 31 03:45:30 2026] 127.0.0.1:38066 Closing
[Sat Oct 31 03:46:11 2026] 127.0.0.1:49390 Accepted
[Sat Oct 31 03:46:11 2026] 127.0.0.1:49390 Closing
[Sat Oct 31 03:46:15 2026] 127.0.0.1:38106 Accepted
[Sat Oct 31 03:46:15 2026] 127.0.0.1:38106 Closing
[Sat Oct 31 03:46:19 2026] 127.0.0.1:38120 Accepted
[Sat Oct 31 03:46:19 2026] 127.0.0.1:38120 Closing
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47314 Accepted
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47314 Closing
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47316 Accepted
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47316 Closing
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47320 Accepted
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47320 Closing
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47324 Accepted
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47324 Closing
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47340 Accepted
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47340 Closing
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47354 Accepted
[Sat Oct 31 03:46:50 2026] 127.0.0.1:47354 Closing
[Sat Oct 31 03:46:51 2026] 127.0.0.1:47356 Accepted
[Sat Oct 31 03:46:51 2026] 127.0.0.1:47356 Closing
[Sat Oct 31 03:46:51 2026] 127.0.0.1:47370 Accepted
[Sat Oct 31 03:46:51 2026] 127.0.0.1:47370 Closing
[Sat Oct 31 03:46:51 2026] 127.0.0.1:47384 Accepted
[Sat Oct 31 03:46:51 2026] 127.0.0.1:47384 Closing
[Sat Oct 31 03:46:51 2026] 127.0.0.1:47392 Accepted
[Sat Oct 31 03:46:51 2026] 127.0.0.1:47392 Closing
[Sat Oct 31 03:50:18 2026] 127.0.0.1:39218 Accepted
[Sat Oct 31 03:50:18 2026] 127.0.0.1:39218 Closing
[Sat Oct 31 03:50:18 2026] 127.0.0.1:39222 Accepted

Other app logs: downloads.log