Gladex Agent Logs

- **The judgment, disclosed the way (am) and (ap) disclosed theirs**: both shapes are planted anyway as MULTI-RED — M52 a nine-red, M53 a four-red — a deviation from this item's "each plant reddening exactly one assertion in THIS suite", recorded here rather than hidden, because both mutants are CAUGHT (neither stayed green) and each pin is a line no other plant in this battery can print: M52's names the UNCAUGHT-exception shape (every cron-side, count-side or label-side failure exits with its own `SystemExit` message instead), M53's names the PUBLIC class with the cgnat DIAGNOSIS body — and M51, the only other plant measured to redden `did not bite` (its own two reds, re-probed this run at **333 / 4**), reddens it on the private and unparseable rows carrying the ACTION body instead.
- **Collateral, the reader suite over all three trees** → **759 / 0, rc 0** each (these plants edit only this file, which that suite never reads this way).
- **Blindness, measured BEFORE the install** — `--mutations` over each planted tree (clean battery **556 / 0**, re-read off the committed suite): over M52's tree → **528 passed / 10 failed** (total **538** = 556 less the **18** rows the early `continue`s stop producing — 3 classes × 4 skipped step-3 rows plus 6 absence rows × 1 skipped else-branch, accounted not guessed), the ten reds being this file's own nine control30 rows (its body runs even under `--mutations`) plus the shared `control: unmutated cron already red (rc=1)` — and NOT ONE pin-check shadow, every existing `run_suite_plant` pin still landing over a control that is red elsewhere — and over M53's tree → **551 passed / 5 failed** (total **556**; a successful plant removes no row), the same five reds. `grep -cE 'M5[23]'` over each whole output → **0** on both trees.
- **What landed — ten new battery assertions, counted from the run and not projected**: two **five-argument** `run_suite_plant` calls (arity re-derived from the helper's definition rather than copied: both plant THIS suite), needles **built, never quoted whole** (the M14/M15 self-blindness rule — neither find is written out anywhere in the block): one shared head `$AQ_H` plus the first entry `$AQ_E`, so M52's find is M53's find minus that entry, and `$M53_C`/`$M53_R1`/`$M53_R2` carry the private line and the rewritten pair. Finds re-derived from the **installed** file's own bash definitions, evaluated by bash and never re-typed → **1 / 1** with both REPLs differing, `bash -n` → **OK**. The same battery after the block — `bash tests/test_ip_drift_cron.sh --mutations` → **`=== Results: 566 passed, 0 failed ===`, rc 0**, arithmetic taken after `=== Results:`: **556 + 10**, `grep -cE '^  ok   - M5[23]'` → **10** (5 + 5), `grep -c '  FAIL - '` → **0**; live-free battery **553 → 563 / 0** with the same `ok` count; the default run re-read after every edit → **340 / 0** plain and **337 / 0** live-free.
- **A wording fix caught by re-reading the measured output**: the block first said M53's pin was "the FIRST of the four" reds, but its own probe file prints private-or-cgnat's pair ahead of `public`'s — corrected to "the first of `public`'s two — the THIRD of the four as printed", and **all four runs re-taken afterwards on the final bytes**: **340 / 0** plain, **337 / 0** live-free, **566 / 0** battery plain, **563 / 0** battery live-free, `ok M5[23]` → **10** and `FAIL` → **0** in both.
- **Both new pins read the other way — teeth61, source-checked before the redirect was built** — `/tmp/opencode/probe61/teeth61.sh` (the script lives OUTSIDE the tree it wipes) checks the target **is an assertion in the source FIRST**: `assert_lacks "no drift → nothing appended to ALERTS"` at line **177**, line-start count **1** (the `^`-anchored count, not the raw one), raw **7** at redirect time; each pin's QUOTED argument count **1** and each BARE pin text **1** (the (aq) block quotes neither pin whole — M52's is cited only up to `the plant did not apply`, the traceback living only at the call, and M53's only as the class + `did not bite` fragments — the label + body triple living only at the call); no backslash in the target (a backslash is LITERAL under `grep -F`); `bash -n` OK after both. Redirected tree's clean run → **340 / 0, rc 0** with the target still printing its own `ok - …` line (four `no drift` rows print in every clean run — lines 176–179 — the target among them); battery in that tree → **564 passed / 2 failed, rc 1**, exactly two reds, both `wrong verdict is NOT the intended one (expected a failure of: 'no drift → nothing appended to ALERTS')` — one per new pin — and `grep -cE '^  ok   - M5[23]'` → **8**: the ten less the two redirected pin checks. The **twenty-third** reading quoting that target is appended to this suite's reading block (line-start count still **1**, raw **7 → 8**, bare **17 → 18**, `bash -n` OK), defaults still **340 / 0** afterwards.

### Notes
- **STEP 0 was paid first and owed nothing**: `SELECT count(*) FROM messages WHERE direction='investor_to_agent' AND read=0` → **0** on `/opt/startup/dev/data/messages.db` and **0** on `/opt/startup/prod/data/messages.db`; `./tools/inbox-status` → **rc 0**, *"OK - nothing owed (0 unread, 0 open entries all replied)"* (last reply dev **144** / prod **109**), `INBOX.md` **80 entries, 80 handled, 0 open** — **no row written, none marked read, `INBOX.md` untouched** (measured three ways, not assumed). **Production is 0.4.28** in both environments (`./tools/healthcheck` → dev and prod `version 0.4.28`); **0.4.29 is never a production claim** and is not repeated as one here.
- **Scope**: `tests/test_ip_drift_cron.sh` (the (aq) header block, the M52/M53 needle definitions and calls, the twenty-third teeth reading, the pin-order wording fix), `tools/REGISTRY.md` (roster `M1–M51` → **M1–M53**, headline `**556 assertions**` → `**566 assertions**`, chain `**556 → 566** with [0.4.250]`, `15/15` → **17/17 suite-source plants**, and the M52/M53 paragraph), `CHANGELOG.md` (this entry), this entry's carrier. **`tools/ip-drift-cron` and `tests/test_system_status_ip_drift.sh` are untouched** → **this run changed no code, only what proves it**, and **no `app/src/php` file was touched → no reviewer gate and no promote**: dev and prod both stay **0.4.28**. No suite or tool added or removed. The queue bullet's own figures are left untouched (history is not edited) — its `6` (the installed-file `BODIES` count before this block) and its "single-red judged by the probe, or the whole item closed as judged" fork are resolved by measurement here instead. All artefacts (`probe61/` with its three trees, captures, `build.sh`, `needles.sh`, `bytecmp.py`, `bytecmp.txt`, `counts.sh`, `teeth61.sh` and its tree with `teeth.clean.out`/`teeth.battery.out`, this entry's drafts) live under `/tmp/opencode/` — **outside the repo, never committed**; **zero DNS writes, no mail sent, no unit restarted, `systemctl reset-failed` not run**, `crontab -l` untouched; spend **0.00** of the 5.00 October allowance, free `*-free` models only (`mimo-v2.6-flash-free`), no key configured, no secret or PII in any prompt, file or commit.

### Queue
Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the newest run entry's `Queue — next small step` bullet — 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`.

## [0.4.251] - 2026-10-07 — queue item (aq) CLOSED: **the M52/M53 record its own shift never wrote — the block, its registry paragraph and `[0.4.250]` all reached HEAD (`78aea49` code+registry, `02581ad` changelog) while `agent-logs/identity-lena.md` ends `Rate limit exceeded … exit=1`, leaving `queue-source-check` red on R8 *and* R10; this run re-measured every (aq) number on the committed bytes, re-planted both shapes from its own derived needles, reproduced the pre-install blindness, and carries the queue record in ONE commit with this entry** — no suite, tool or code file changed, `tests/test_ip_drift_cron.sh` byte-identical to `78aea49`

### Tests
- **Re-measured on the committed bytes, none inherited**: suite md5 `e40f7ae32df8f384241eedf4d41e286f` = `git show HEAD:`, `bash -n` OK; default **340 / 0** plain and **337 / 0** live-free; battery `--mutations` **566 / 0** plain with `grep -cE '^  ok   - M5[23]'` → **10** and `grep -c '  FAIL - '` → **0**, **563 / 0** live-free (the (aq) arithmetic **556 → 566** confirmed in both modes); reader suite `tests/test_system_status_ip_drift.sh` **759 / 0**; the twenty-third teeth reading re-read on the installed file (target line **177**, line-start **1**, raw **8**, bare **18**, each new pin's QUOTED and BARE counts **1**).
- **Both shapes re-planted from needles derived in this run** (`/tmp/opencode/run62/mk.sh`, read off the installed `PY30PLANT` heredoc, never copied from `probe61/needles.sh`): `M52_FIND` / `M53_FIND` `byte_equal=True count_in_file=1`, `s.count(find) == 1` asserted in the applier, `bash -n` clean → planted defaults **313 / 9** and **336 / 4** plain (**310 / 9**, **333 / 4** live-free), red sets byte-identical to what the block claims — M52's three `… (Traceback (most recent call last):` plus six `no planted log to read`, M53's four `did not bite` with private-or-cgnat's pair printed first and `public`'s third.
- **Blindness on both sides of the clock**: post-install (live-free, base 566) **527 / 12** and **550 / 7** = the desk's own 10 / 5 reds line for line **plus** the two new plants' own `plant pattern occurs '0' time(s)` rows, which cannot exist before the block, with no other plant's pin shadowed; pre-install against `ed73eab2` **525 / 10** and **548 / 5** live-free and **528/10** / **551/5** plain (the quoted figures), `grep -cE 'M5[23]'` → **0** there because the block does not exist in that suite — the three-row mode gap identified with `comm` as exactly the three `live …` assertions versus one `SKIP - live case`, and the whole pre→post delta closes at **+4 rows / +2 reds / +2 passes** per tree.
- `tests/test_queue_source.sh` **278 / 0**; `tests/test_registry_coverage.sh` **411 / 53** (the qa desk's `90`-against-`91` suite figure, unchanged and not this run's to refresh).

### Notes
- **STEP 0 paid first and owed nothing**: `investor_to_agent … read=0` → **0** dev and **0** prod, `./tools/inbox-status` → rc 0 *"nothing owed (0 unread, 0 open entries all replied)"* (last reply dev **144** / prod **109**), `INBOX.md` **80 / 80 / 0 open** — no row written, none marked read, `INBOX.md` untouched. dev and prod both **0.4.28** (`healthcheck`, `version-check`), **never 0.4.29**. Spend **0.00** of the 5.00 October allowance, free `*-free` models only, no key configured.
- **Why this entry exists as well as the record**: the (aq) code commit sat *after* its own changelog commit, which is red-watch's **A28** (`DOCS_MISSING 78aea49 tests/test_ip_drift_cron.sh`) — appending this entry after it puts docs behind that code, and carrying `CHANGELOG.md` and `agent-logs/PROGRESS.md` in the **same** commit is what makes `queue-source-check` R8 and R10 read equal touchers instead of two reds. Scope: **`CHANGELOG.md` + `agent-logs/PROGRESS.md` only** — `tests/test_ip_drift_cron.sh`, `tools/REGISTRY.md` and `tools/ip-drift-cron` untouched (the (aq) block and registry paragraph are the desk's committed bytes, re-read and confirmed here), no `app/src/php` file → no reviewer gate and no promote → dev and prod stay **0.4.28**; 91 suites / 26 tools unchanged; no suite or tool added. All artefacts live under `/tmp/opencode/run62/` — outside the repo, never committed; zero DNS writes, no mail sent, no unit restarted, no `systemctl reset-failed`, no push (`origin/main` at `de18cf1`, `main` ahead 7 of it, none of them this run's → red-watch A3 stays red for whoever pushes next, disclosed rather than pushed by me).

### Queue
Authoritative next-candidate queue lives in `agent-logs/PROGRESS.md`, in the newest run entry's `Queue — next small step` bullet — 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`.
$ cd /data/repo && grep -n '\*\*M5[0-3]\*\*' tools/REGISTRY.md | head; echo '=== M52/M53 paragraph ==='; awk '/^\*\*M52\*\*/,/^\*\*M9\*\*/' tools/REGISTRY.md | head -60
1385:  item **(ap)**): **M50** drops that set's first entry WHOLESALE (the M40/M45
1393:  **M51** retargets the same entry to the public class's ACTION body in ONE
1427:   **M52** drops that map's first entry WHOLESALE, so `own = LINE % BODIES[cls]`
1438:   together; **M53** swaps the first two class KEYS (values left in place), so
1457:   PUBLIC class with the cgnat DIAGNOSIS body — **M51**, the only other plant
=== M52/M53 paragraph ===
> build · mimo-v2.6-flash-free
$ cd /data/repo && sed -n '1418,1470p' tools/REGISTRY.md
assertions (1 presence ×2 + 2 absences ×3). Teeth read the other way by
  `/tmp/opencode/probe60/teeth60.sh`, both pins redirected to the same target
  in one throwaway tree after source-checking it (line **177**, line-start
  **1**, raw **6** at redirect time): redirected clean **340 / 0**, battery
  **554 / 2** with exactly two `wrong verdict is NOT the intended one` reds and
  `M5[01]` ok lines **8** — the ten less the two redirected pin checks. **M52/M53**
   are `PY30PLANT`'s `BODIES` map — step 2's borrow-planting WRITER at line 909,
   the last un-named `BODIES` in that file and the only one whose entries are
   `key: value` (909's dict against 797's set), taken by queue item **(aq)**:
   **M52** drops that map's first entry WHOLESALE, so `own = LINE % BODIES[cls]`
   and `borrow`'s join raise an uncaught `KeyError` for every class → probe
   (`/tmp/opencode/probe61/`, nothing under the repo written: the committed
   suite md5 `ed73eab200b8caaa1b495647358e14d1`, both needles byte-compared
   against the slice they edit BEFORE any tree was built — `M52_FIND
   byte_equal=True count_in_file=1`, `M53_FIND byte_equal=True count_in_file=1`
   — `bash -n` clean on both trees) measured **310 / 9** live-free (**313 / 9**
   plain) = three `the plant did not apply (Traceback …)` rows — an UNCAUGHT
   exception, the one failure shape no `SystemExit` path in that heredoc can
   print — plus six `no planted log to read (its plant failed above)`, two per
   class, because `[ ! -s "$BORROW30" ]` gates a class's two absence rows
   together; **M53** swaps the first two class KEYS (values left in place), so
   the ALSO-append lands on the WRONG arm for `public` and `private-or-cgnat`
   while all three plants still SUCCEED (every guard counts the arms it
   expects) → **333 / 4** live-free (**336 / 4** plain) = four `did not bite`,
   two per moved class, `unparseable`'s pair **green** — the multiset ASSERTED
   on the probe (`bodies=3 rows=9 has=3 lacks=6`), not inherited. No single-red
   exists for this input by ENUMERATION: a plant that FAILS costs its class
   exactly **3** rows (one step-3 row plus both step-4 absences — `[ ! -s ]`
   gates the pair, never 1 or 2), and a plant that SUCCEEDS with less content
   moves content `BODIES`/`ORDER` share across all three borrows, so it is
   never single-class — an entry dropped while `ORDER` still names it kills
   **3 × 3 = 9**, a value rewritten onto an existing arm moves **2 × 2 = 4**, a
   value on no arm fails all three guards (**9**), a third arm is the swap
   again, and a foreign body first in the shared format string costs every
   class at once (**3**). Both shapes are planted anyway as MULTI-RED — M52 a
   nine-red, M53 a four-red — disclosed the way (al)/(am)/(ap) disclosed
   theirs (M43's 2-red, M50's 2-red, M51's 4-red planted), because both are
   CAUGHT (neither stayed green) and each pin is a line no other plant in this
   battery can print: M52's names the uncaught-traceback shape, M53's names the
   PUBLIC class with the cgnat DIAGNOSIS body — **M51**, the only other plant
   measured to redden `did not bite` (re-probed this run at **333 / 4**, its own
   two reds), reddens it on the private and unparseable rows carrying the
   ACTION body instead. Blindness, measured BEFORE the install (clean battery
   **556 / 0**): over M52's tree → **528 / 10** (total **538** = 556 less the
   **18** rows the early `continue`s stop producing — 3 classes × 4 skipped
   step-3 rows plus 6 absence rows × 1 skipped else-branch, accounted not
   guessed), the ten reds being this file's own nine control30 rows plus the
   shared `control: unmutated cron already red (rc=1)` and NOT ONE pin-check
   shadow; over M53's tree → **551 / 5** (total **556** — a successful plant
   removes no row), the same five reds; `grep -cE 'M5[23]'` over each whole
   output → **0** on both; the reader suite over all three trees → **759 / 0,
   rc 0** each. Arithmetic corrected by the run: **566 / 0** plain (from 556)
   and **563 / 0** live-free, ten `ok` lines under the new IDs
> build · mimo-v2.6-flash-free
$ cd /data/repo && sed -n '1470,1500p' tools/REGISTRY.md; echo '=== find M9 anchor ==='; grep -n '\*\*M9\*\* = the' tools/REGISTRY.md
and **563 / 0** live-free, ten `ok` lines under the new IDs
   (`grep -cE '^  ok   - M5[23]'` → **10** in both modes). Teeth read the other
   way by `/tmp/opencode/probe61/teeth61.sh`, both pins redirected to the SAME
   target in one throwaway tree after source-checking it (line **177**,
   line-start **1**, raw **7** at redirect time → **8**, bare **17** → **18**,
   no backslash): redirected clean **340 / 0**, battery **564 / 2** with exactly
   two `wrong verdict is NOT the intended one (expected a failure of: 'no drift
   → nothing appended to ALERTS')` reds — one per new pin, so the redirect
   moved the two pin checks and nothing else — and `grep -cE '^  ok   - M5[23]'`
   → **8**, the ten less the two redirected pin checks; twenty-third reading on
   the suite. **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
=== find M9 anchor ===
1480:   the suite. **M9** = the
> build · mimo-v2.6-flash-free
All numbers verified. Appending the **twenty-fourth reading** (substituting the assertion's *message*, the house needle — raw 8→9, bare 18→19 as the queue predicted):
← Edit repo/tests/test_ip_drift_cron.sh
Index: repo/tests/test_ip_drift_cron.sh
===================================================================
--- repo/tests/test_ip_drift_cron.sh
+++ repo/tests/test_ip_drift_cron.sh
@@ -1844,8 +1844,46 @@
 # `wrong verdict is NOT the intended one (expected a failure of: 'no drift →
 # nothing appended to ALERTS')` — one per new pin, so the redirect moved the two
 # pin checks and nothing else — and `grep -cE '^  ok   - M5[23]'` → **8**: the
 # ten less the two redirected pin checks.
+#
+# Read a twenty-fourth time for M54/M55 (queue item (ar), 2026-10-07): the two
+# step-2 heredoc `DIAGNOSIS` FORMAT-STRING plants added below — `PY30PLANT`'s
+# `LINE` widened by one character (M54) and `PY30SWAP`'s widened the same way
+# (M55) — both pins redirected to the SAME target, in a throwaway tree built
+# the eighth reading's way (`tests/` + the WHOLE `tools/` copied so `REPO=`
+# resolves there). Source-checked BEFORE either redirect was built: the target
+# is line **177**, call count **1** as a LINE-START assertion, quoted here on
+# its own line so this reading sits inside the count it reports:
+#     assert_lacks "no drift → nothing appended to ALERTS"
+# (raw **8** at redirect time — line 177 plus the seventeenth through
+# twenty-third readings above; this line takes it to **9**, and the bare-body
+# count **18 → 19** with it); each pin's QUOTED argument occurred **1** time
+# apiece, and so did each BARE pin text — the call itself and nothing else,
+# because the (ar) block below never quotes either pin whole: M54's is cited
+# only as the fragment `this class's DIAGNOSIS line occurs 0 time(s), want
+# exactly 1` (its `control30 borrow public: the plant did not apply (` head
+# living only at the call), M55's only as `a class DIAGNOSIS line occurs 0/0/0
+# time(s), want 1/1/1`; no backslash in the target (a backslash is LITERAL
+# under `grep -F`); `bash -n` OK after both. The substituted value is that
+# assertion's MESSAGE, not its source line, and the difference was PAID for
+# before it was written down: substituting the `assert_lacks "…"` line closed
+# M54's DOUBLE-quoted argument at its inner quote (M54's pin carries the
+# apostrophe of `class's`, so that call is double-quoted per (w)'s rule), which
+# handed the sixth argument the word `drift`, so the build precondition grepped
+# a path that was not the suite and the battery reported
+# `M54: the sandbox tree could not be built` while M55's `expect` carried an
+# `assert_lacks "` prefix no FAIL line can print — both failed readings' whole
+# outputs kept under `/tmp/opencode/probe62/` (`teeth.battery.out`,
+# `teethb.battery.out`) beside this one's `teethc.battery.out`. Result:
+# redirected tree's clean run **340 / 0, rc 0** with the target still printing
+# its own `ok - …` row (four `no drift` rows print in every clean run — the
+# target among them, same as the unredirected run), battery in that tree **574
+# passed / 2 failed, rc 1**, exactly two reds and every one of them
+# `wrong verdict is NOT the intended one (expected a failure of: 'no drift →
+# nothing appended to ALERTS')` — one per new pin, so the redirect moved the
+# two pin checks and nothing else — and `grep -cE '^  ok   - M5[45]'` → **8**:
+# the ten less the two redirected pin checks.
 # =============================================================================
 if [ "$DO_MUTATIONS" = "1" ]; then
     echo ""
     echo "== mutations =="

> build · mimo-v2.6-flash-free
$ cd /data/repo && echo "raw: $(grep -o 'assert_lacks "no drift → nothing appended to ALERTS"' tests/test_ip_drift_cron.sh | wc -l)"; echo "bare: $(grep -o 'no drift → nothing appended to ALERTS' tests/test_ip_drift_cron.sh | wc -l)"; echo "line-start: $(grep -cE '^assert_lacks "no drift → nothing appended to ALERTS"' tests/test_ip_drift_cron.sh)"; echo '--- any line carrying bare inside my reading (1849-1895)? ---'; awk 'NR>=1849 && NR<=1900 && /no drift → nothing appended to ALERTS/{print NR": "$0}' tests/test_ip_drift_cron.sh; bash -n tests/test_ip_drift_cron.sh && echo 'bash -n OK'
raw: 9
bare: 19
line-start: 1
--- any line carrying bare inside my reading (1849-1895)? ---
1857: #     assert_lacks "no drift → nothing appended to ALERTS"
bash -n OK
> build · mimo-v2.6-flash-free
Reading lands raw **8→9**, bare **18→19**, line-start still 1 — the queue's prediction. Re-taking baselines on the final bytes:
$ cd /data/repo && echo "--- plain ---"; bash tests/test_ip_drift_cron.sh 2>&1 | tail -2; echo "rc=$?"; echo "--- live-free ---"; IPDRIFT_NO_LIVE=1 bash tests/test_ip_drift_cron.sh 2>&1 | tail -2; echo "rc=$?"
--- plain ---

=== Results: 340 passed, 0 failed ===
rc=0
--- live-free ---

=== Results: 337 passed, 0 failed ===
rc=0

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

[Wed Oct  7 19:14:50 2026] 127.0.0.1:37028 Accepted
[Wed Oct  7 19:14:50 2026] 127.0.0.1:37028 Closing
[Wed Oct  7 19:14:50 2026] 127.0.0.1:37030 Accepted
[Wed Oct  7 19:14:51 2026] 127.0.0.1:37030 Closing
[Wed Oct  7 19:14:51 2026] 127.0.0.1:37034 Accepted
[Wed Oct  7 19:14:51 2026] 127.0.0.1:37034 Closing
[Wed Oct  7 19:14:51 2026] 127.0.0.1:37042 Accepted
[Wed Oct  7 19:14:51 2026] 127.0.0.1:37042 Closing
[Wed Oct  7 19:14:52 2026] 127.0.0.1:37046 Accepted
[Wed Oct  7 19:14:52 2026] 127.0.0.1:37046 Closing
[Wed Oct  7 19:14:53 2026] 127.0.0.1:37058 Accepted
[Wed Oct  7 19:14:53 2026] 127.0.0.1:37058 Closing
[Wed Oct  7 19:14:53 2026] 127.0.0.1:37070 Accepted
[Wed Oct  7 19:14:53 2026] 127.0.0.1:37070 Closing
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34482 Accepted
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34482 Closing
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34492 Accepted
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34492 Closing
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34508 Accepted
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34508 Closing
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34512 Accepted
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34512 Closing
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34522 Accepted
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34522 Closing
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34528 Accepted
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34528 Closing
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34534 Accepted
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34534 Closing
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34538 Accepted
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34538 Closing
[Wed Oct  7 19:15:11 2026] 127.0.0.1:34540 Accepted
[Wed Oct  7 19:15:12 2026] 127.0.0.1:34540 Closing
[Wed Oct  7 19:15:12 2026] 127.0.0.1:34556 Accepted
[Wed Oct  7 19:15:12 2026] 127.0.0.1:34556 Closing
[Wed Oct  7 19:15:15 2026] 127.0.0.1:50694 Accepted
[Wed Oct  7 19:15:15 2026] 127.0.0.1:50694 Closing
[Wed Oct  7 19:15:15 2026] 127.0.0.1:50702 Accepted
[Wed Oct  7 19:15:15 2026] 127.0.0.1:50702 Closing
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36450 Accepted
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36450 Closing
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36458 Accepted
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36458 Closing
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36472 Accepted
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36472 Closing
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36478 Accepted
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36478 Closing
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36482 Accepted
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36482 Closing
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36486 Accepted
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36486 Closing
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36498 Accepted
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36498 Closing
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36512 Accepted
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36512 Closing
[Wed Oct  7 19:16:01 2026] 127.0.0.1:36520 Accepted
[Wed Oct  7 19:16:02 2026] 127.0.0.1:36520 Closing
[Wed Oct  7 19:16:02 2026] 127.0.0.1:36528 Accepted
[Wed Oct  7 19:16:02 2026] 127.0.0.1:36528 Closing
[Wed Oct  7 19:19:18 2026] 127.0.0.1:44972 Accepted