Gladex Agent Logs

  `guarded "$TOOLS_DIR/regression-run"` only — the plant does not touch that
  file — and the suite's own comment above A3 already says a second detacher
  *"fails C1 rather than making A3's own subject ambiguous"*, so the prose and
  the table disagreed inside the same commit. The REGISTRY row carries the
  measured 3; the historical entry is left exactly as written, because a
  changelog is not edited retroactively to make a past number agree.
- **Declared limit, queued as (86)** — the pairing counts `wait` **arguments**,
  it does not resolve them: `wait "$p" "$q"` covers two jobs but decrements
  once, and two `wait "$p"` calls naming the *same* job decrement twice while
  a sibling sleeps on. Both need the argument list split (arity) and, for the
  second, the `$!` assignment resolved — the reader has never had either, and
  no registered tool writes that shape today.
- **Not done, one step per run**: **no other reader in the suite touched**
  (`scan_file`'s `DETACH`/`BG` output and every A2/A4/A6–A14 assertion are
  unchanged, which is why the four earlier mutants re-run to their own recorded
  reds); **no queue item struck beyond (84)** — (73), (78), (79), (81), (82),
  (83), (85) and the whole carried list stand; **no version-train bump**
  (`GLADEX_APP_VERSION` stays `0.4.28`), no promote executed, no service
  restarted, no certificate touched, **zero DNS writes** (no `pdns-api.py`
  call), no mail sent, Nextcloud untouched (`{"installed":true}`, §14 closed
  2026-09-29), `/opt/cloud` untouched, Immich untouched (`{"res":"pong"}`, 8
  accounts), **spend 0.00** (`*-free` only).
- **STEP 0**: unread `investor_to_agent` = **0 dev / 0 prod** at the start of
  the run (direct `SELECT count(*) … AND read=0` on both live SQLite DBs,
  confirmed by `tools/inbox-status` → **exit 0, `owed.total` 0**, **74 entries
  / 74 handled / 0 open**, and `grep '^## ' INBOX.md | grep -v HANDLED` →
  empty), so no unread row was marked read that is not mine; the status reply
  was written anyway rather than skipped — **dev 122 / prod 88**,
  `read=1`, `ts 2026-09-29T09:12Z`, parameterised insert with the unread
  predicate re-checked inside a `BEGIN IMMEDIATE` transaction (abort rc 9 if it
  no longer held), script `rm -f`'d and confirmed absent, unread still **0 /
  0** after. **An unanswered investor is a failed run; there was none.**

### 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 (84 sections as of `[0.4.127]`). 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
→ Read repo/tools/disk-show 
> build · mimo-v2.6-flash-free
Now the mutation control, on sandbox copies (live tree untouched):
← Write /tmp/opencode/mut82.sh
Created file successfully: /tmp/opencode/mut82.sh
> build · mimo-v2.6-flash-free
$ bash /tmp/opencode/mut82.sh
control                planted=-   rc=0  pass=80  fail=0   
breach_decided         planted=yes rc=1  pass=71  fail=7   D1 a mount at/above the threshold exits 3 (want rc=3 got=0);D2 the breach is named on stderr (a caller must not have to parse stdout) (missing: breach at /);D3 ok is false when the exit code is 3;E1 use_pct exactly at the threshold is a breach (>=, not >) (want rc=3 got=0);E4 use_pct exactly equal to a raised threshold still breaches (want rc=3 got=0);M1 divergence (real=0 mutant=0) — breach-decision mutant caught (want rc=3|0 got=0|0);M2 mutation setup: the plant did not land exactly once;
boundary_ge_gt         planted=yes rc=1  pass=70  fail=5   E1 use_pct exactly at the threshold is a breach (>=, not >) (want rc=3 got=0);E2 the boundary row is reported as a breach;E4 use_pct exactly equal to a raised threshold still breaches (want rc=3 got=0);M1 mutation setup: sed did not plant exactly one mutant ('        return 3' must occur once);M2 precondition: threshold comparison found 0 times (want exactly 1);
cannot_verify_removed  planted=yes rc=1  pass=68  fail=8   G1 a watched path missing from the fixture exits 4 (want rc=4 got=0);G3 ok is false - exit 4 is never reported as a pass;G4 precedence: 4 beats 3 (cannot verify outranks a partial breach) (want rc=4 got=0);G5 and 4 beats 0 too - no measured mount means nothing was verified (want rc=4 got=0);G6 a watched path that does not exist on the real fs exits 4 (want rc=4 got=0);G8 the condition is named on stderr (missing: cannot verify);M1 mutation setup: sed did not plant exactly one mutant ('        return 3' must occur once);M2 mutation setup: the plant did not land exactly once;
json_key_dropped       planted=yes rc=1  pass=63  fail=17  C6 keys are exactly the documented set;E3 the same row below a raised threshold exits 0 (want rc=0 got=1);E4 use_pct exactly equal to a raised threshold still breaches (want rc=3 got=1);E5 and one point above it does not (want rc=0 got=1);G4 precedence: 4 beats 3 (cannot verify outranks a partial breach) (want rc=4 got=1);G5 and 4 beats 0 too - no measured mount means nothing was verified (want rc=4 got=1);H8 nothing was unknown in this table;H9 human format exits 0 on the same input (want rc=0 got=1);H10 human output names the entry (missing: exact-file);H11 human output states the read-only promise (missing: never deletes);H12 human output totals the reclaimable bytes (missing: reclaimable total: );M1 divergence (real=1 mutant=0) — breach-decision mutant caught (want rc=3|0 got=1|0);M1 mutant still exits 0 on a clean fixture (surgical, not a crash) (want rc=0 got=1);M1 mutant still exits 4 for cannot-verify (only 3 was removed) (want rc=4 got=1);M2 divergence (real=1 mutant=1) — boundary mutant caught (want rc=3|1 got=1|0);M2 mutant still exits 3 on a real 95% breach (the mutation is surgical) (want rc=3 got=1);M2 mutant still exits 0 on a clean fixture (want rc=0 got=1);
budget_zero            planted=yes rc=1  pass=70  fail=6   H2 the exact 1000-byte file is measured exactly;H4 the directory is measured and marked existing (>= the 5000-byte file inside it);H7 reclaimable_bytes is the sum of the two measured rows (1000 + the tree);H8 nothing was unknown in this table;M1 mutation setup: sed did not plant exactly one mutant ('        return 3' must occur once);M2 mutation setup: the plant did not land exactly once;
threshold_default_100  planted=yes rc=1  pass=66  fail=10  C5 the echoed threshold is the one asked for;D1 a mount at/above the threshold exits 3 (want rc=3 got=0);D2 the breach is named on stderr (a caller must not have to parse stdout) (missing: breach at /);D3 ok is false when the exit code is 3;D4 breaches lists exactly the breaching mount;D5 the breaching mount carries breach=true;E1 use_pct exactly at the threshold is a breach (>=, not >) (want rc=3 got=0);E2 the boundary row is reported as a breach;M1 mutation setup: sed did not plant exactly one mutant ('        return 3' must occur once);M2 mutation setup: the plant did not land exactly once;
> build · mimo-v2.6-flash-free
All seven mutants caught. Now the queue/progress format:
$ cd /data/repo && wc -l agent-logs/PROGRESS.md && grep -n "^## \|^### " agent-logs/PROGRESS.md | tail -30
6443 agent-logs/PROGRESS.md
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]`
6128:### 2026-09-28T14:52Z — post-commit confirmation of the entry above (`875226d`, pushed)
6136:## 2026-09-28T16:00Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; fresh-probe reply **dev 107 / prod 73**), then ONE step: **(64) EXECUTED** — every documented exit code 2 is now *probed*, not merely registered: `tests/test_registry_coverage.sh` section **E** + controls **C14**/**C15**, suite **67 → 86**, `[0.4.114]`
6152:### 2026-09-28T16:30Z — post-commit confirmation of the entry above (`0b1f36b`, pushed `b7e78a0..0b1f36b`)
6160:## 2026-09-28T17:30Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; re-answering reply **dev 108 / prod 74**), then ONE step: **(63) EXECUTED** — `tools/REGISTRY.md`'s regression figures became *checkable*: section **F** + controls **C16–C20** in `tests/test_registry_coverage.sh`, suite **86 → 120**, `[0.4.116]`
6177:### 2026-09-28T17:5xZ — post-commit confirmation of the entry above (`394297c`, pushed `3c8f026..394297c`)
6186:## 2026-09-28T18:45Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; re-answering reply **dev 109 / prod 75**), then ONE step: **(65) EXECUTED** — a documented exit 2 is now probed for a bad *VALUE*, which caught two parsers that had been swallowing `--format` for weeks: `system-status` and `version-check` repaired (validate before any I/O), section **G** + controls **C21**/**C22**, suite **120 → 140**, `[0.4.117]`
6201:### 2026-09-28T19:05Z — post-commit confirmation of the entry above (`35f4acb`, pushed `201f3f7..35f4acb`)
6209:## 2026-09-28T19:35Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; re-answering reply **dev 110 / prod 76**), then ONE step: **(69) EXECUTED** — the exit-2 guard asked *which flag*, never *what a port is*: of the 4 flags whose `--help` says `--flag PORT` only **1** refused `not-a-number`, so two tools reached curl with exit 1 while promising `2 - Invalid arguments`; G's third derived class reads the **METAVAR**, suite **140 → 154**, `[0.4.118]`
6226:### 2026-09-28T19:50Z–20:15Z — post-commit confirmation of the entry above (`db9ea88`, pushed `e7a396c..db9ea88`)
6234:## 2026-09-28T21:05Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; re-answering reply **dev 111 / prod 77**), then ONE step: **(72) EXECUTED** — the missing-value probe was still two FLAG NAMES, and a name list can never be complete: of the **59** help lines shaped `--flag TOKEN`, exactly one tool still died in `shift 2` (`verify-landing --env`, exit **1** against its own `2 - Invalid arguments`), so G's fourth class reads the **WRITING** of the line (one space = takes a value), suite **154 → 168**, `[0.4.119]`
6250:### 2026-09-28T21:37Z — post-commit confirmation of the entry above (`b216430`, pushed `5006617..b216430`)
6258:## 2026-09-28T22:20Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; re-answering reply **dev 112 / prod 78**), then ONE step: **(75) EXECUTED** — the suite's two scope readers used the SAME one-space convention, so they agreed **by construction**: an option line written `--env  ENV` (two spaces) dropped out of the probing scope *and* out of G14's recount together, `miss + fmt + port` still closed and every assertion stayed green while the flag was never probed; a **spacing-independent third reader** + control **C25**, suite **168 → 182**, `[0.4.120]`
6272:### 2026-09-28T22:45Z — post-commit confirmation of the entry above (`9d886b4`, pushed `ba1f79c..9d886b4`)
6280:## 2026-09-29T00:20Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; re-answering reply **dev 114 / prod 80**), then ONE step: **`[0.4.121]` RECONCILED** — run 315 committed its code *and* its registry prose citing a version heading it never wrote, so `main` was **red on a clean tree** (`repo-lint` → exit 1, 2 missing citations); this run writes that heading from the committed code, every number re-measured
6294:### 2026-09-29T01:05Z — post-commit confirmation of the entry above (`d5d0ebc`, pushed `529655e..d5d0ebc`)
6302:### 2026-09-29T03:05Z run — STEP 0 answered FIRST, before any other work
6306:## 2026-09-29T04:35Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; re-answering reply **dev 115 / prod 81**), then ONE step: **(76) EXECUTED** — the (75) reader's own description-column rule left a shape **no reader could see**: `--env  ENV Environment` fell out of the single-space scope *and* out of the third reader, so `conv_extra` stayed 0 while the flag was never probed; widened to one space, control **C27**, suite **190 → 201**, `[0.4.122]`
6321:### 2026-09-29T03:20Z — post-commit confirmation of the entry above (`b80a496`, pushed `c4540bd..b80a496`)
6329:## 2026-09-29T05:20Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; re-answering reply **dev 116 / prod 82**), then ONE step: **(77) EXECUTED** — the row a caller reads first was the one row no assertion opened: of the **19** tools whose `--help` prints an option list, **16** named a flag on their own `usage:` row and **3** did not (`Usage: $0 [OPTIONS]`, or `Usage:` with the synopsis on the next line), so A1/A3 called the tree *fully covered, zero violations* over three tools that never said what they take; one-row reader + control **C28**, suite **201 → 213**, `[0.4.123]`
6344:### 2026-09-29T05:45Z — post-commit confirmation of the entry above (`4537d05`, pushed `d133bc5..4537d05`)
6352:## 2026-09-29T05:07Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; replies **dev 117+118 / prod 83+84**), then ONE step: **INBOX line 468 EXECUTED** — Nextcloud installed with the same 8 accounts as Immich, **§14 closed**, INBOX now **74/74 handled**
6365:### 2026-09-29T05:29Z — post-commit confirmation of the entry above (`d950011`, pushed `366243f..d950011`)
6372:## 2026-09-29T05:50Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; status reply **dev 119 / prod 85**), then ONE step: **(74) EXECUTED** — a suite runs in its **own session**, so `timeout 3 regression-run` returned **124** with the suite reparented to init and its grandchild still writing, and a direct **SIGINT never ended the tool at all**; termination guard + reaped suite group, suite **237 → 255**, `[0.4.124]`
6386:## 2026-09-29T07:41Z main-loop run (continuation, after an environment outage) — STEP 0 re-read FIRST (0 unread both DBs; status reply **dev 120 / prod 86**), **(74) confirmed DONE** on its own push, then the post-push **28 reds attributed to one cause** — the `- Live:` suite figure was a suite behind (59 → 60) — fixed and measured: coverage **187/26 → 213/0**, post-push **all suites green (60 / 5361 / 0)**, `[0.4.125]`
6402:## 2026-09-29T08:20Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; status reply **dev 121 / prod 87**), then ONE step: **(80) EXECUTED** — the detached-child sweep across all 20 registered tools: **no second tool needs (74)'s guard**, because GNU `timeout` signals the child's **process group** and only a foreign *session* escapes it; new suite `tests/test_detached_children.sh` **28/0**, suite **60 → 61**, `[0.4.126]`
6416:### 2026-09-29T09:00Z — post-commit confirmation of the entry above (`1991fb1` + `7ccab89`, pushed `ba38293..7ccab89`)
6424:## 2026-09-29T09:41Z main-loop run — STEP 0 answered FIRST (0 unread both DBs; status reply **dev 122 / prod 88**), then ONE step: **(84) EXECUTED** — `bg_waited()` compared the file's **last** `&` against its **last** `wait`, so a file whose *earlier* child was orphaned read as *waited*; measured live (the fixture exits in 1 s with that child's `sleep 61` alive while the old reader answers rc 0), the reader is now a **per-child pairing** with plants **A15/A16** and the shape run live as **B11–B13**, suite **28 → 33**, `[0.4.127]`
6437:### 2026-09-29T09:55Z — post-commit confirmation of the entry above (`0949ceb`, pushed `28f26bc..0949ceb`)
$ cd /data/repo && bash tools/queue-source-check --format json; echo "rc=$?"
tools/queue-source-check: line 74: agent-logs/PROGRESS.md: Permission denied
tools/queue-source-check: line 74: Next-candidate: command not found
tools/queue-source-check: line 74: [0.4.65]: command not found
tools/queue-source-check: line 74: [0.4.66]: command not found
tools/queue-source-check: line 74: [0.4.65]: command not found
tools/queue-source-check: line 74: --jobs: command not found
tools/queue-source-check: line 74: agent-logs/PROGRESS.md: Permission denied
tools/queue-source-check: line 74: [0.4.66]: command not found
tools/queue-source-check: line 74: [0.4.67]: command not found
tools/queue-source-check: line 74: -: command not found
tools/queue-source-check: line 74: -: command not found
tools/queue-source-check: line 74: AGENT_BRIEF.md: command not found
tools/queue-source-check: line 74: +: command not found
tools/queue-source-check: line 74: 1.: command not found
tools/queue-source-check: line 74: agent-logs/PROGRESS.md: Permission denied
tools/queue-source-check: line 74: Next-candidate: command not found
tools/queue-source-check: line 74: newest_section: command not found
tools/queue-source-check: line 74: progress_bullets: command not found
tools/queue-source-check: command substitution: line 74: syntax error near unexpected token `"Next-candidate queued"'
tools/queue-source-check: command substitution: line 74: `pg_text.count("Next-candidate queued")'
tools/queue-source-check: line 74: -: command not found
tools/queue-source-check: line 74: **Next-candidate: command not found
tools/queue-source-check: line 74: detail: command not found
tools/queue-source-check: command substitution: line 74: unexpected EOF while looking for matching `"'
tools/queue-source-check: line 76: \: command not found
tools/queue-source-check: line 74: queue-source-check - prove that the next-candidate work queue has ONE home.

Why this exists (CHANGELOG [0.4.67], closing [0.4.66]'s queue item 1):
    from [0.4.40] to [0.4.66] every CHANGELOG entry carried its own
     section AND every
     run entry carried a copy of the same list as a
     bullet - two lists, hand-maintained, in two files.
    They diverged exactly as two hand-maintained copies do: PROGRESS's
     queue listed the regression-baseline item that  then
    actioned, while CHANGELOG's  queue never listed it and instead
    carried a  note the run had already rejected by design. The same
    version therefore carried two different queues, so an item could sit in one
    file and be re-proposed from the other - and nothing versioned checked it.

The decision this tool enforces (not asks about):
     is the SINGLE authoritative next-candidate queue.
    It is what the loop appends to and re-reads every run, and it was the copy
    that stayed correct. CHANGELOG's  sections stop carrying items
    after : from  on they are a one-line POINTER at
    agent-logs/PROGRESS.md, and the 111 item lines already written into the
    historical sections are FROZEN - they are history, not a live list, so a
    strike-through edits them in place and nothing is ever added or removed.
    No prose copy states HOW MANY historical sections there are: that number
    grows with every CHANGELOG entry, so a written-down copy is stale by
    construction (three copies said 25 while rules.queue_sections read 62 on
    the day [0.4.106] removed them - the live figure is that JSON key).

Availability (exit 3 cannot: File name too long
tools/queue-source-check: line 104: from: command not found
tools/queue-source-check: line 106: import: command not found
tools/queue-source-check: line 107: import: command not found
tools/queue-source-check: line 108: import: command not found
tools/queue-source-check: line 109: import: command not found
tools/queue-source-check: line 110: import: command not found
tools/queue-source-check: line 111: import: command not found
tools/queue-source-check: line 112: import: command not found
tools/queue-source-check: line 113: import: command not found
tools/queue-source-check: line 115: TOOL: command not found
tools/queue-source-check: line 116: EXIT_OK: command not found
tools/queue-source-check: line 117: EXIT_VIOLATION: command not found
tools/queue-source-check: line 118: EXIT_USAGE: command not found
tools/queue-source-check: line 119: EXIT_CANNOT: command not found
tools/queue-source-check: line 121: FROZEN_ITEMS: command not found
tools/queue-source-check: line 122: PROGRESS_REL: command not found
tools/queue-source-check: line 123: POINTER_NEEDLE: command not found
tools/queue-source-check: line 124: syntax error near unexpected token `('
tools/queue-source-check: line 124: `HEAD_RE = re.compile(r"^## \[([^\]]*)\]")'
rc=2
> build · mimo-v2.6-flash-free
→ Read repo/agent-logs/PROGRESS.md [offset=6416]
$ cd /data/repo && ./tools/queue-source-check --format json; echo "rc=$?"
{"changelog": "/data/repo/CHANGELOG.md", "detail": "one queue: [0.4.127] pointer-only, 111 item line(s) frozen across 84 section(s), 88 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.127", "progress_bullets": 88, "queue_headings_fenced": 1, "queue_headings_raw": 85, "queue_sections": 84}, "timestamp": "2026-09-29T10:54:00Z", "tool": "queue-source-check", "violations": []}
rc=0
> build · mimo-v2.6-flash-free
$ cd /data/repo && git status --porcelain && echo "--- HEAD:" && git log --oneline -1 && echo "--- live disk-show:" && /usr/bin/time -f "wall %e s" ./tools/disk-show --format json > /tmp/opencode/ds_live.json 2>/tmp/opencode/ds_live.err; echo "rc=$?"; tail -2 /tmp/opencode/ds_live.err; python3 -c "
import json;d=json.load(open('/tmp/opencode/ds_live.json'))
print('keys',list(d))
print('threshold',d['threshold'],'ok',d['ok'],'worst',d['worst_path'],d['worst_use_pct'],'breaches',d['breaches'])
for m in d['mounts']: print(' mount',m['path'],m['use_pct'],'avail',m['avail_bytes'],'breach',m['breach'],'err',m['error'])
print('reclaimable_bytes',d['reclaimable_bytes'],'unknown',d['reclaimable_unknown'],'errors',d['errors'])
for r in d['reclaimable']: print('  ',r['name'],r['bytes'],r['error'],r['exists'])
"
M tests/test_registry_coverage.sh
 M tools/REGISTRY.md
?? tests/test_disk_show.sh
?? tools/disk-show
--- HEAD:
deea81d docs: [0.4.127] post-commit confirmation — full regression 61 suites / 5394 / 0 green (5389 + 5, the step's own 5), push 28f26bc..0949ceb, gates re-read (repo-lint entries 132), STEP 0 still 0/0 with dev 122 / prod 88 newest
--- live disk-show:
rc=0
wall 3.04 s
keys ['tool', 'timestamp', 'threshold', 'ok', 'worst_path', 'worst_use_pct', 'breaches', 'mounts', 'reclaimable', 'reclaimable_bytes', 'reclaimable_unknown', 'errors']
threshold 90 ok True worst / 77.5 breaches []
 mount / 77.5 avail 22397104128 breach False err None
 mount /data 5.1 avail 110358700032 breach False err None
reclaimable_bytes 4499706892 unknown 1 errors []
   go-build-cache 844235868 None True
   go-modcache-gomod 292615758 None True
   go-modcache-gomodcache 833032839 None True
   go-modcache-gocache 0 None False
   go-modcache-gomod2 0 None False
   go-modcache-go 0 None False
   go-modcache-gm2 0 None False
   gopath-tmp 703108243 None True
   gopath-root 1324031577 None True
   go-build-root 169612233 None True
   pip-cache 13660700 None True
   apt-archives 319409674 None True
   loop-scratch None timeout True

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

[Tue Sep 29 12:25:28 2026] 127.0.0.1:36204 Accepted
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36204 Closing
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36210 Accepted
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36220 Accepted
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36210 Closing
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36212 Accepted
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36220 Closing
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36214 Accepted
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36212 Closing
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36248 Accepted
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36214 Closing
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36248 Closing
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36256 Accepted
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36256 Closing
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36260 Accepted
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36260 Closing
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36274 Accepted
[Tue Sep 29 12:25:28 2026] 127.0.0.1:36274 Closing
[Tue Sep 29 12:38:50 2026] 127.0.0.1:35008 Accepted
[Tue Sep 29 12:38:50 2026] 127.0.0.1:35008 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:38:50 2026] 127.0.0.1:35008 Closing
[Tue Sep 29 12:38:52 2026] 127.0.0.1:35016 Accepted
[Tue Sep 29 12:38:52 2026] 127.0.0.1:35016 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:38:52 2026] 127.0.0.1:35016 Closing
[Tue Sep 29 12:39:17 2026] 127.0.0.1:51540 Accepted
[Tue Sep 29 12:39:17 2026] 127.0.0.1:51540 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:39:17 2026] 127.0.0.1:51540 Closing
[Tue Sep 29 12:39:19 2026] 127.0.0.1:51546 Accepted
[Tue Sep 29 12:39:19 2026] 127.0.0.1:51546 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:39:19 2026] 127.0.0.1:51546 Closing
[Tue Sep 29 12:41:48 2026] 127.0.0.1:56900 Accepted
[Tue Sep 29 12:41:48 2026] 127.0.0.1:56900 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:41:48 2026] 127.0.0.1:56900 Closing
[Tue Sep 29 12:41:49 2026] 127.0.0.1:56912 Accepted
[Tue Sep 29 12:41:49 2026] 127.0.0.1:56912 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:41:49 2026] 127.0.0.1:56912 Closing
[Tue Sep 29 12:42:15 2026] 127.0.0.1:35016 Accepted
[Tue Sep 29 12:42:15 2026] 127.0.0.1:35016 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:42:15 2026] 127.0.0.1:35016 Closing
[Tue Sep 29 12:42:16 2026] 127.0.0.1:35028 Accepted
[Tue Sep 29 12:42:16 2026] 127.0.0.1:35028 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:42:16 2026] 127.0.0.1:35028 Closing
[Tue Sep 29 12:47:02 2026] 127.0.0.1:41968 Accepted
[Tue Sep 29 12:47:02 2026] 127.0.0.1:41968 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:47:02 2026] 127.0.0.1:41968 Closing
[Tue Sep 29 12:47:03 2026] 127.0.0.1:41972 Accepted
[Tue Sep 29 12:47:03 2026] 127.0.0.1:41972 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:47:03 2026] 127.0.0.1:41972 Closing
[Tue Sep 29 12:47:29 2026] 127.0.0.1:57826 Accepted
[Tue Sep 29 12:47:29 2026] 127.0.0.1:57826 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:47:29 2026] 127.0.0.1:57826 Closing
[Tue Sep 29 12:47:31 2026] 127.0.0.1:57830 Accepted
[Tue Sep 29 12:47:31 2026] 127.0.0.1:57830 Closed without sending a request; it was probably just an unused speculative preconnection
[Tue Sep 29 12:47:31 2026] 127.0.0.1:57830 Closing
[Tue Sep 29 12:49:36 2026] 127.0.0.1:47426 Accepted
[Tue Sep 29 12:49:36 2026] 127.0.0.1:47426 Closing
[Tue Sep 29 12:54:38 2026] 127.0.0.1:41514 Accepted
[Tue Sep 29 12:54:38 2026] 127.0.0.1:41514 Closing
[Tue Sep 29 12:54:39 2026] 127.0.0.1:41524 Accepted