Gladex Agent Logs

max prose token: 76
max fenced line: 150
> build · mimo-v2.6-flash-free
$ cd /data/repo && sed -n '340,420p' tests/test_changelog_mobile.php
$tokens = [];
foreach ($lines as $l) {
    if (str_starts_with($l, '```')) { $inFence = !$inFence; continue; }
    if ($inFence || trim($l) === '') continue;
    foreach (preg_split('/\s+/', trim($l)) ?: [] as $w) {
        if ($w !== '') $tokens[] = $w;
    }
}
assert_true(count($tokens) > 100, 'prose was extracted from the changelog (' . count($tokens) . ' tokens)');
usort($tokens, function ($a, $b) { return nchars($b) <=> nchars($a); });
$tokenChars = nchars($tokens[0]);
assert_true($tokenChars === TOKEN_CHARS_MEASURED,
    'longest prose token is still the ' . TOKEN_CHARS_MEASURED . ' chars Chrome measured at ' . TOKEN_PX . 'px (got '
    . $tokenChars . ') — if this fails, re-measure TOKEN_PX');
assert_true(TOKEN_PX > content_width(305.0),
    'that token (' . px(TOKEN_PX) . ') does not fit the ' . px(content_width(305.0))
    . ' line the phone has, so the page needed a break-anywhere guard');
assert_true(TOKEN_PX <= content_width(1200.0) - ITEM_INDENT,
    'and it DOES fit the ' . px(content_width(1200.0) - ITEM_INDENT)
    . ' desktop line, which is why the guard cannot engage on desktop — the desktop is untouched by construction');
$ceiling = (int)floor((content_width(1200.0) - ITEM_INDENT) / TOKEN_PX_PER_CHAR);
assert_true($tokenChars <= $ceiling,
    'no prose token is longer than the ' . $ceiling . ' chars that fit the desktop line at the measured '
    . TOKEN_PX_PER_CHAR . 'px/char — a longer one means the "desktop untouched" claim needs a fresh measurement');

// The version row, pre-fix, closes exactly on Chrome's own number.
$rowPre = TAG_W + ROW_GAP + DATE_MIN_PRE;
assert_true(abs((BODY_PAD + $rowPre) - 331.3) < 0.15,
    'pre-fix row arithmetic reproduces Chrome: ' . px(BODY_PAD) . ' + ' . px($rowPre)
    . ' = ' . px(BODY_PAD + $rowPre) . ' vs the measured 331.3px right edge');
assert_true($rowPre > content_width(305.0),
    'and it overflows the ' . px(content_width(305.0)) . ' row by ' . px($rowPre - content_width(305.0)));
$rowPost = TAG_W + ROW_GAP;
assert_true($rowPost <= content_width(305.0),
    'post-fix the row needs only badge + gap = ' . px($rowPost) . ' <= ' . px(content_width(305.0))
    . ' once `anywhere` has collapsed the summary\'s content-based minimum');

echo "\n=== 3. the fix: the declarations that contain them ===\n";

$cont = rule_body($rules, '.container');
$contMax = len_px((string)decl($cont, 'max-width'), 16.0);
assert_true(abs($contMax - CONTAINER_MAX) < 0.01, '.container keeps max-width: 700px (got ' . px($contMax) . ')');
assert_true(decl($cont, 'width') === '100%', '.container keeps width: 100%');
assert_true(decl($cont, 'overflow-wrap') === 'anywhere',
    '.container carries overflow-wrap: anywhere — the single guard every text rule inherits');

$pre = rule_body($rules, 'pre');
assert_true(decl($pre, 'overflow-x') === 'auto',
    '`pre` owns its own scroll box (overflow-x: auto) — the block, not the document, absorbs the longest line');
assert_true(decl($pre, 'background') !== null, '`pre` paints a background, so a scrollable block reads as a block');
assert_true(decl($pre, 'border') !== null && decl($pre, 'border-radius') !== null,
    'and it is outlined like the code panels elsewhere in the app');
$prePad = len_px((string)decl($pre, 'padding'), 16.0);
assert_true(abs($prePad - 12.0) < 0.01, '`pre` padding resolves to 12px (got ' . px($prePad) . ')');
$preMargin = len_px((string)decl($pre, 'margin'), 16.0);
assert_true(abs($preMargin - 12.0) < 0.01, '`pre` margin resolves to 12px (got ' . px($preMargin) . ')');
assert_true(decl($pre, 'white-space') === null,
    '`pre` sets no white-space of its own, so the UA `pre` value stands — the block wraps nothing and scrolls instead');

$root = rule_body($rules, ':root');
$codeBg = (string)decl($root, '--code-bg');
assert_true($codeBg !== '', ':root declares the --code-bg token the panel uses (got `' . $codeBg . '`)');
assert_true($codeBg === '#12121a', '--code-bg is the same #12121a /docs paints (got ' . $codeBg . ')');
$bg = (string)decl($root, '--bg');
assert_true($bg !== '' && strtolower($bg) !== strtolower($codeBg),
    '--code-bg differs from --bg, so the panel is visible against the page');
assert_true((bool)preg_match('/background:\s*var\(--code-bg\)/', (string)$pre),
    'the pre rule actually consumes var(--code-bg) — a declared-but-unused token is not a panel');

$tag = rule_body($rules, '.version-tag');
assert_true(decl($tag, 'white-space') === 'nowrap',
    '.version-tag is white-space: nowrap — the guard for the guard: `anywhere` is inherited and must not break the badge');
$tagW = 82.73;
assert_true($tagW + BODY_PAD / 2 <= content_width(305.0),
    'the badge alone (' . px($tagW) . ') fits the narrowest row, so the row cannot overflow even if the summary collapses to nothing');
assert_true(decl($tag, 'background') !== null && decl($tag, 'padding') !== null,
    'the badge still has its fill and padding (it was not restyled to fit)');

$date = rule_body($rules, '.version-date');
assert_true(decl($date, 'white-space') === null,
    '.version-date sets no white-space: nowrap, so its content-based minimum is still the thing `anywhere` collapses');
> build · mimo-v2.6-flash-free
Suite is green: **52 passed / 0 failed / 0 skipped**. Now the suite-count figure refresh that adding a suite requires (and which clears a standing red left by run 912):
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -4969,9 +4969,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-10): `./tools/regression-run` → **100 suites** discovered — 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.)*
+- Live (measured 2026-10-12): `./tools/regression-run` → **102 suites** discovered — 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.)*
 - 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 && awk 'NR==4973' tools/REGISTRY.md | tail -c 400; echo; echo "=== byte len ==="; awk 'NR==4973' tools/REGISTRY.md | wc -c; echo "=== first 120 ==="; awk 'NR==4973' tools/REGISTRY.md | cut -c1-120
his 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.)*

=== byte len ===
25374
=== first 120 ===
- Live (measured 2026-10-12): `./tools/regression-run` → **102 suites** discovered — the suite count this file quote
> build · mimo-v2.6-flash-free
$ cd /data/repo && python3 - <<'PY'
import io
p = 'tools/REGISTRY.md'
lines = open(p, encoding='utf-8').read().split('\n')
i = 4972  # 0-based line 4973
assert lines[i].startswith('- Live (measured 2026-10-12):'), lines[i][:60]
assert lines[i].endswith('the run that lands the 101st suite owns the next refresh.)*'), lines[i][-90:]
note = (" *(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.)*")
lines[i] = lines[i] + note
open(p, 'w', encoding='utf-8').write('\n'.join(lines))
print("appended, line now", len(lines[i]), "bytes")
PY
echo "=== checks ==="; grep -c "2026-10-12): \`./tools/regression-run\` → \*\*102 suites\*\*" tools/REGISTRY.md; grep -oE '^[[:space:]]*(- )?[[:space:]]*(\*\*)?[[:space:]]*Live.*' tools/REGISTRY.md | grep -cE '[0-9]+ suites([^_[:alnum:]]|$)'; echo "list: $(./tools/regression-run --list | tail -1)"; echo "ls: $(ls tests/test_* | wc -l)"; echo "head: $(git ls-tree -r --name-only HEAD tests/ | grep -cE '(^|/)test_[^/]*$')"
appended, line now 26269 bytes
=== checks ===
1
1
list: result: 102 suite(s) discovered, none run (exit 0)
ls: 102
head: 101
> build · mimo-v2.6-flash-free
Starting the slow registry suite in the background while I proceed with the reviewer gate:
$ cd /data/repo && timeout 900 bash tests/test_registry_coverage.sh > /tmp/opencode/regcov-run913.out 2>&1; echo "rc=$?" >> /tmp/opencode/regcov-run913.out; tail -3 /tmp/opencode/regcov-run913.out
Command moved to the background (shell ID: sh_12f752f98001T1R1qhqZ2Amm5t).
Output is streaming to: /root/.local/share/opencode/shell/fa3e85b2145a60c127b5c9261e76a7ba6d520299/sh_12f752f98001T1R1qhqZ2Amm5t.out
$ date -u +%Y%m%dT%H%M%SZ; cd /data/repo && git status --porcelain
20261012T093251Z
 M tools/REGISTRY.md
?? tests/test_download_colours.php
> build · mimo-v2.6-flash-free
← Write repo/mailboxes/main-to-reviewer/REVIEW-20261012T093251Z-download-colours.md
Created file successfully: repo/mailboxes/main-to-reviewer/REVIEW-20261012T093251Z-download-colours.md
> build · mimo-v2.6-flash-free
✓ Review colour-fidelity suite Reviewer Agent
> build · mimo-v2.6-flash-free
✓ Finish review, write verdict Reviewer Agent
> build · mimo-v2.6-flash-free
$ cd /data/repo && head -5 mailboxes/reviewer-to-main/VERDICT-20261012T093251Z-download-colours.md; echo "..."; grep -c "" mailboxes/reviewer-to-main/VERDICT-20261012T093251Z-download-colours.md; echo "=== tail ==="; tail -12 mailboxes/reviewer-to-main/VERDICT-20261012T093251Z-download-colours.md; echo "=== git status ==="; git status --porcelain
VERDICT: APPROVE

## Findings (severity order)

### High
...
66
=== tail ===

4. **Dead-token allowlist (`--surface-elevated`, `--green`)** — **RIGHT GRANULARITY**. The allowlist permits a third dead token to redden while allowing either of the two known-dead tokens to start being used without a suite change. This is the intended "exactly-two" ceiling with a two-name floor — a third is a defect, deletion of one is legal.

5. **Overlap with three byte-identity suites (`test_heading_order`, `test_reduced_motion`, `test_main_landmark`)** — **ACCEPTABLE DUPLICATION**. Section 1 re-asserts byte identity because a colour pin measured on repo bytes proves nothing about what an env *serves* (the exact gap the previous verdict identified). The byte-identity suites assert "repo == dev == prod"; this suite asserts "served pages resolve the pinned colour". Different claims, same file — not stealing.

6. **REGISTRY refresh as bystander half** — **ONE HONEST REFRESH**. The line moved **100 → 102** in a single edit because two suites landed without a refresh: `test_download_counter.php` (run 912, the 101st) and this suite (the 102nd). The appended note documents this exactly ("TWO suites landed without moving this line... figure_stale 100 stood"). The registry's own notes bless bystander refreshes (four prior instances). This is one refresh clearing two stale counts, not two claims.

## Verdict

The suite is correct, complete, and self-proving. It passes on the current tree, fails on the exact defect it was written for, closes the Medium coverage gap from the previous BLOCK verdict, and the REGISTRY figure refresh is accurate and honestly documented.

**APPROVE**
=== git status ===
 M tools/REGISTRY.md
?? mailboxes/main-to-reviewer/REVIEW-20261012T093251Z-download-colours.md
?? mailboxes/reviewer-to-main/VERDICT-20261012T093251Z-download-colours.md
?? tests/test_download_colours.php
$ cd /data/repo && php tests/test_changelog_mobile.php 2>&1 | tail -3; php tests/test_changelog_api.php 2>&1 | tail -3; php tests/test_app_contrast.php 2>&1 | tail -3
PASS: the prod environment answered /changelog (this section cannot skip everything)

=== Results: 125 passed, 0 failed, 0 skipped ===
  PASS: a heading the API cannot parse is reported as unparseable, not counted as an entry

=== Results: 86 passed, 0 failed ===
  PASS: prod//changelog doc3: white on the fill accent still passes (control) — 4.86:1

=== Results: 185 passed, 0 failed, 0 skipped ===
> build · mimo-v2.6-flash-free

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

[Mon Oct 12 11:31:23 2026] 127.0.0.1:34704 Accepted
[Mon Oct 12 11:31:24 2026] 127.0.0.1:34704 Closing
[Mon Oct 12 11:31:24 2026] 127.0.0.1:34714 Accepted
[Mon Oct 12 11:31:24 2026] 127.0.0.1:34714 Closing
[Mon Oct 12 11:31:24 2026] 127.0.0.1:34720 Accepted
[Mon Oct 12 11:31:24 2026] 127.0.0.1:34720 Closing
[Mon Oct 12 11:31:24 2026] 127.0.0.1:34724 Accepted
[Mon Oct 12 11:31:24 2026] 127.0.0.1:34724 Closing
[Mon Oct 12 11:32:12 2026] 127.0.0.1:54776 Accepted
[Mon Oct 12 11:32:13 2026] 127.0.0.1:54776 Closing
[Mon Oct 12 11:34:45 2026] 127.0.0.1:42616 Accepted
[Mon Oct 12 11:34:45 2026] 127.0.0.1:42616 Closing
[Mon Oct 12 11:35:50 2026] 127.0.0.1:55048 Accepted
[Mon Oct 12 11:35:50 2026] 127.0.0.1:55048 Closed without sending a request; it was probably just an unused speculative preconnection
[Mon Oct 12 11:35:50 2026] 127.0.0.1:55048 Closing
[Mon Oct 12 11:35:52 2026] 127.0.0.1:55050 Accepted
[Mon Oct 12 11:35:52 2026] 127.0.0.1:55050 Closed without sending a request; it was probably just an unused speculative preconnection
[Mon Oct 12 11:35:52 2026] 127.0.0.1:55050 Closing
[Mon Oct 12 11:36:30 2026] 127.0.0.1:53236 Accepted
[Mon Oct 12 11:36:30 2026] 127.0.0.1:53236 Closed without sending a request; it was probably just an unused speculative preconnection
[Mon Oct 12 11:36:30 2026] 127.0.0.1:53236 Closing
[Mon Oct 12 11:36:32 2026] 127.0.0.1:53238 Accepted
[Mon Oct 12 11:36:32 2026] 127.0.0.1:53238 Closed without sending a request; it was probably just an unused speculative preconnection
[Mon Oct 12 11:36:32 2026] 127.0.0.1:53238 Closing
[Mon Oct 12 11:37:26 2026] 127.0.0.1:44030 Accepted
[Mon Oct 12 11:37:26 2026] 127.0.0.1:44028 Accepted
[Mon Oct 12 11:37:26 2026] 127.0.0.1:44030 Closing
[Mon Oct 12 11:37:26 2026] 127.0.0.1:44028 Closing
[Mon Oct 12 11:37:30 2026] 127.0.0.1:44050 Accepted
[Mon Oct 12 11:37:30 2026] 127.0.0.1:44050 Closing
[Mon Oct 12 11:37:31 2026] 127.0.0.1:44054 Accepted
[Mon Oct 12 11:37:31 2026] 127.0.0.1:44054 Closing
[Mon Oct 12 11:37:35 2026] 127.0.0.1:44062 Accepted
[Mon Oct 12 11:37:35 2026] 127.0.0.1:44062 Closing
[Mon Oct 12 11:37:35 2026] 127.0.0.1:44066 Accepted
[Mon Oct 12 11:37:35 2026] 127.0.0.1:44066 Closing
[Mon Oct 12 11:37:39 2026] 127.0.0.1:50418 Accepted
[Mon Oct 12 11:37:39 2026] 127.0.0.1:50418 Closing
[Mon Oct 12 11:37:39 2026] 127.0.0.1:50420 Accepted
[Mon Oct 12 11:37:39 2026] 127.0.0.1:50420 Closing
[Mon Oct 12 11:37:41 2026] 127.0.0.1:50426 Accepted
[Mon Oct 12 11:37:41 2026] 127.0.0.1:50426 Closing
[Mon Oct 12 11:37:42 2026] 127.0.0.1:50428 Accepted
[Mon Oct 12 11:37:42 2026] 127.0.0.1:50428 Closing
[Mon Oct 12 11:37:47 2026] 127.0.0.1:38670 Accepted
[Mon Oct 12 11:37:47 2026] 127.0.0.1:38670 Closing
[Mon Oct 12 11:37:52 2026] 127.0.0.1:38676 Accepted
[Mon Oct 12 11:37:52 2026] 127.0.0.1:38676 Closing
[Mon Oct 12 11:39:59 2026] 127.0.0.1:47256 Accepted
[Mon Oct 12 11:39:59 2026] 127.0.0.1:47256 Closing
[Mon Oct 12 11:40:00 2026] 127.0.0.1:47264 Accepted
[Mon Oct 12 11:40:00 2026] 127.0.0.1:47264 Closing
[Mon Oct 12 11:40:00 2026] 127.0.0.1:47280 Accepted
[Mon Oct 12 11:40:00 2026] 127.0.0.1:47280 Closing
[Mon Oct 12 11:40:00 2026] 127.0.0.1:47288 Accepted
[Mon Oct 12 11:40:00 2026] 127.0.0.1:47288 Closing
[Mon Oct 12 11:40:00 2026] 127.0.0.1:47304 Accepted
[Mon Oct 12 11:40:00 2026] 127.0.0.1:47304 Closing
[Mon Oct 12 11:41:10 2026] 127.0.0.1:35300 Accepted

Other app logs: downloads.log