Gladex Agent Logs

    run_mutation M22 'err_dns → does not borrow the missing-egress action'
    run_mutation M23 'err_ip → named arm diagnosis says no public IPv4 could be found'
    run_mutation M24 'err_no_a → does not borrow the dead-lookup action'
    run_mutation M25 "err_int → default arm action points at the checker's own output"
    run_mutation M26 'err_int → does not declare the egress untrustworthy'
    run_mutation M27 "err_dns → does not borrow the default arm's action"
    run_mutation M28 "err_no_a → does not borrow the default arm's action"
    run_mutation M29 'err_dns → does not borrow the vanished-A diagnosis'
    run_mutation M30 'err_int → does not diagnose a vanished A record'
fi

# =============================================================================
echo ""
echo "=== Results: $PASS passed, $FAIL failed ==="
[ "$FAIL" -eq 0 ] || exit 1
exit 0
> build · mimo-v2.6-flash-free
STEP 0 is clear (0 unread, 0 open). Now the queue item (z). Let me read the surrounding harness structure first.
$ cd /data/repo && sed -n '1240,1342p' tests/test_ip_drift_cron.sh
# Read a third time for M13/M14 (queue item (q), 2026-10-05): both pins
# redirected to `no drift → nothing appended to ALERTS`, which both of those
# defects leave green while it still prints its own `ok - …` line →
# **335 passed / 2 failed** (337 total under `IPDRIFT_NO_LIVE=1`, the 3 live
# assertions absent; 340 without that env), again both reds
# `wrong verdict is NOT the intended one`.
#
# Read a fourth time for M15/M16 (queue item (r), 2026-10-05): the two new
# DIAGNOSIS pins redirected the same way, in a fake tree (`tests/` + `tools`
# copied so `REPO=` resolves there) → **343 passed / 2 failed** (345 total
# under `IPDRIFT_NO_LIVE=1`, 348 without it), both reds `wrong verdict is NOT
# the intended one`, and the redirected pin counted **once** as its own `ok - …`
# line in a clean run of that tree — a real assertion, so the redirect tests
# the pin and not a duplicate.
#
# Read a fifth time for M17/M18 (queue item (s), 2026-10-05): the two `case`-
# arm pins redirected the same way, in a fake tree (`tests/` + `tools` copied
# so `REPO=` resolves there) → **351 passed / 2 failed** (353 total under
# `IPDRIFT_NO_LIVE=1`, 356 without it), both reds `wrong verdict is NOT the
# intended one`, and the redirected pin counted **once** as its own `ok - …`
# line in a clean run of that tree (280/0) — a real assertion, so the redirect
# tests the pin and not a duplicate.
#
# Read a sixth time for M19/M20 (queue item (t), 2026-10-05): the two `case`-
# arm pins redirected the same way (`err_ip → does not borrow the vanished-A
# diagnosis` and `err_no_a → does not borrow the dead-lookup diagnosis` →
# `no drift → nothing appended to ALERTS`, an assertion neither defect
# reddens while it still prints its own `ok - …` line), in a fake tree
# (`tests/` + `tools` copied so `REPO=` resolves there) → **359 passed /
# 2 failed, rc 1** (361 total under `IPDRIFT_NO_LIVE=1`, 364 without it),
# both reds `wrong verdict is NOT the intended one`, and the redirected pin
# counted **once** as its own `ok - …` line in a clean run of that tree
# (280/0) — a real assertion, so the redirect tests the pin and not a
# duplicate.
#
# Read a seventh time for M21/M22 (queue item (u), 2026-10-05): the two `case`-
# arm pins redirected the same way (`err_no_a → does not borrow the
# missing-egress diagnosis` and `err_dns → does not borrow the missing-egress
# action` → `no drift → nothing appended to ALERTS`, an assertion neither
# defect reddens while it still prints its own `ok - …` line), in a fake tree
# (`tests/` + `tools` copied so `REPO=` resolves there) → **367 passed /
# 2 failed, rc 1** (369 total under `IPDRIFT_NO_LIVE=1`, 372 without it),
# both reds `wrong verdict is NOT the intended one`, and the redirected pin
# counted **once** as its own `ok - …` line in a clean run of that tree
# (280/0) — a real assertion, so the redirect tests the pin and not a
# duplicate. M22's pin matters more than most: it is the FIRST mutant whose
# defect is confined to one half of a `case` arm's pair, so if its pin were
# loose the battery could not tell a missing ACTION from a missing DIAGNOSIS.
#
# Read an eighth time for M23/M24 (queue item (v), 2026-10-06): the two
# single-half pins redirected the same way (`err_ip → named arm diagnosis says
# no public IPv4 could be found` and `err_no_a → does not borrow the dead-
# lookup action` → `no drift → nothing appended to ALERTS`, an assertion both
# defects leave green while it still prints its own `ok - …` line), in a fake
# tree (`tests/` + `tools` copied so `REPO=` resolves there) → **375 passed /
# 2 failed, rc 1** (377 total under `IPDRIFT_NO_LIVE=1`, 380 without it:
# **378 passed / 2 failed**), both reds `wrong verdict is NOT the intended one`,
# and the redirected pin counted **once** as its own `ok - …` line in a clean
# run of that tree (**280/0**) — a real assertion, so the redirect tests the
# pin and not a duplicate. This reading is the one that pays for M23/M24: with
# a whole-pair borrow the two halves always redden together, so a loose pin was
# invisible; now that M23 reddens a DIAGNOSIS and leaves the ACTION green while
# M24 reddens an ACTION and leaves the DIAGNOSIS green, the pin has to be a
# FAIL-line grep on exactly that assertion or the battery would report the
# separation it does not have.
#
# Read a ninth time for M25/M26 (queue item (w), 2026-10-06): the two
# pins redirected the same way — M25's `err_int → default arm action points at
# the checker's own output` (double-quoted in the call, because the assertion
# name carries an apostrophe) and M26's `err_int → does not declare the egress
# untrustworthy` → `no drift → nothing appended to ALERTS`, an assertion both
# defects leave green while it still prints its own `ok - …` line), in a fake
# tree (`tests/` + `tools` copied so `REPO=` resolves there — the WHOLE
# `tools/` directory, the mistake the eighth reading corrected rather than a
# formatting nit) → **383 passed / 2 failed, rc 1** (385 total under
# `IPDRIFT_NO_LIVE=1`, **386 passed / 2 failed** (388 total) without it), both
# reds `wrong verdict is NOT the intended one`, and the redirected pin counted
# **once** as its own `ok - …` line in a clean run of that tree (**280/0**) — a
# real assertion, so the redirect tests the pin and not a duplicate. This
# reading pays for M25/M26 specifically because BOTH mutants live in the
# three-scenario loop: a mutant whose run carries 17 reds (M25) or 6 (M26) can
# hide a loose pin behind sheer red volume, and the redirected pin is the only
# shape that shows whether the FAIL-line grep is pointed at the right
# assertion rather than at a busy one.
#
# Read a tenth time for M27/M28 (queue item (x), 2026-10-06): the two
# remaining `case`-exchange pins redirected the same way — M27's `err_dns →
# does not borrow the default arm's action` and M28's `err_no_a → does not
# borrow the default arm's action` (both double-quoted in the call, because
# each assertion name carries an apostrophe) → `no drift → nothing appended
# to ALERTS`, an assertion both defects leave green while it still prints its
# own `ok - …` line — in a fake tree (`tests/` + the WHOLE `tools/` directory
# copied so `REPO=` resolves there) → **391 passed / 2 failed, rc 1** (393
# total under `IPDRIFT_NO_LIVE=1`, **394 passed / 2 failed** without it, i.e.
# 396 total), both reds `wrong verdict is NOT the intended one`, and the
# redirected pin counted **once** as its own `ok - …` line in a clean run of
# that tree (**280 / 0** with `IPDRIFT_NO_LIVE=1`, **283 / 0** without it) —
# a real assertion, so the redirect tests the pin and not a duplicate. This
# reading pays for M27/M28 for the opposite reason to the ninth: those two
# are the widest needles in the battery (9 and 12 lines) and each reddens 17
# assertions, so a pin could be riding on red volume alone — the redirect is
# the only shape that shows the FAIL-line grep is pointed at exactly the
# assertion the exchange names rather than at any of the sixteen others.
$ cd /data/repo && grep -n "ip-drift-cron" tools/REGISTRY.md | head; echo "=== registry entry"; grep -n "test_ip_drift_cron\|M1–M30\|404\|30/30" tools/REGISTRY.md | head -40
829:**Purpose**: Compare our egress public IPv4 address with the DNS A record(s) to detect drift (read-only — never edits DNS; the weekly `ip-drift-cron` only alerts, a VPS IP change needs sign-off).
859:**Evidence rule (why `1` is hard to reach by accident)**: a drift verdict needs **two validated IPv4 literals** — the egress answer and a `dig` answer line. An HTML/rate-limit body, an empty body, an IPv6 answer (not comparable to A), a CNAME/hostname line and a resolver that never completed a query are *errors*, not votes: they exit `3` with `drift: null` and can never produce `drift: true`. A bad answer from one service also never aborts the check — the next service is tried. **CGNAT/private IPv4 egress is deliberately still a verdict** (`100.64.0.0/10`, RFC1918): that address *is* the tunnel-down signal `ip-drift-cron` classifies.
881:**Use case**: Weekly cron (see `ip-drift-cron`) to detect that our egress no longer matches DNS — most commonly a WireGuard tunnel drop. Part of the agent's weekly IP drift duty per investor directive. Detection only; changing DNS is a separate, deliberate step.
936:- `tools/ip-drift-cron` deliberately does **NOT** call this (detect+alert only, since 2026-09-23).
952:## ip-drift-cron
956:**Location**: `/data/repo/tools/ip-drift-cron`
961:ip-drift-cron [--help] [domain]
964:0 3 * * 0 /data/repo/tools/ip-drift-cron gladex.de
1062:  swap** planted on `tools/ip-drift-cron` and replayed through this suite's own `run_cron`
1113:  writer `ip-drift-cron` alone (no reader exists to sanction), (C4) neither
=== registry entry
1055:- `bash tests/test_ip_drift_cron.sh` → **283 assertions** (measured 2026-10-05; was **224**
1171:  tests/test_ip_drift_cron.sh` rewrites only the two hardcoded path literals into
1174:- `bash tests/test_ip_drift_cron.sh --mutations` — mutation battery, **M1–M30** (each
1176:  verdict, with a clean control); **404 assertions** measured 2026-10-06 (the
1184:  `[0.4.230]`, and **396 → 404** with
1187:  the measured figure and not the chain's arithmetic; **30/30 mutants caught,
1588:  2 failed** without it, i.e. 404 total), again both reds `wrong verdict is
1659:  on PATH simulates HTTP 200/404/500/000 and content variants — no network
1662:  (dev/prod defaults, custom port), failure modes (HTTP 404/500/000, missing
1929:  reader — `tests/test_ip_drift_cron.sh` section 7 measured the only non-comment
1987:  that plant ran this suite **471/0 green** while `tests/test_ip_drift_cron.sh`
2007:  `tests/test_ip_drift_cron.sh` **224 → 222 / 2**, which has had the writer-side
3820:- Live (measured 2026-10-04): `./tools/regression-run` → **90 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.)
5589:  `POST /api/assets`: **401 proves the route exists, 404 proves the route
> build · mimo-v2.6-flash-free
$ cd /data/repo && sed -n '1168,1215p' tools/REGISTRY.md
`public` `else`, so no new mutant was added *with that block* — the class arms got their
  own mutants later, **M9**/**M10** below (`[0.4.221]`).
- **Pre-fix replay**: `IPDRIFT_CRON=<pre-fix blob> IPDRIFT_CRON_LEGACY=1 bash
  tests/test_ip_drift_cron.sh` rewrites only the two hardcoded path literals into
  the sandbox (the pre-fix cron has no hooks) → the suite **refuses to run
  (exit 2)** without that flag instead of appending to the real alert log.
- `bash tests/test_ip_drift_cron.sh --mutations` — mutation battery, **M1–M30** (each
  precondition-asserted to occur exactly once, must RUN and give the wrong
  verdict, with a clean control); **404 assertions** measured 2026-10-06 (the
  battery counts the suite's own assertions plus its control, so it moves with
  the suite: 194 → 206 with `[0.4.214]`, 206 → 239 with `[0.4.215]`, 239 → 316
  with `[0.4.220]`, **316 → 324** with `[0.4.221]`, **324 → 332** with
  `[0.4.222]`, **332 → 340** with `[0.4.223]`, **340 → 348** with
  `[0.4.224]`, **348 → 356** with `[0.4.225]`, **356 → 364** with
  `[0.4.226]`, **364 → 372** with `[0.4.227]`, **372 → 380** with
  `[0.4.228]`, **380 → 388** with `[0.4.229]`, **388 → 396** with
  `[0.4.230]`, and **396 → 404** with
  `[0.4.231]` — the 239 was not refreshed
  when `[0.4.216]` … `[0.4.219]` each moved the suite, so this line now carries
  the measured figure and not the chain's arithmetic; **30/30 mutants caught,
  0 survived**). **M9** = the
  `private-or-cgnat` arm quoting the public class's
  diagnosis (its own `class=` token contradicted by the sentence under it) and
  **M10** = the public and tunnel arms exchanging their diagnosis bodies — both
  are the drift-side (`exit 1`) twins of **M7**/**M8**, which guard the `exit 3`
  `case` arms; each is pinned to the assertion that the defect reddens
  (`drift_cgnat → does not borrow the public class's diagnosis` and
  `drift_pub → own diagnosis present (the four absences read a real log)`).
  **M11** = that same `private-or-cgnat` arm quoting the public class's
  `ACTION` (pinned to `drift_cgnat → does not borrow the public class's action`)
  and **M12** = the public and tunnel arms exchanging their `ACTION` bodies
  (pinned to `drift_pub → own action present (the class-internal absences read
  a real log)`) — the ACTION half of the pair, which control30's header comment
  recorded as reddened by *nobody at all* before these two existed; measured on
  their probes (2026-10-05, `/tmp/opencode/probe32/`) they redden **4** and
  **8** assertions respectively against the control's **280 / 0**. **M13** =
  the THIRD class arm's turn (queue item (q), 2026-10-05): the `unparseable`
  arm quoting the public class's `ACTION` — it orders the operator to verify
  the VPS IP while its own `class=unparseable` token says the address did not
  parse, the M9 shape on the third arm, where **M6** only ever made that arm
  *unreachable* — pinned to `drift_unparse → does not borrow the public class's
  action`; and **M14** = the unparseable and public arms exchanging their
  `ACTION` bodies over the same `if/elif/else` span (tunnel arm untouched),
  pinned to `drift_unparse → own action present (the class-internal absences
  read a real log)`. Probe (2026-10-05, `/tmp/opencode/probe33/`, built BEFORE
  the `M{}` dict entries existed): each needle counted exactly once in the
  tool, both copies `bash -n` clean, **M13 → 275 passed / 5 failed, rc 1** and
  **M14 → 271 passed / 9 failed, rc 1** against the control **280 / 0** —
> build · mimo-v2.6-flash-free

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

[Tue Oct  6 06:03:07 2026] 127.0.0.1:50290 Accepted
[Tue Oct  6 06:03:07 2026] 127.0.0.1:50290 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Oct  6 06:03:07 2026] 127.0.0.1:50290 Closing
[Tue Oct  6 06:03:08 2026] 127.0.0.1:50306 Accepted
[Tue Oct  6 06:03:08 2026] 127.0.0.1:50306 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Oct  6 06:03:08 2026] 127.0.0.1:50306 Closing
[Tue Oct  6 06:06:08 2026] 127.0.0.1:58378 Accepted
[Tue Oct  6 06:06:08 2026] 127.0.0.1:58378 Closing
[Tue Oct  6 06:06:09 2026] 127.0.0.1:58386 Accepted
[Tue Oct  6 06:06:09 2026] 127.0.0.1:58386 Closing
[Tue Oct  6 06:06:10 2026] 127.0.0.1:58390 Accepted
[Tue Oct  6 06:06:10 2026] 127.0.0.1:58390 Closing
[Tue Oct  6 06:08:30 2026] 127.0.0.1:34146 Accepted
[Tue Oct  6 06:08:30 2026] 127.0.0.1:34146 Closing
[Tue Oct  6 06:08:30 2026] 127.0.0.1:34148 Accepted
[Tue Oct  6 06:08:30 2026] 127.0.0.1:34148 Closing
[Tue Oct  6 06:15:09 2026] 127.0.0.1:41840 Accepted
[Tue Oct  6 06:15:09 2026] 127.0.0.1:41840 Closing
[Tue Oct  6 06:15:09 2026] 127.0.0.1:41850 Accepted
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41850 Closing
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41866 Accepted
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41866 Closing
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41876 Accepted
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41876 Closing
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41886 Accepted
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41886 Closing
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41896 Accepted
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41896 Closing
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41908 Accepted
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41908 Closing
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41924 Accepted
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41924 Closing
[Tue Oct  6 06:15:10 2026] 127.0.0.1:41934 Accepted
[Tue Oct  6 06:15:11 2026] 127.0.0.1:41934 Closing
[Tue Oct  6 06:15:11 2026] 127.0.0.1:41940 Accepted
[Tue Oct  6 06:15:11 2026] 127.0.0.1:41940 Closing
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38286 Accepted
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38286 Closing
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38298 Accepted
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38298 Closing
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38300 Accepted
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38300 Closing
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38302 Accepted
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38302 Closing
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38310 Accepted
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38310 Closing
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38324 Accepted
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38324 Closing
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38332 Accepted
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38332 Closing
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38340 Accepted
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38340 Closing
[Tue Oct  6 06:15:58 2026] 127.0.0.1:38344 Accepted
[Tue Oct  6 06:15:59 2026] 127.0.0.1:38344 Closing
[Tue Oct  6 06:15:59 2026] 127.0.0.1:38356 Accepted
[Tue Oct  6 06:15:59 2026] 127.0.0.1:38356 Closing
[Tue Oct  6 06:23:47 2026] 127.0.0.1:45826 Accepted
[Tue Oct  6 06:23:47 2026] 127.0.0.1:45826 Closing
[Tue Oct  6 06:23:49 2026] 127.0.0.1:45836 Accepted