Gladex Agent Logs

-- `bash tests/test_ip_drift_cron.sh` → **93 assertions**, hermetic: a scenario-driven
+- `bash tests/test_ip_drift_cron.sh` → **103 assertions** (measured 2026-10-04; was **93**
+  before `[0.4.206]` added section **7, the channel sweep**), hermetic: a scenario-driven
   `ip-drift-check` **stub** (`ok` / `drift_pub` / `drift_cgnat` / `err_no_a` /
   `err_dns` / `err_ip` / `err_int` / `garbage` / `empty` / `rc2` / `rc99`) plus
   `IPDRIFT_LOG_DIR` sandboxing — no network is touched and **the real
   `/data/agent-logs/ip-drift-ALERTS.log` is asserted byte-for-byte untouched** at

> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -1050,8 +1050,24 @@
   errors never reported as DRIFT and vice versa), append-only alerting across
   runs, the hooks, static no-DNS-write guards (write subcommands only — the error
   path *names* `pdns-api.py records` as the human's next step) and the REGISTRY
   contract, plus one guarded live case.
+- **Section 7, the channel sweep** (`[0.4.206]`, the generalisation of
+  `tests/test_red_watch.sh` G28–G34 to this writer's two channels): an inline
+  `ipchan_scan <dir> <files|guard|names>` reader asserts that (C1) the only
+  `tests/` file naming a live `/data/agent-logs/ip-drift*` channel is this suite
+  itself, (C2) every such line there rides the `REAL_ALERT*` write-guard rather
+  than taking a verdict off a live channel, (C3) `tools/` is set-equality on the
+  writer `ip-drift-cron` alone (no reader exists to sanction), (C4) neither
+  writer source carries a `want=`, and (C5) a real drift run's channel text
+  exists and holds neither `want=` nor a whole-line healthy verdict. Comments are
+  skipped and single-quoted segments stripped first (a single-quoted path here is
+  a needle, not an open), `*.md` is excluded by extension, and **C6–C8 are a
+  five-twin plant** (open / needle / comment / guarded / unguarded) that keeps the
+  classifier itself honest: both real-tree set expectations are non-empty, so a
+  scanner that stopped reading reddens instead of passing on `""`. Measured with
+  plants: `tests/zz-plant.sh` → C1+C2 red (101/2), `tools/zz-plant` → C3 red
+  (102/1), both removed → **103/0**.
 - **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.

> build · mimo-v2.6-flash-free
Now the changelog entry:
$ cd /data/repo && cat >> CHANGELOG.md <<'ENTRY'

## [0.4.206] - 2026-10-04 — the sweep `[0.4.205]` queued as candidate (c): the box's other scheduled writer gets the same reader, and the measurement behind the decision is written down instead of remembered (`tests/test_ip_drift_cron.sh` section 7, 93 → 103)

### Added
- **Section 7, the channel sweep, in `tests/test_ip_drift_cron.sh`** — the generalisation `[0.4.205]`'s closing bullet queued as (c): *"`tools/ip-drift-cron` also appends an alerts log and a dated log, so measure first (`grep -rn "want=" tests tools` over its channels) whether any suite reads them, and only then decide whether it needs the same reader."* Measured first, decided second, wrote the decision down third — in that order.
- **The measurement, taken on the live tree this run.** `want=` is **0** in `tools/ip-drift-cron`, **0** in `tools/ip-drift-check` and **0** across all four live dated logs (2026-09-23 / 09-24 / 09-27 / 10-04), so this writer carries no expectation a grep could satisfy itself with — unlike `red-watch`'s state file, there was **nothing to strip**. The only non-comment code naming a live `ip-drift` channel anywhere in `tests/` is this suite's own write-guard: the `REAL_ALERTS=` snapshot and the before/after *"never written"* delta, which reads line COUNTS to prove the suite did not write — it never derives a verdict from content. `tools/` is set-equality on `ip-drift-cron` alone: `system-status` and `red-watch` consume no ip-drift output at all. So unlike `[0.4.204]` there was no reader to sanction and no needle to drop — the honest decision is **no strip, one guard**.
- **The reader.** An inline `ipchan_scan <dir> <files|guard|names>` (comments skipped, single-quoted segments stripped first — a single-quoted path in this tree is a needle grepped against another file's source — `*.md` excluded by extension) enforces: **C1** the only `tests/` file naming a live channel is this write-guard suite (set equality, so a second opener is *named*, not just counted); **C2** every such line inside it rides the `REAL_ALERT*` guard, so a verdict taken off a live channel reports its line; **C3** `tools/` allows exactly the writer, making a future sanctioned reader a deliberate edit rather than an accident; **C4** neither writer source carries a `want=`; **C5** a real drift run's channel text exists and holds neither `want=` nor a whole-line healthy verdict. Anti-vacuity is the **five-twin plant** (open / single-quoted needle / comment / guarded / unguarded) behind **C6–C8**, and both real-tree set expectations are non-empty, so a scanner that stopped reading reddens instead of passing on an empty string.

### Tests
- **`tests/test_ip_drift_cron.sh` → 103 passed / 0 failed** (93 → 103, the ten new `C*` assertions); **`--mutations` → 124 / 0** (114 → 124), all five mutants still caught and still landing on their intended assertion, the mutation control still green with the new section running under it.
- **Both plants measured, never predicted**: `tests/zz-plant.sh` (a literal live-channel open) → **101 passed / 2 failed**, C1 reporting `test_ip_drift_cron.sh` + `zz-plant.sh` and C2 naming `zz-plant.sh:1`; `tools/zz-plant` → **102 / 1 failed** with C3 reporting `ip-drift-cron zz-plant`; both files removed → **103 / 0** again, tree left exactly as found.

### Notes
- **Scope**: `tests/test_ip_drift_cron.sh` (section 7), `tools/REGISTRY.md` (suite figure 93 → 103, dated, plus the section-7 bullet), this entry. **No `app/src/php` file touched → no reviewer gate, no promote** (dev and prod both stay `0.4.28`); **no suite added or removed** (`- Live:` stays **89**, so no figure refresh is owed); **zero DNS writes, no mail sent, no unit restarted, no `systemctl reset-failed`**, `crontab -l` untouched; spend **0.00** of the 5.00 October allowance, free `*-free` models only, no key configured, no secret or PII in any prompt or commit.
- **Not this step**: the three `identity-run@{jonas,lena,leon}` units stay red on purpose as `(r1)`'s production evidence until their timers fire **Mon 08:06+ CEST**, so candidate (b) of `[0.4.204]`'s queue is still not actionable; `(93)`/`(97)(a)` (the Marco Steiner hire) still waits on an answer that was **0 unread** at this run's start; the standing `SOA:gladex.de … mname=placeholder (NEEDS-INVESTOR open)` row is the investor's item, untouched.

### Queue
Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the `Next-candidate queued, not actioned` bullet of the newest run entry — it is not duplicated here, and has not been since `[0.4.67]`. To read the live queue, open `PROGRESS.md`; to know whether that is still true, run `tools/queue-source-check`.
ENTRY
grep -c "^## \[" CHANGELOG.md; grep -n "^## \[0.4.206\]" CHANGELOG.md; awk '/^## \[0.4.206\]/{f=1} f' CHANGELOG.md | awk '{for(i=1;i<=NF;i++) if(length($i)>m) m=length($i)} END{print "longest token:", m}'
211
7705:## [0.4.206] - 2026-10-04 — the sweep `[0.4.205]` queued as candidate (c): the box's other scheduled writer gets the same reader, and the measurement behind the decision is written down instead of remembered (`tests/test_ip_drift_cron.sh` section 7, 93 → 103)
longest token: 32
> build · mimo-v2.6-flash-free
$ cd /data/repo && { echo "### changelog_api"; timeout 300 php tests/test_changelog_api.php 2>&1 | tail -3; echo "### changelog_mobile"; timeout 300 php tests/test_changelog_mobile.php 2>&1 | tail -3; echo "### queue_source"; timeout 600 bash tests/test_queue_source.sh 2>&1 | tail -3; echo "### repo_lint"; timeout 600 ./tools/repo-lint 2>&1 | tail -4; echo "### inbox"; ./tools/inbox-status 2>&1 | tail -3; } > /tmp/opencode/run1.log 2>&1; cat /tmp/opencode/run1.log
### changelog_api
  PASS: a heading the API cannot parse is reported as unparseable, not counted as an entry

=== Results: 86 passed, 0 failed ===
### changelog_mobile
  PASS: the prod environment answered /changelog (this section cannot skip everything)

=== Results: 125 passed, 0 failed, 0 skipped ===
### queue_source
===============================
queue-source-check suite: 278 passed, 0 failed
===============================
### repo_lint
  skipped:  binary=2  empty=6  no_shebang=4  unsupported_ext=99
  go-compile: 45 module file(s) compile clean (1.763s)
  changelog-version: 210 changelog version heading(s), 210 unique, 6212 citation(s) checked, 0 missing, 5874 bare token(s) counted
result: all 185 linted file(s) parse clean (exit 0)
### inbox
  INBOX.md        : 79 entries, 79 handled, 0 open

verdict: OK - nothing owed (0 unread, 0 open entries all replied)
> build · mimo-v2.6-flash-free
$ cd /data/repo && { echo "### registry_coverage"; timeout 900 bash tests/test_registry_coverage.sh 2>&1 | tail -4; echo "### monitor"; timeout 300 bash tests/test_gladex_monitor.sh 2>&1 | tail -30; } > /tmp/opencode/run2.log 2>&1; echo done
Command moved to the background (shell ID: sh_108c82cef0017XSGnhL9D1460c).
Output is streaming to: /root/.local/share/opencode/shell/fa3e85b2145a60c127b5c9261e76a7ba6d520299/sh_108c82cef0017XSGnhL9D1460c.out
> build · mimo-v2.6-flash-free
$ cd /data/repo && for t in test_red_watch.sh test_ip_drift_check.sh; do echo "### $t"; timeout 300 bash tests/$t 2>&1 | tail -2; done; echo "### test_ip_drift_safety.php"; timeout 300 php tests/test_ip_drift_safety.php 2>&1 | tail -2; echo "### budget"; ./tools/budget-show | tail -5; echo "### health"; ./tools/healthcheck >/dev/null 2>&1; echo "healthcheck rc=$?"
### test_red_watch.sh

=== Results: 196 passed, 0 failed ===
### test_ip_drift_check.sh

=== Results: 136 passed, 0 failed ===
### test_ip_drift_safety.php

=== Results: 16 passed, 0 failed ===
### budget
  - 2026-09-20: investor APPROVED gladex.de (1.50/mo). Awaiting registrar purchase + DNS creds.
  - 2026-09-20: purchase completed same day — RDAP status active (changed 2026-09-20T11:10:57+02:00), DNS wired via pdns wrapper (A apex/dev/git/info/stats/log/team -> 77.90.15.49, MX 10 gladex.de), dig-verified; DOMAIN.md holds evidence.
  - 2026-09-24: ledger narrative corrected — spent-line still said "purchase pending at registrar" 4 days after registration (queued candidate #1); numbers unchanged (1.50/3.50, no money moved), log history above kept verbatim.
  - 2026-10-01: month rolled per brief §4 (balance resets to 5.00 on the 1st, unspent does NOT roll over). September history above is kept verbatim; September closed at spent 1.50 / remaining 3.50.
  - 2026-10-02: October opened at spent 0.00 / remaining 5.00 because no October charge exists in any file on this box — while gladex.de is a known 1.50/mo recurring cost with NO renewal date recorded anywhere. Figure to be corrected the moment the investor answers REPORT.md §14.
### health
healthcheck rc=0
> build · mimo-v2.6-flash-free
$ cd /data/repo && echo "=== git status ==="; git status --porcelain; echo "=== crontab ==="; crontab -l; echo "=== system-status ip-drift row? ==="; grep -c "ip-drift" tools/system-status; echo "=== date ==="; date -u +%Y-%m-%dT%H:%MZ; echo "=== STEP 0 re-read ==="; sqlite3 /opt/startup/dev/data/messages.db "SELECT count(*) FROM messages WHERE direction='investor_to_agent' AND read=0;"; sqlite3 /opt/startup/prod/data/messages.db "SELECT count(*) FROM messages WHERE direction='investor_to_agent' AND read=0;"
=== git status ===
 M CHANGELOG.md
 M tests/test_ip_drift_cron.sh
 M tools/REGISTRY.md
=== crontab ===
0 3 * * 0 /data/repo/tools/ip-drift-cron gladex.de
*/15 * * * * /data/repo/tools/red-watch >> /data/agent-logs/red-watch-cron.log 2>&1
=== system-status ip-drift row? ===
0
=== date ===
2026-10-04T21:19Z
=== STEP 0 re-read ===
0
0
> build · mimo-v2.6-flash-free
$ cd /data/repo && ./tools/queue-source-check; echo "rc=$?"
queue-source-check: FAIL - 1 violation(s): [0.4.206] is not named in agent-logs/PROGRESS.md - the newest CHANGELOG entry has no record in the authoritative file
  - [0.4.206] is not named in agent-logs/PROGRESS.md - the newest CHANGELOG entry has no record in the authoritative file
rc=1
> build · mimo-v2.6-flash-free
← Write /tmp/opencode/entry-draft.md
Created file successfully: /tmp/opencode/entry-draft.md
> build · mimo-v2.6-flash-free
← Edit /tmp/opencode/entry-draft.md
Index: /tmp/opencode/entry-draft.md
===================================================================
--- /tmp/opencode/entry-draft.md
+++ /tmp/opencode/entry-draft.md
@@ -7,9 +7,9 @@
 
 - **Measured first — the decision belongs to the measurement, not to me.** Six readings taken before a line of code was written: `grep -c want=` → **0** in `tools/ip-drift-cron`, **0** in `tools/ip-drift-check`, **0** in all four live dated logs (`ip-drift-20260923/20260924/20260927/20261004.log`) — this writer carries no expectation a grep could satisfy itself with, so unlike `red-watch`'s state file there is **nothing to strip**. The only non-comment code naming a live `/data/agent-logs/ip-drift*` channel anywhere in `tests/` is **this suite's own write-guard**: the `REAL_ALERTS=` snapshot and the before/after *"never written"* delta — which compares line COUNTS to prove the suite did not write, and never reads content for a verdict. `tools/` is set-equality on **`ip-drift-cron` alone**: `grep -c "ip-drift" tools/system-status` → **0**, and `red-watch`'s single hit is a docstring sentence with no live path, so neither consumes ip-drift output. The live `ip-drift-ALERTS.log` **does not exist** (no drift has ever fired) and no live channel carries the monitor's healthy line. `crontab -l` holds exactly two writers — `ip-drift-cron` (Sundays 03:00) and `red-watch` (`*/15`) — so with this step **both scheduled writers have a reader** and (c) is closed, not half-done.
 - **Decision: no strip, one guard.** `[0.4.204]` needed a strip because a needle really was reaching greppable output; here the honest generalisation is the thing that keeps this run's measurement true for suites written later — a reader that reddens the moment somebody opens the channel, rather than a sentence recorded once in a commit message.
 - **The reader, `tests/test_ip_drift_cron.sh` section 7.** Inline `ipchan_scan <dir> <files|guard|names>` (python3 heredoc; comments skipped and **single-quoted segments stripped first**, because a single-quoted path in this tree is a needle grepped against another file's source; `*.md` excluded by extension, `__pycache__` skipped): **C1** the only `tests/` file naming a live channel is this write-guard suite — set equality, so a second opener is *named*; **C2** every live-channel line inside it must ride `REAL_ALERT*`, so a verdict taken off a live channel reports its own `file:line`; **C3** `tools/` allows exactly the writer, making a future sanctioned reader a deliberate edit (the same shape as `[0.4.205]`'s `red-watch system-status` set); **C4** `cat $CRON $REAL_CHECK | grep -c 'want='` → **0**; **C5** a real drift run's channel text exists (`C5a`) and holds neither `want=` (`C5b`) nor `Overall: ALL SYSTEMS HEALTHY` (`C5c`). Anti-vacuity is a **five-twin plant** — open / single-quoted needle / comment / guarded / unguarded — behind **C6–C8**, plus the fact that both real-tree set expectations are **non-empty**: a scanner that stopped reading reddens C1 and C3, it cannot pass on `""`.
-- **Measured after, never predicted.** `bash tests/test_ip_drift_cron.sh` → **103 passed / 0 failed** (93 → 103); `--mutations` → **124 / 0** (114 → 124), all five mutants still caught and still landing on their intended assertion with the new section running under the control. **Both plants run against the real trees**: `tests/zz-plant.sh` (literal live-channel open) → **101 passed / 2 failed** — C1 reports `test_ip_drift_cron.sh` + `zz-plant.sh`, C2 reports `zz-plant.sh:1` — and `tools/zz-plant` → **102 / 1 failed** — C3 reports `ip-drift-cron zz-plant`; each file removed → **103 / 0** again, `git status --porcelain` showing only this run's files at every point. Neighbours re-read: `test_red_watch.sh` **196/0** (its own G28–G34 unaffected — the new lines carry no red-watch token outside comments), `test_ip_drift_check.sh` **136/0**, `test_ip_drift_safety.php` **16/0**, `test_changelog_api.php` **86/0**, `test_changelog_mobile.php **125/0** (the new entry's longest prose token measured **32**, far under the 76 ceiling), `test_queue_source.sh` **278/0**, `./tools/repo-lint` **exit 0** on HEAD (`all 185 linted file(s) parse clean`, 210 version headings / 6212 citations / 0 missing — the pre-entry tree; the index-tree read happens at commit time), `./tools/inbox-status` **exit 0**, `./tools/healthcheck` **exit 0**, `./tools/budget-show` **exit 0** (month 2026-10, spent **0.00 €** / remaining **5.00 €**).
+- **Measured after, never predicted.** `bash tests/test_ip_drift_cron.sh` → **103 passed / 0 failed** (93 → 103); `--mutations` → **124 / 0** (114 → 124), all five mutants still caught and still landing on their intended assertion with the new section running under the control. **Both plants run against the real trees**: `tests/zz-plant.sh` (literal live-channel open) → **101 passed / 2 failed** — C1 reports `test_ip_drift_cron.sh` + `zz-plant.sh`, C2 reports `zz-plant.sh:1` — and `tools/zz-plant` → **102 / 1 failed** — C3 reports `ip-drift-cron zz-plant`; each file removed → **103 / 0** again, `git status --porcelain` showing only this run's files at every point. Neighbours re-read: `test_red_watch.sh` **196/0** (its own G28–G34 unaffected — the new lines carry no red-watch token outside comments), `test_ip_drift_check.sh` **136/0**, `test_ip_drift_safety.php` **16/0**, `test_changelog_api.php` **86/0**, `test_changelog_mobile.php` **125/0** (the new entry's longest prose token measured **32**, far under the 76 ceiling), `test_queue_source.sh` **278/0**, `./tools/repo-lint` **exit 0** on HEAD (`all 185 linted file(s) parse clean`, 210 version headings / 6212 citations / 0 missing — the pre-entry tree; the index-tree read happens at commit time), `./tools/inbox-status` **exit 0**, `./tools/healthcheck` **exit 0**, `./tools/budget-show` **exit 0** (month 2026-10, spent **0.00 €** / remaining **5.00 €**).
 - **The one red this entry owns, cleared by this entry:** `./tools/queue-source-check` → **exit 1**, exactly one violation — *`[0.4.206]` is not named in `agent-logs/PROGRESS.md`* — rule 8 by construction; appending this is what turns it green (re-read below).
 <!-- MONITOR_ATTRIBUTION -->
 - **Disclosures (shared tree, swept nothing).** `git status --porcelain` at write time shows exactly this run's **4 files** (`tests/test_ip_drift_cron.sh`, `tools/REGISTRY.md`, `CHANGELOG.md`, `agent-logs/PROGRESS.md`), nothing staged by another desk; `tools/REGISTRY.md` carries only this run's edits (suite figure **93 → 103** dated 2026-10-04, plus the section-7 bullet). No `app/src/php` file touched → **no reviewer gate, no promote** (dev and prod both stay **0.4.28**); **no suite added or removed** (`- Live:` stays **89**, so no figure refresh is owed); **zero DNS writes, no mail sent, no unit restarted, no `systemctl reset-failed`**, `crontab -l` untouched (2 lines); spend **0.00** of the 5.00 October allowance, free `*-free` models only, no key configured, no secret or PII in any prompt or commit.
 

> build · mimo-v2.6-flash-free
$ cd /data/repo && ./tools/system-status 2>&1 | tail -25; echo "rc=${PIPESTATUS[0]}"
page-info                 [OK] 200
  page-stats                [OK] 200
  page-team                 [OK] 200
  cloud                     [OK] nextcloud 200 installed=true; immich 200 pong; 5/5 containers up
  DNS:gladex.de             [OK] 77.90.15.49 on 1.1.1.1+8.8.8.8
  DNS:dev.gladex.de         [OK] 77.90.15.49 on 1.1.1.1+8.8.8.8
  DNS:git.gladex.de         [OK] 77.90.15.49 on 1.1.1.1+8.8.8.8
  DNS:info.gladex.de        [OK] 77.90.15.49 on 1.1.1.1+8.8.8.8
  DNS:stats.gladex.de       [OK] 77.90.15.49 on 1.1.1.1+8.8.8.8
  DNS:team.gladex.de        [OK] 77.90.15.49 on 1.1.1.1+8.8.8.8
  DNS:log.gladex.de         [OK] 77.90.15.49 on 1.1.1.1+8.8.8.8
  MX:gladex.de              [OK] 10 gladex.de. on 1.1.1.1+8.8.8.8
  SOA:gladex.de             [WARN] serial=2026092602 consistent on 1.1.1.1+8.8.8.8; mname=placeholder (NEEDS-INVESTOR open)
  tls-cert-expiry           [OK] 78d left
  tls-cert-expiry-photos    [OK] 81d left
  investor-messages         [OK] 0 unread dev=0 prod=0
  investor-duty             [OK] owed=0 unread=0 unreplied=0 open=0
  git-tree                  [WARN] 3 uncommitted changes
  red-watch                 [WARN] red, failed=8, since 2026-10-04T16:16:44Z, 6m old; FAIL A3 tree clean AND in sync with origin/main (kind=is key=git) ;; FAIL A12 system-status exits 0 (kind=rc key=sys) ;; FAIL A13 overall healthy (kind=line key=sys) ;; FAIL A15 git-tree reports a clean tree (kind=contains key=sys) ;; FAIL A16 system-status json exits 0 (kind=rc key=sysj) ;; FAIL A17 json channel says overall ok (kind=contains key=sysj) ;; FAIL A18 json channel says zero errors (k
  queue-source              [FAIL] 1 violation(s): [0.4.206] is not named in agent-logs/PROGRESS.md - the newest CHANGELOG entry has no record in the authoritative file
  go-tests                  [OK] passing (worktree)
  go-compile                [OK] 45 module file(s) compile clean (2.017s) (commit a97196a)
  promote-gates             [OK] promote-ready: verdict, dev-sync, commit-lint and ship-tree all pass (commit a97196a)

Overall: 2 CHECK(S) FAILED
rc=1
> build · mimo-v2.6-flash-free
$ cd /data/repo && ./tools/system-status 2>&1 | grep -E "failed-units|Overall|git-tree|queue-source" ; echo "rc=${PIPESTATUS[0]}"
failed-units              [FAIL] 3 failed: identity-run@jonas.service rc=1 shift_exit=1, identity-run@lena.service rc=1 shift_exit=1, identity-run@leon.service rc=1 shift_exit=1
  git-tree                  [WARN] 3 uncommitted changes
  red-watch                 [WARN] red, failed=8, since 2026-10-04T16:16:44Z, 7m old; FAIL A3 tree clean AND in sync with origin/main (kind=is key=git) ;; FAIL A12 system-status exits 0 (kind=rc key=sys) ;; FAIL A13 overall healthy (kind=line key=sys) ;; FAIL A15 git-tree reports a clean tree (kind=contains key=sys) ;; FAIL A16 system-status json exits 0 (kind=rc key=sysj) ;; FAIL A17 json channel says overall ok (kind=contains key=sysj) ;; FAIL A18 json channel says zero errors (k
  queue-source              [FAIL] 1 violation(s): [0.4.206] is not named in agent-logs/PROGRESS.md - the newest CHANGELOG entry has no record in the authoritative file
Overall: 2 CHECK(S) FAILED
rc=1
> build · mimo-v2.6-flash-free
Measurement phase complete; the reader is written and both plants measured. Waiting on the two heavy suites (registry coverage + monitor) that run in the background before I append the PROGRESS entry and commit.

State so far:
- **STEP 0**: 0 unread investor rows on both DBs, `inbox-status` exit 0, `INBOX.md` 79/79/0 — nothing owed.
- **Queue item (c) executed**: `tests/test_ip_drift_cron.sh` section 7 (`ipchan_scan`) — suite **93 → 103**, `--mutations` **114 → 124**, live plants red then restored (101/2 and 102/1 → 103/0).
- Measured first as ordered: `want=` = 0 in the writer, the checker and all four live logs; only live-channel code in `tests/` is this suite's own write-guard; `tools/` set = the writer alone; both `crontab` writers now have a reader.
- Files touched: `tests/test_ip_drift_cron.sh`, `tools/REGISTRY.md`, `CHANGELOG.md` (`[0.4.206]`) — no `app/src/php`, so no promote, spend 0.00.
exit=0

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

[Mon Oct  5 00:15:57 2026] 127.0.0.1:39136 Accepted
[Mon Oct  5 00:15:57 2026] 127.0.0.1:39136 Closing
[Mon Oct  5 00:15:57 2026] 127.0.0.1:39152 Accepted
[Mon Oct  5 00:15:57 2026] 127.0.0.1:39152 Closing
[Mon Oct  5 00:17:25 2026] 127.0.0.1:55770 Accepted
[Mon Oct  5 00:17:25 2026] 127.0.0.1:55770 Closed without sending a request; it was probably just an unused speculative preconnection
[Mon Oct  5 00:17:25 2026] 127.0.0.1:55770 Closing
[Mon Oct  5 00:17:26 2026] 127.0.0.1:55782 Accepted
[Mon Oct  5 00:17:26 2026] 127.0.0.1:55782 Closed without sending a request; it was probably just an unused speculative preconnection
[Mon Oct  5 00:17:26 2026] 127.0.0.1:55782 Closing
[Mon Oct  5 00:18:01 2026] 127.0.0.1:48382 Accepted
[Mon Oct  5 00:18:01 2026] 127.0.0.1:48382 Closed without sending a request; it was probably just an unused speculative preconnection
[Mon Oct  5 00:18:01 2026] 127.0.0.1:48382 Closing
[Mon Oct  5 00:18:03 2026] 127.0.0.1:48386 Accepted
[Mon Oct  5 00:18:03 2026] 127.0.0.1:48386 Closed without sending a request; it was probably just an unused speculative preconnection
[Mon Oct  5 00:18:03 2026] 127.0.0.1:48386 Closing
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49256 Accepted
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49256 Closing
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49270 Accepted
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49270 Closing
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49272 Accepted
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49272 Closing
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49276 Accepted
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49276 Closing
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49292 Accepted
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49292 Closing
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49298 Accepted
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49298 Closing
[Mon Oct  5 00:22:24 2026] 127.0.0.1:49306 Accepted
[Mon Oct  5 00:22:25 2026] 127.0.0.1:49306 Closing
[Mon Oct  5 00:22:25 2026] 127.0.0.1:58046 Accepted
[Mon Oct  5 00:22:25 2026] 127.0.0.1:58046 Closing
[Mon Oct  5 00:22:25 2026] 127.0.0.1:58056 Accepted
[Mon Oct  5 00:22:25 2026] 127.0.0.1:58056 Closing
[Mon Oct  5 00:22:25 2026] 127.0.0.1:58066 Accepted
[Mon Oct  5 00:22:25 2026] 127.0.0.1:58066 Closing
[Mon Oct  5 00:23:10 2026] 127.0.0.1:35146 Accepted
[Mon Oct  5 00:23:10 2026] 127.0.0.1:35146 Closing
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35158 Accepted
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35158 Closing
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35166 Accepted
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35166 Closing
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35168 Accepted
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35168 Closing
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35182 Accepted
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35182 Closing
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35188 Accepted
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35188 Closing
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35192 Accepted
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35192 Closing
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35208 Accepted
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35208 Closing
[Mon Oct  5 00:23:11 2026] 127.0.0.1:35218 Accepted
[Mon Oct  5 00:23:12 2026] 127.0.0.1:35218 Closing
[Mon Oct  5 00:23:12 2026] 127.0.0.1:35226 Accepted
[Mon Oct  5 00:23:12 2026] 127.0.0.1:35226 Closing
[Mon Oct  5 00:23:37 2026] 127.0.0.1:52958 Accepted
[Mon Oct  5 00:23:37 2026] 127.0.0.1:52958 Closing
[Mon Oct  5 00:23:37 2026] 127.0.0.1:52964 Accepted