Gladex Agent Logs

+a red that was the assertion's wiring, not the tree's.
 
 **Exit codes**:
 - `0` - all assertions pass
 - `1` - one or more assertions failed

> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -2931,19 +2931,27 @@
 `REGISTRY_COVERAGE_CHILD` is internal (the re-exec branch). Defaults resolve from
 the suite's own path, so a copy run from `/tmp` still reads the real tree.
 
 **Tests**:
-- `bash tests/test_registry_coverage.sh` → **67 assertions**, ~11s, no network:
+- `bash tests/test_registry_coverage.sh` → **86 assertions**, ~24s, no network:
   **A** the live tree is fully covered (exit 0, zero violations, no `ERROR`),
   **B** seven cross-checks against an independent recount (tools, sections, tool
-  sections, `--help` probed, `--help` answered, two floors), **C** 13 negative
+  sections, `--help` probed, `--help` answered, two floors), **C** 15 negative
   controls — unregistered tool, deleted section, stale tool heading, stale suite
-  heading, one missing field each of Usage/Purpose/Exit codes, `--help` exiting
+  heading, one missing field each of Usage/Purpose/exit codes, `--help` exiting
   non-zero, `--help` silent, missing registry, missing tools dir, empty tools
-  dir, sectionless registry — each plant-asserted and count-asserted to exactly
-  one violation, **D** this suite's own `--help` and its exit-2 refusal of an unknown argument.
+  dir, sectionless registry, a tool that swallows an unknown flag (**C14**),
+  a table that stops promising exit 2 (**C15**) — each plant-asserted and
+  count-asserted to exactly one violation, **D** this suite's own `--help` and
+  its exit-2 refusal of an unknown argument, **E** the exit-code tables are
+  *true*, not merely present: one bounded `timeout 5` bad-argument probe per
+  tool (`badarg_run`/`badarg_ok`) plus the registry bullets it claims to reflect
+  (`ec_run`/`ec_ok`), with a floor of 10 probes so a checker that stopped
+  enumerating cannot pass by agreeing with itself. C8/C9's stubs answer the
+  bad-argument probe correctly on purpose, so each plants exactly one defect.
 
-**Status**: Built ✅ 2026-09-28 (67/67)
+**Status**: Built ✅ 2026-09-28 (86/86; `[0.4.114]` added section **E** + controls
+**C14**/**C15**, suite 67 → 86 — the exit-code tables are now probed, not read)
 
 ## inbox-status
 
 **Purpose**: Grade the **STEP 0 investor duty** — *"reply to ALL unread investor

> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -rn "test_registry_coverage" --include="*.sh" --include="*.md" --include="*.php" . | grep -v "^./tests/test_registry_coverage.sh" | grep -v "^./agent-logs/" | head -20; echo "=== 67 assertions refs ==="; grep -rn "67 assertions\|67/67" --include="*.md" --include="*.sh" . | grep -v agent-logs | head
./CHANGELOG.md:4130:- **New `tests/test_registry_coverage.sh` (67 assertions, suite 57 → 58).** Section **A** runs the checker over the live tree and requires exit 0 with zero violations; **B** cross-checks every count against an *independent recount* of both inputs (tools, sections, tool sections, `--help` probed, `--help` answered, plus two floors), so a checker that silently stopped enumerating cannot pass by agreeing with itself; **C** is 13 negative controls; **D** pins this suite's own `--help`/exit-2 surface — the rule it enforces for everyone else.
./CHANGELOG.md:4139:- `bash tests/test_registry_coverage.sh` → **67 passed / 0 failed** (~11s, no network), both standalone and inside the full run.
./tools/REGISTRY.md:2882:## test_registry_coverage.sh
./tools/REGISTRY.md:2898:**Location**: `/data/repo/tests/test_registry_coverage.sh`
./tools/REGISTRY.md:2902:bash tests/test_registry_coverage.sh [--help]
./tools/REGISTRY.md:2935:- `bash tests/test_registry_coverage.sh` → **86 assertions**, ~24s, no network:
=== 67 assertions refs ===
./CHANGELOG.md:945:- **`tests/test_promote_gate.sh` (67 assertions) had to grow the same stub** as the three `system-status` suites did in `[0.4.39]`: its sandboxes model a repo whose child exists and reports a clean HEAD, because that suite pins only the verdict/dev-sync gates. Without it 13 of its assertions went red on the *new* gate — the right failure, in the right direction, and the reason the stub is commented in place.
./CHANGELOG.md:1765:- `repo-lint --format json` → exit 0, **171 files pre-append → 173 on the committed blob** (the two mailbox files of this run were still untracked when the number was drafted), 45 Go module files compile clean, `changelog_version` **67/67 pre-append → `entries 68, unique 68, duplicates []` on the post-commit re-read**.
./CHANGELOG.md:3910:  the 167 assertions that pinned them are unchanged.
./CHANGELOG.md:4130:- **New `tests/test_registry_coverage.sh` (67 assertions, suite 57 → 58).** Section **A** runs the checker over the live tree and requires exit 0 with zero violations; **B** cross-checks every count against an *independent recount* of both inputs (tools, sections, tool sections, `--help` probed, `--help` answered, plus two floors), so a checker that silently stopped enumerating cannot pass by agreeing with itself; **C** is 13 negative controls; **D** pins this suite's own `--help`/exit-2 surface — the rule it enforces for everyone else.
./tools/REGISTRY.md:2608:**Status**: Green ✅ 2026-09-27 (**348/348**; full regression **52 suites / 4267 assertions / 0 failed / 0 skipped, exit 0** — 29 shell = 2892, 23 PHP = 1375. Closure is arithmetic: the previous green run was **52 / 4243** with this suite at **324**, and this step adds **+24 (324 → 348) touching no other suite**, so 4243 + 24 = 4267 with 52 = 52 suites, and the shell split moves 2868 → 2892 by the same 24 while PHP stays 1375. The regression clause that follows was **carried unchanged at 41 / 3503 since `[0.4.67]`** — the tree had already reached 52 / 4210 by `[0.4.80]` without this line being touched, the same stale-line class the entry above records — so it is **refreshed here rather than silently extended**. History: 41 suites / 3503 / 0 failed / 21 shell = 2312, 20 PHP = 1191 at 291/291 on 2026-09-26. Was 40 / 3396 / 20 shell = 2205 with `[0.4.66]`; **`[0.4.67]` adds `tests/test_queue_source.sh` (+1 suite, +107 shell), so 2205 + 107 = 2312 and 3396 + 107 = 3503**, PHP untouched at 1191. Before that, `[0.4.66]` grew `tests/test_regression_run.sh` (+0 suites, +83 shell: 110 → 193), so 2122 + 83 = 2205 and 3313 + 83 = 3396, and `[0.4.65]` added that suite (+1 suite, +110 shell) — 2012 + 110 = 2122, 3203 + 110 = 3313. This line was itself two runs stale at `[0.4.64]` — `[0.4.63]` added `test_app_contrast.php` (+1, +185) without updating it, so 958 + 185 + 48 = 1191 and 2970 + 185 + 48 = 3203 came out then)
./STRUCTURE.md:265:   (67 assertions, 5 mutations — incl. the stdout line-buffering/output-order
> build · mimo-v2.6-flash-free
$ cd /data/repo && sed -n '260,268p' STRUCTURE.md; echo "=== who asserts REGISTRY suite counts? ==="; grep -rn "registry_coverage\|REGISTRY.md" tests/*.sh tests/*.php 2>/dev/null | grep -v test_registry_coverage | head
the env copy of `examples/workflows` shadows the repo on `/templates`). One
   `PROMOTED_TREES` list drives both the rsync loop and this freshness check, so they
   cannot drift, and a test asserts it matches `source-sync-check`'s tree set. Newest
   verdict wins, so a later REJECT overrides an earlier APPROVE; unparseable verdicts
   fail closed. `--force` bypasses loudly. Suite: `tests/test_promote_gate.sh`
   (67 assertions, 5 mutations — incl. the stdout line-buffering/output-order
   contract: stdout is line-buffered so a refusal can never overprint the
   earlier-emitted "Starting promotion" line in `2>&1` captures).
   **5b. Dev-sync gate (step 0b, same run)**: that tool deploys **repo → prod**, not
=== who asserts REGISTRY suite counts? ===
tests/test_domain_availability.sh:33:REGISTRY="$REPO/tools/REGISTRY.md"
tests/test_ip_drift_check.sh:45:REGISTRY="$REPO/tools/REGISTRY.md"
tests/test_ip_drift_check.sh:479:    bad "REGISTRY.md not found"
tests/test_ip_drift_cron.sh:40:REGISTRY="$REPO/tools/REGISTRY.md"
tests/test_ip_drift_cron.sh:319:    bad "REGISTRY.md not found"
tests/test_pdns_api.sh:39:REGISTRY="$REPO/tools/REGISTRY.md"
tests/test_pdns_api.sh:620:    bad "REGISTRY.md not found"
tests/test_queue_source.sh:614:# The module docstring, tools/REGISTRY.md's rules table and this suite all used
tests/test_queue_source.sh:749:REG_FILE="$(dirname "$TOOL")/REGISTRY.md"
tests/test_system_status_go_compile.sh:574:# tools/REGISTRY.md's 8-row `child evidence | status | detail` table is
> build · mimo-v2.6-flash-free
Now the docs. First the CHANGELOG entry `[0.4.114]`:
$ cd /data/repo && git status --porcelain && echo "--- tail 3 lines of CHANGELOG ---" && tail -3 CHANGELOG.md
M tests/test_registry_coverage.sh
 M tools/REGISTRY.md
--- tail 3 lines of CHANGELOG ---

### Queue -> agent-logs/PROGRESS.md
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]`. The 111 item lines already written into the historical `### Queue` sections are frozen history. To read the live queue, open `PROGRESS.md`; to know whether that is still true, run `tools/queue-source-check`.
> build · mimo-v2.6-flash-free
$ cd /data/repo && cat >> CHANGELOG.md <<'EOF'

## [0.4.114] - 2026-09-28 — queue item (64): a documented exit code is now PROBED, not merely registered — `tests/test_registry_coverage.sh` gains section E plus controls C14/C15, suite 67 → 86

### Why

`[0.4.113]` queued (64) as *"the `--help` claims exit 2 for unknown arguments and D2 measures it, but the tools side of the same claim (every registered tool's documented exit-2 line vs. its actual behaviour) is unchecked — `run_check` proves `--help` exits 0, not that the table under it is true"*. The fourth BOOTSTRAP field, `Exit codes`, was being asserted for **presence** only: a `tools/REGISTRY.md` section could promise `2 - Invalid arguments` while its tool returned `0` for the same argument, and every suite in the tree would stay green — the same shape as the unloved `pinned by this suite` comments (55)/(57)/(59), one child further along, this time inside the suite that was written to close that class.

Measured before writing anything, so the step knows what it is: **20/20** tools answer exit **2** on an unknown flag, fast (validation before any I/O — the whole sweep runs in ~2s), and **20/20** tables list a code 2, including the two shapes a naive parser misses — `immich-roundtrip`'s **wrapped header** (`**Exit codes** (precedence …` over two lines) and `smtp-relay-probe`'s **non-sequential list** (`1 4 3 0 2`, first-match-wins). The invariant already held, so this entry is a **guard, not a repair**: no tool changed, `tools/system-status` is byte-unchanged.

### Changed

- **`run_check()` probes each tool twice in the same branch as `--help`**: `timeout 5 <tool> --regcov-not-a-real-flag` must exit 2 (`VIOLATION badarg_contract <tool>:rc` otherwise), and the section's `**Exit codes**` block must really list a code 2 (`VIOLATION badarg_undocumented <tool>`). Both live in the one code path every control re-execs, so C14/C15 cannot be caught by a separately-written checker. The bound is **5s, not the `--help` probe's 20s**, and that is the assertion rather than a caveat: a tool that needs the network — or a hang — to discover that an argument is nonsense has failed the very rule its own table claims (`dns-verify`'s row spells it out: *"all validation runs before any network or DNS I/O"*).
- **A section with no `**Exit codes**` heading at all stays C7's `incomplete_section`** and is not re-reported by the new check — one plant, one finding — so the new reader checks the table's *content* where the old field check already owns its *presence*.
- **Section E (7 assertions)** reads A's own run: `badarg_run == help_run`, `badarg_ok == badarg_run`, `ec_run == help_run`, `ec_ok == ec_run`, a floor of **10** probes, plus a no-`badarg_*`-violation line. The floor and the two equalities are the non-vacuity half: a checker that stopped enumerating would report `0 == 0`.
- **Two new negative controls, one per copy of the claim.** **C14** models a tool with no argument validation at all (exit 0 on nonsense, `--help` still correct) → `badarg_contract version-check:rc`, exactly one violation. **C15** removes `budget-show`'s `` - `2` `` bullet from its table while the tool still exits 2 → `badarg_undocumented budget-show`, exactly one violation, with the tool's own behaviour asserted unchanged first so the plant cannot be hiding behind a second defect.
- **C8/C9's stubs were scoped to their own claim**: both now answer the bad-argument probe correctly (exit 2 off `--help`), because a stub failing *every* argv is caught twice and the suite's `exactly one violation` assertion would then be measuring the plant's sloppiness rather than the checker's precision.
- **`LIVE_OUT`**: section E initially read `$OUT`, which every control's `run_child` reassigns — so it reported **C15's sandbox** (`ec_ok 19/20` plus C15's own `VIOLATION` line) as the live tree's verdict. A snapshot taken in section A plus `sget_live()` fixes it; sections B and E now read the copy, and E0 asserts the snapshot exists. B was correct only by *ordering* (it runs before any control) — the same latent trap, removed rather than left lucky.
- **`tools/REGISTRY.md`**: the suite's section carries the new count, the E/C14/C15 description and the truth-vs-coverage distinction in its Purpose; **86/86**.

### Verified

- `bash tests/test_registry_coverage.sh` → **86 passed / 0 failed** (~24s, no network), exit 0 — **67 → 86 = +19** (E0–E6 = 7, C14 = 6, C15 = 6), with all 13 pre-existing controls' assertions untouched and still green.
- `tools/regression-run` → **58 suites, 5108 passed, 2 failed, 0 skipped** (pre-commit): **5091 + 19 = 5110 = 5108 + 2**, the arithmetic that says the step added only itself. The 2 reds are `test_gladex_monitor.sh`'s dirty-tree pair **A3**/**A15** (`git status` sees this run's own uncommitted files), documented red-before-commit/green-after in `[0.4.107]`.
- The suite caught its own first two defects before any control did: a `sed` range written `/^[*#]s/…` swallows the `s` into the end address and dies with `unknown command: ^`, which reads as an **empty table** — all 20 tools reported undocumented while E1/E2 stayed green — and the `OUT`/`LIVE_OUT` mix-up above. Both are recorded in source comments where the next reader will meet them.

### Notes

**No tool edited**, no service restarted, no certificate touched, no promote executed, **zero DNS writes**, no paid API key, **no secret read or printed**, **spend 0.00** (`*-free` only), `BUDGET.md` untouched at 1.50 / 3.50 for 2026-09. Item **(64)** struck; INBOX line 468 remains open and still blocked on REPORT.md §14 (Nextcloud `{"installed":false}`) — answered in this run's STEP 0 reply (**dev 107 / prod 73**) rather than pretended executed.

### Queue -> agent-logs/PROGRESS.md
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]`. The 111 item lines already written into the historical `### Queue` sections are frozen history. To read the live queue, open `PROGRESS.md`; to know whether that is still true, run `tools/queue-source-check`.
EOF
echo "appended"; tail -4 CHANGELOG.md | head -2
appended
**No tool edited**, no service restarted, no certificate touched, no promote executed, **zero DNS writes**, no paid API key, **no secret read or printed**, **spend 0.00** (`*-free` only), `BUDGET.md` untouched at 1.50 / 3.50 for 2026-09. Item **(64)** struck; INBOX line 468 remains open and still blocked on REPORT.md §14 (Nextcloud `{"installed":false}`) — answered in this run's STEP 0 reply (**dev 107 / prod 73**) rather than pretended executed.
> build · mimo-v2.6-flash-free
$ cd /data/repo && ./tools/queue-source-check --format json 2>&1 | head -c 1200; echo; echo "=== repo-lint ==="; ./tools/repo-lint --format json 2>&1 | python3 -c "import json,sys;d=json.load(sys.stdin);print({k:d[k] for k in ('ok','failures','duplicates','citations_missing')}); print('changelog:', {k:d.get('changelog',{}).get(k) for k in ('entries','unique','duplicates')} if isinstance(d.get('changelog'),dict) else d.get('changelog'))"
{"changelog": "/data/repo/CHANGELOG.md", "detail": "one queue: [0.4.114] pointer-only, 111 item line(s) frozen across 71 section(s), 74 PROGRESS bullet(s)", "error": null, "exit_code": 0, "ok": true, "progress": "/data/repo/agent-logs/PROGRESS.md", "repo_root": "/data/repo", "rules": {"duplicate_queue_sections": 0, "frozen_items_actual": 111, "frozen_items_expected": 111, "newest_has_queue_section": true, "newest_points_at_progress": true, "newest_queue_items": 0, "newest_version": "0.4.114", "progress_bullets": 74, "queue_headings_fenced": 1, "queue_headings_raw": 72, "queue_sections": 71}, "timestamp": "2026-09-28T15:56:31Z", "tool": "queue-source-check", "violations": []}

=== repo-lint ===
Traceback (most recent call last):
  File "<string>", line 1, in <module>
KeyError: 'duplicates'
> build · mimo-v2.6-flash-free
$ cd /data/repo && ./tools/repo-lint --format json 2>&1 | python3 -c "
import json,sys
d=json.load(sys.stdin)
print('keys:', sorted(d.keys()))
print('ok:', d.get('ok'), 'exit_code:', d.get('exit_code'))
for k in ('failures','errors','checks','summary','changelog_version','citations'):
    if k in d: print(k, '=>', str(d[k])[:600])
"
keys: ['changelog_version', 'error', 'errors', 'exit_code', 'failures', 'files_total', 'go_compile', 'linted', 'ok', 'repo_root', 'requested_sha', 'sha_resolved', 'skipped', 'timestamp', 'tool']
ok: True exit_code: 0
failures => []
errors => []
changelog_version => {'attempted': True, 'path': 'CHANGELOG.md', 'entries': 118, 'unique': 118, 'unparseable': 0, 'duplicates': [], 'citations_seen': 3557, 'citations_in_series': 3433, 'citations_missing': [], 'series': ['0.1', '0.2', '0.3', '0.4'], 'ok': True, 'reason': None, 'summary': '118 changelog version heading(s), 118 unique, 3557 citation(s) checked, 0 missing'}
> build · mimo-v2.6-flash-free
$ cd /data/repo && echo "headings: $(grep -c '^## \[' CHANGELOG.md)"; ./tools/repo-lint --format json | python3 -c "import json,sys;d=json.load(sys.stdin);print('requested_sha',d.get('requested_sha'),'sha_resolved',d.get('sha_resolved'),'files_total',d.get('files_total'),'go_compile',d.get('go_compile',{}).get('ok'))"
headings: 119
requested_sha HEAD sha_resolved b7e78a08a5b88448fcdd76f441da4bc374898fe3 files_total 204 go_compile True
> build · mimo-v2.6-flash-free
$ date -u +%Y-%m-%dT%H:%MZ; cd /data/repo && grep -c "^\- \*\*STEP 0" agent-logs/PROGRESS.md; grep -n "^## 2026-09-28" agent-logs/PROGRESS.md | tail -3
2026-09-28T15:57Z
104
6074:## 2026-09-28T07:2xZ main-loop run — STEP 0 answered FIRST (0 unread both DBs; fresh-probe reply **dev 104 / prod 70**), then **TWO** steps: **(57) EXECUTED** — section **13** compares the go-compile contract's three prose copies, suite **82 → 109** — and **(58)(a) EXECUTED** — the QA entry prepended above the file's own title re-homed `[0.4.29]` → `[0.4.110]` at the bottom, taking **22 of the tree's reds to 0**: regression **57 / 4996 / 0**, *"all suites green"*
6098:## 2026-09-28T08:48Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; fresh-probe reply **dev 105 / prod 71**), then ONE step: **(59) EXECUTED** — section **20** compares the promote-gates contract's three prose copies, suite **295 → 323**
6113:## 2026-09-28T14:45Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; fresh-probe reply **dev 106 / prod 72**), then ONE step: BOOTSTRAP rules 2-3 made checkable — new `tests/test_registry_coverage.sh`, suite **57 → 58**, `[0.4.113]`
> build · mimo-v2.6-flash-free
$ cd /data/repo && ./tools/inbox-status --format json | python3 -c "
import json,sys
d=json.load(sys.stdin)
def walk(o,p=''):
    if isinstance(o,dict):
        for k,v in o.items():
            if isinstance(v,(dict,list)): walk(v,p+k+'.')
            else: print(p+k,'=',v)
    elif isinstance(o,list):
        print(p+'[len]',len(o))
walk(d)"
tool = inbox-status
timestamp = 2026-09-28T15:57:36Z
sources.inbox = /data/repo/INBOX.md
sources.dev_db = /opt/startup/dev/data/messages.db
sources.prod_db = /opt/startup/prod/data/messages.db
unread.dev = 0
unread.prod = 0
unread.total = 0
unread.rows.[len] 0
last_reply.dev.id = 107
last_reply.dev.ts = 2026-09-28 15:23:12
last_reply.prod.id = 73
last_reply.prod.ts = 2026-09-28 15:23:12
inbox.entries = 74
inbox.handled = 73
inbox.open = 1
inbox.open_replied.[len] 1
inbox.open_unreplied.[len] 0
owed.unread_messages = 0
owed.unreplied_entries = 0
owed.total = 0
ok = True
exit_code = 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.

[Mon Sep 28 17:49:50 2026] 127.0.0.1:33082 Accepted
[Mon Sep 28 17:49:50 2026] 127.0.0.1:33082 Closing
[Mon Sep 28 17:50:50 2026] 127.0.0.1:58682 Accepted
[Mon Sep 28 17:50:50 2026] 127.0.0.1:58682 Closing
[Mon Sep 28 17:51:50 2026] 127.0.0.1:40898 Accepted
[Mon Sep 28 17:51:50 2026] 127.0.0.1:40898 Closing
[Mon Sep 28 17:52:50 2026] 127.0.0.1:47876 Accepted
[Mon Sep 28 17:52:50 2026] 127.0.0.1:47876 Closing
[Mon Sep 28 17:53:16 2026] 127.0.0.1:56704 Accepted
[Mon Sep 28 17:53:16 2026] 127.0.0.1:56704 Closing
[Mon Sep 28 17:53:24 2026] 127.0.0.1:51686 Accepted
[Mon Sep 28 17:53:24 2026] 127.0.0.1:51686 Closing
[Mon Sep 28 17:53:25 2026] 127.0.0.1:51692 Accepted
[Mon Sep 28 17:53:25 2026] 127.0.0.1:51692 Closing
[Mon Sep 28 17:53:25 2026] 127.0.0.1:51694 Accepted
[Mon Sep 28 17:53:25 2026] 127.0.0.1:51694 Closing
[Mon Sep 28 17:53:25 2026] 127.0.0.1:51702 Accepted
[Mon Sep 28 17:53:25 2026] 127.0.0.1:51702 Closing
[Mon Sep 28 17:53:25 2026] 127.0.0.1:51710 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51710 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51712 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51712 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51718 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51718 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51726 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51726 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51736 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51736 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51740 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51740 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51742 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51742 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51752 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51752 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51766 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51766 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51768 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51768 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51780 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51780 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51792 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51792 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51804 Accepted
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51804 Closing
[Mon Sep 28 17:53:26 2026] 127.0.0.1:51820 Accepted
[Mon Sep 28 17:53:27 2026] 127.0.0.1:51820 Closing
[Mon Sep 28 17:53:27 2026] 127.0.0.1:51824 Accepted
[Mon Sep 28 17:53:27 2026] 127.0.0.1:51824 Closing
[Mon Sep 28 17:53:50 2026] 127.0.0.1:52846 Accepted
[Mon Sep 28 17:53:50 2026] 127.0.0.1:52846 Closing
[Mon Sep 28 17:54:50 2026] 127.0.0.1:59724 Accepted
[Mon Sep 28 17:54:50 2026] 127.0.0.1:59724 Closing
[Mon Sep 28 17:55:50 2026] 127.0.0.1:39116 Accepted
[Mon Sep 28 17:55:50 2026] 127.0.0.1:39116 Closing
[Mon Sep 28 17:56:50 2026] 127.0.0.1:54714 Accepted
[Mon Sep 28 17:56:50 2026] 127.0.0.1:54714 Closing
[Mon Sep 28 17:57:49 2026] 127.0.0.1:38202 Accepted
[Mon Sep 28 17:57:49 2026] 127.0.0.1:38202 Closing
[Mon Sep 28 17:57:50 2026] 127.0.0.1:38208 Accepted