Gladex Agent Logs

Exactly the five expected paths, nothing staged by another desk. Staging by explicit pathspec and committing.
$ cd /data/repo
git add tools/attribution-gap tests/test_attribution_gap.sh tools/REGISTRY.md CHANGELOG.md agent-logs/PROGRESS.md
echo "=== staged ==="; git diff --cached --name-only
echo "=== unstaged after staging ==="; git status --porcelain
echo "=== stat ==="; git diff --cached --stat
=== staged ===
CHANGELOG.md
agent-logs/PROGRESS.md
tests/test_attribution_gap.sh
tools/REGISTRY.md
tools/attribution-gap
=== unstaged after staging ===
M  CHANGELOG.md
M  agent-logs/PROGRESS.md
M  tests/test_attribution_gap.sh
M  tools/REGISTRY.md
M  tools/attribution-gap
=== stat ===
 CHANGELOG.md                  |  19 +++++
 agent-logs/PROGRESS.md        |  24 ++++++
 tests/test_attribution_gap.sh | 190 +++++++++++++++++++++++++++++++++++++++++-
 tools/REGISTRY.md             |  79 +++++++++++++-----
 tools/attribution-gap         | 124 +++++++++++++++++++++++----
 5 files changed, 397 insertions(+), 39 deletions(-)
> build · mimo-v2.6-flash-free
$ cd /data/repo
git commit -m "run 960: attribution-gap window opens on a DAY boundary so the default and --all agree by construction; refuses an unreadable history (exit 3) instead of printing a clean verdict; suite 58 -> 80; CHANGELOG [0.4.350]" -- tools/attribution-gap tests/test_attribution_gap.sh tools/REGISTRY.md CHANGELOG.md agent-logs/PROGRESS.md
echo "=== commit rc above; log ==="; git log --oneline -1
echo "=== git status --porcelain straight after ==="; git status --porcelain
[main 790cf47] run 960: attribution-gap window opens on a DAY boundary so the default and --all agree by construction; refuses an unreadable history (exit 3) instead of printing a clean verdict; suite 58 -> 80; CHANGELOG [0.4.350]
 5 files changed, 397 insertions(+), 39 deletions(-)
=== commit rc above; log ===
790cf47 run 960: attribution-gap window opens on a DAY boundary so the default and --all agree by construction; refuses an unreadable history (exit 3) instead of printing a clean verdict; suite 58 -> 80; CHANGELOG [0.4.350]
=== git status --porcelain straight after ===
> build · mimo-v2.6-flash-free
Commit `790cf47` landed, tree clean, `agent-logs/PROGRESS.md` no longer listed (rule 1/3 satisfied). Pushing.
$ cd /data/repo
git push origin main 2>&1 | tail -5; echo "push rc=${PIPESTATUS[0]}"
echo "=== rev-list ==="; git rev-list --count origin/main..main
echo "=== git status --porcelain ==="; git status --porcelain
To git://git.gladex.de/gladex.git
   992e390..790cf47  main -> main
push rc=0
=== rev-list ===
0
=== git status --porcelain ===
> build · mimo-v2.6-flash-free
Pushed `790cf47`, rev-list → 0, tree clean. Now the post-push re-reads.
$ cd /data/repo
echo "=== queue-source-check ==="; ./tools/queue-source-check 2>&1 | head -3; echo "rc=$?"
echo "=== version-check ==="; ./tools/version-check 2>&1 | head -2
echo "=== inbox-status ==="; ./tools/inbox-status 2>&1 | tail -2
=== queue-source-check ===
queue-source-check: OK - one queue: [0.4.350] pointer-only, 111 item line(s) frozen across 304 section(s), 203 PROGRESS bullet(s), 2 path token(s)
rc=0
=== version-check ===
OK: dev=0.4.28 prod=0.4.28 (match)
=== inbox-status ===

verdict: OK - nothing owed (0 unread, 0 open entries all replied)
$ cd /data/repo
echo "=== bare ==="; tools/attribution-gap 2>&1 | tail -3; echo "rc=${PIPESTATUS[0]}"
echo "=== --all ==="; tools/attribution-gap --all 2>&1 | tail -2; echo "rc=${PIPESTATUS[0]}"
=== bare ===
attribution-gap  repo=/data/repo  since=7 days ago  window-day=2026-10-07
  7 transcript(s), 56 `identity .. shift` commit date(s)
  no attribution gap: every transcript touch-date is covered by an `identity <id> shift` commit
rc=0
=== --all ===
  7 transcript(s), 143 `identity .. shift` commit date(s)
  no attribution gap: every transcript touch-date is covered by an `identity <id> shift` commit
rc=0
> build · mimo-v2.6-flash-free
$ cd /data/repo
echo "=== leak ==="; bash tests/test_leak_figure_readers.sh 2>&1 | tail -2
echo "=== budget ==="; ./tools/budget-show 2>&1 | grep -E "spent|remaining|allowance" | head -3
echo "=== healthcheck prod ==="; curl -sSL -o /dev/null -w "%{http_code}\n" --max-time 20 https://gladex.de/healthcheck
echo "=== healthcheck dev ==="; curl -sSL -o /dev/null -w "%{http_code}\n" --max-time 20 https://dev.gladex.de/healthcheck
=== leak ===
leak-figure-readers suite: 41 passed, 0 failed
===============================
=== budget ===
  - 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.
=== healthcheck prod ===
200
=== healthcheck dev ===
200
$ cd /data/repo
bash tests/test_attribution_gap.sh 2>&1 | tail -2
attribution-gap suite: 80 passed, 0 failed
> build · mimo-v2.6-flash-free
$ cd /data/repo
./tools/repo-lint 2>&1 | tail -4
go-compile: 47 module file(s) compile clean (2.37s)
  changelog-version: 355 changelog version heading(s), 355 unique, 11105 citation(s) checked, 0 missing, 17944 bare token(s) counted
  elf-allowlist: 2 tracked ELF file(s), all shipped
result: all 219 linted file(s) parse clean (exit 0)
$ cd /data/repo
bash tests/test_gladex_monitor.sh > /tmp/opencode/run1137/monitor_post.log 2>&1
echo "=== monitor summary ==="; grep -E "^assertions:|^passed:|^failed:" /tmp/opencode/run1137/monitor_post.log
echo "=== failing rows ==="; grep -E "^FAIL" /tmp/opencode/run1137/monitor_post.log
=== monitor summary ===
assertions: 28
passed: 24
failed: 4
=== failing rows ===
FAIL A12 system-status verdict - checks in error: failed-units (kind=is key=sysverdict want=HEALTHY)
FAIL A30 no unit is left in systemctl --failed (kind=contains key=sys want=[OK] 0 failed unit(s))
FAIL A31 source-sync-check exits 0 (kind=rc key=sync want=0)
FAIL A32 the committed tree reached dev AND prod (kind=contains key=sync want=in sync)
> build · mimo-v2.6-flash-free
All post-push re-reads are in: queue-source-check `[0.4.350]` pointer-only rc 0, repo-lint **355/355 unique / 0 missing** (as predicted), attribution **80/0**, leak **41/0**, healthcheck 200/200, version 0.4.28 both, monitor down to 4 reds — A3/A4–A8/A15/A28 all cleared by the push; the four standing reds (A12/A30 mia+sofia, A31/A32 `b460155`'s undeployed `download.php`) belong to other seats. Now waiting for the first `*/15` red-watch tick after the push (~18:56Z) before the close-correction commit.
$ NEXT=$(date -u -d "$(date -u -d 'next 15 minutes' +%H:00:00)" +%s 2>/dev/null || date -u +%s)
NOW=$(date -u +%s)
# compute seconds until the next :00/:15/:30/:45 boundary
MOD=$(( (15*60) - (NOW % (15*60)) ))
echo "now=$(date -u +%H:%M:%SZ)  waiting ${MOD}s for the next */15 tick"
sleep $(( MOD + 20 ))
echo "=== ticks after push (790cf47) ==="
tail -2 /data/agent-logs/red-watch-20261014.log
date: invalid date ‘next 15 minutes’
now=19:02:17Z  waiting 763s for the next */15 tick
=== ticks after push (790cf47) ===
2026-10-14T18:45:02Z state=red monitor_exit=1 passed=17 failed=11 alert=RED-SET fails="FAIL A3 tree clean AND in sync with origin/main (kind=is key=git want=## main...origin/main) | FAIL A4 queue-source-check exits 0 (kind=rc key=qsc want=0) | FAIL A5 queue has exactly one home (kind=contains key=qsc want=queue-source-check: OK - one queue:) | FAIL A6 newest CHANGELOG queue is pointer-only (kind=contains key=qsc want=pointer-only) | FAIL A7 queue-source-check json exits 0 (kind=rc k"
2026-10-14T19:00:01Z state=red monitor_exit=1 passed=24 failed=4 alert=RED-SET fails="FAIL A12 system-status verdict - checks in error: failed-units (kind=is key=sysverdict want=HEALTHY) | FAIL A30 no unit is left in systemctl --failed (kind=contains key=sys want=[OK] 0 failed unit(s)) | FAIL A31 source-sync-check exits 0 (kind=rc key=sync want=0) | FAIL A32 the committed tree reached dev AND prod (kind=contains key=sync want=in sync)"
> build · mimo-v2.6-flash-free
The `19:00:01Z` tick — the first after the 18:56Z push — reads `passed=24 failed=4`, fails exactly A12, A30, A31, A32: A3/A4–A8/A15/A28 all cleared with the push, matching my own post-push monitor read exactly. Now the close-correction bullet, appended before commit #2 (rule 2).
← Edit repo/agent-logs/PROGRESS.md
Index: repo/agent-logs/PROGRESS.md
===================================================================
--- repo/agent-logs/PROGRESS.md
+++ repo/agent-logs/PROGRESS.md
@@ -19476,4 +19476,8 @@
 
 - **Queue — next small step (read this first):** **STEP 0 first every run** (today **0 unread dev / 0 prod**, `INBOX.md` **80/80/0 open** — an empty inbox is answered by the measurement). **This run closed `[0.4.349]`'s first priced item** (the window fix + section F's missing case + the live `--all`-vs-default agreement assertion), and in doing so **refused the false pass it exposed** (unreadable history → exit 3 in both modes). **NEW, re-queued unnumbered: the *hermetic* window is now day-granular, but the live default's `--since '7 days ago'` is still resolved by git's approxidate at call time** — so `window_open_day` can still shift across a midnight boundary *between* two runs of the same command (not a defect: both sets move together, and J5's subset assertion holds either way), and the honest next measurement is a **J5-shaped live assertion run twice ≥ 12 h apart** to confirm the day key moves without manufacturing a gap. **Also still open, unchanged:** run 952's **(i)** future-dated-footer guard (re-queued **only on a measured future-dated marker** — 332 scanned, 0 found) and **(iii)** run 951's `system-status` A12 wording (**only on a measured A12 misread** — the live row already names mia + sofia and the `work/ownlog/other` split); run 953's dispatcher-footer-coverage observation; **(93)**/**(97)(a)** first if the investor answers `hiring/queue/*.json` (**2 proposals**, unchanged since 2026-10-04 / 2026-09-30); **(2'')** the day the `GETTING_STARTED.md` keep/fold/retire answer arrives; **§14 renewal** cadence NEEDS-INVESTOR; the LAN-only A/B/C; NUL-blob watch on a measured harm only; **(av)(d)** after the `REPORT.md` §14 sign-off; **(i)** until the prune lands; SOA MNAME and Pip's mail-policy research NEEDS-INVESTOR; **(113)**'s two `cp`s operator-blocked; **2026-10-20** §10 #6 re-read; the `/stats` display row; and **(ax)**, **(e)**, the drift-verify line, **(aw)**, the `promote-gates` verdict watch, and run 915's monitor item — **A31/A32 now waiting on `b460155`'s `src/php/download.php` reaching dev and prod** (the dev-sync desk's, from `7f3166e`; this run promoted nothing). **V14b** (`shift-deploy` 132 vs 127) stays a **standing environmental red** owned by the stale-verdict gate, disclosed above.
 
 - **Close-state:** this entry is appended **before** the commit that carries it (CLOSE PROTOCOL rule 1) and is never `git checkout --`-ed, staged-only or parked in `/tmp` (rules 2–3); the stop-state check is `git status --porcelain` **not listing `agent-logs/PROGRESS.md`** after the commit. The push must leave `git rev-list --count origin/main..main` → **0**. Post-push re-reads (`queue-source-check` → rc 0 on `[0.4.350]` pointer-only, `repo-lint` → 355 headings / 0 missing, the attribution-gap suite, regcov, leak-figure, figread, the monitor, `inbox-status`, `version-check`, `budget-show`, `healthcheck`, `git status --porcelain`, `rev-list`) plus the first `*/15` red-watch tick after the push are recorded in the **close-correction** bullet appended before any close commit (rule 2).
+
+- **Close correction (appended before commit #2 — CLOSE PROTOCOL rule 2): `790cf47` pushed, ten post-push re-reads green except the reds this run does not own, and the first `*/15` red-watch tick after the push waited for — 17 → 24 passed.** Commit #1 by **explicit pathspec** — `git status --porcelain` read immediately before staging and it showed exactly the five paths (` M CHANGELOG.md`, ` M agent-logs/PROGRESS.md`, ` M tests/test_attribution_gap.sh`, ` M tools/REGISTRY.md`, ` M tools/attribution-gap`), `git diff --cached --name-only` after `git add <those five>` was those same five and nothing else — **never `git add -A`** on this shared index → `790cf47`, **5 files changed, 397 insertions(+), 39 deletions(-)**; `git status --porcelain` → **empty straight after it** (the entry is carried by commit #1, not left staged, not `git checkout --`-ed, not parked in `/tmp` — rules 1 and 3 hold, and `agent-logs/PROGRESS.md` is **not** in that reading); `git push origin main` → **rc 0, `992e390..790cf47`**, carrying the concurrent `992e390` alongside this run's commit; `git rev-list --count origin/main..main` → **0** — A3's condition, re-read at the close.
+- **Post-push re-reads, all on the pushed tree `790cf47`:** `./tools/queue-source-check` → **rc 0**, `one queue: [0.4.350] pointer-only, 111 item line(s) frozen across 304 section(s), 203 PROGRESS bullet(s), 2 path token(s)` — **R8 clear** (pointer moved `[0.4.349]` → `[0.4.350]`) and R10 satisfied by ancestry; `./tools/repo-lint` → **rc 0, `all 219 linted file(s) parse clean`**, **`355 changelog version heading(s), 355 unique, 11105 citation(s) checked, 0 missing, 17944 bare token(s) counted`** — **354 → 355 with `[0.4.350]`, as predicted and re-read rather than carried**, and **0 missing** discharges this entry's citations; `bash tests/test_attribution_gap.sh` → **rc 0, 80 passed / 0 failed** (re-run after the push); `bash tests/test_leak_figure_readers.sh` → **rc 0, 41 / 0**; `./tools/inbox-status` → **rc 0, `nothing owed`** — **STEP 0 still paid at the close, no `agent_to_investor` row written**; `./tools/version-check` → `OK: dev=0.4.28 prod=0.4.28 (match)`; `./tools/healthcheck` → **dev + prod HEALTHY, HTTP 200** (redirect-followed), both payloads `version 0.4.28`; `./tools/budget-show` → **2026-10, allowance 5.00 / spent 0.00 / remaining 5.00**; `git status --porcelain` → **empty** (does not list `agent-logs/PROGRESS.md`); `git rev-list --count origin/main..main` → **0**. Live attribution re-read after the push: bare → exit 0, `window-day=2026-10-07`, `56` shift dates, `no attribution gap`; `--all` → exit 0, `143`, `no attribution gap` — the two agree on `/data/repo` by construction, J5's live assertion.
+- **The first `*/15` tick after the push WAS waited for: `2026-10-14T19:00:01Z` → `state=red, monitor_exit=1, passed=24 failed=4, alert=RED-SET`** (push ≈ 18:56Z), fails exactly **A12, A30, A31, A32** — **17 → 24 passed** versus the 18:45:02Z pre-push tick (17/11), i.e. **A3, A4–A8, A15 and A28 all cleared with this push** exactly as the entry above predicted (A3/A15 the clean tree, A4–A8 `queue-source-check` on `[0.4.350]`, A28 the CHANGELOG+code-in-one-commit ordering). The four standing reds each belong to a seat this run does not own: **A12/A30** `identity-run@mia.service` + `identity-run@sofia.service` (`Model unavailable: opencode/ling-3.1-flash-free`, class `other-error`), left standing on purpose and **never** reset from this seat; **A31/A32** `source-sync-check --env both` DRIFT on `src/php/download.php` — `b460155`'s repo commit reached **no** environment (dev-sync desk's, from `7f3166e`). `bash tests/test_gladex_monitor.sh` on the pushed tree → **28 assertions, 24 passed, 4 failed** (`/tmp/opencode/run1137/monitor_post.log`), the four exactly those same rows. `alert=RED-SET` is the standing set, recorded so a reader of `red-watch-ALERTS.log` does not meet a RED on a run that closed nine rows. **This close commit carries `agent-logs/PROGRESS.md` only** (no `tests/` or `tools/` file), so A28's window stays closed through it. **Stop-state: `git status --porcelain` does not list `agent-logs/PROGRESS.md`; the close ends with `git rev-list --count origin/main..main` → 0.** Spend **0.00**, free `*-free` models only.

> build · mimo-v2.6-flash-free
$ cd /data/repo
echo "=== git status --porcelain (immediately before staging commit #2) ==="; git status --porcelain
echo "=== rev-list ==="; git rev-list --count origin/main..main
=== git status --porcelain (immediately before staging commit #2) ===
 M agent-logs/PROGRESS.md
=== rev-list ===
0
> build · mimo-v2.6-flash-free
Only `agent-logs/PROGRESS.md` is modified — the close-correction commit carries that one file, keeping A28's window closed.
$ cd /data/repo
git add agent-logs/PROGRESS.md
echo "=== staged ==="; git diff --cached --name-only
git commit -m "run 960 close correction: post-push re-reads green, 355 headings / 0 missing, monitor 24/4 (A12/A30 mia+sofia, A31/A32 b460155 undeployed), first */15 tick 19:00:01Z 17->24 passed" -- agent-logs/PROGRESS.md
echo "=== log ==="; git log --oneline -2
echo "=== status straight after ==="; git status --porcelain
=== staged ===
agent-logs/PROGRESS.md
[main 5cd1546] run 960 close correction: post-push re-reads green, 355 headings / 0 missing, monitor 24/4 (A12/A30 mia+sofia, A31/A32 b460155 undeployed), first */15 tick 19:00:01Z 17->24 passed
 1 file changed, 4 insertions(+)
=== log ===
5cd1546 run 960 close correction: post-push re-reads green, 355 headings / 0 missing, monitor 24/4 (A12/A30 mia+sofia, A31/A32 b460155 undeployed), first */15 tick 19:00:01Z 17->24 passed
790cf47 run 960: attribution-gap window opens on a DAY boundary so the default and --all agree by construction; refuses an unreadable history (exit 3) instead of printing a clean verdict; suite 58 -> 80; CHANGELOG [0.4.350]
=== status straight after ===
> build · mimo-v2.6-flash-free
$ cd /data/repo
git push origin main 2>&1 | tail -3; echo "push rc=${PIPESTATUS[0]}"
echo "=== rev-list ==="; git rev-list --count origin/main..main
echo "=== git status --porcelain ==="; git status --porcelain
To git://git.gladex.de/gladex.git
   790cf47..5cd1546  main -> main
push rc=0
=== rev-list ===
0
=== git status --porcelain ===
> build · mimo-v2.6-flash-free
Run 960 is closed. Both commits are pushed, `rev-list` is 0, and `git status --porcelain` is clean.

## Summary

**The step (run 959's queued item):** `tools/attribution-gap`'s default `--since` window now opens on a **day boundary** — `window_open_day()` resolves the date via git's own parser and both the shift-commit set and the touch-day set are cut client-side on the author-day key, so the bare default and `--all` agree by construction instead of by where the clock sits inside a day. An empty window uses the `EMPTY_WINDOW_DAY` sentinel; an unresolvable window is exit 3.

**The extra hole, found and fixed while writing the missing case:** on a repo whose every `git log` fails, the old tool printed `no attribution gap` exit 0 — a clean verdict over history it had never read. `window_open_day()` now probes readability for `--all` too; both modes refuse with exit 3.

**Suite:** 58 → **80** assertions (`80 passed / 0 failed`, rc 0, 5.5 s). Negative control vs the pre-fix tool = **61 passed / 12 failed**. Registry `## attribution-gap` section refreshed in step (`**Tests**` 58→80, new window paragraph, widened exit-3 bullet, dated live reading); `- Live:` stays 114, C28g 30 / G38 27 unchanged (no new flags).

**Live readings:** bare → `window-day=2026-10-07`, `56` shift dates, `no attribution gap`; `--all` → `143`, `no attribution gap` — they agree.

**Commits:**
- `790cf47` — the fix + suite + registry + `CHANGELOG.md [0.4.350]` + PROGRESS entry (5 files, 397+/39−)
- `5cd1546` — the close-correction bullet (PROGRESS only, keeps A28 closed)

**Close-state:** queue-source-check `[0.4.350]` pointer-only rc 0; repo-lint **355 headings / 355 unique / 0 missing**; attribution 80/0, leak 41/0, regcov 497/0; version 0.4.28 both; healthcheck 200/200; budget 5.00/0.00/5.00; monitor **24 passed / 4 failed**; first `*/15` tick after push (`19:00:01Z`) **17 → 24 passed**, the four standing reds all other seats' (A12/A30 mia+sofia, A31/A32 `b460155`'s undeployed `download.php`). STEP 0 paid first and at the close — 0 owed, no row written. Spend 0.00.
exit=0

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

[Wed Oct 14 22:01:51 2026] 127.0.0.1:55010 Accepted
[Wed Oct 14 22:01:51 2026] 127.0.0.1:55010 Closing
[Wed Oct 14 22:01:51 2026] 127.0.0.1:55016 Accepted
[Wed Oct 14 22:01:51 2026] 127.0.0.1:55016 Closing
[Wed Oct 14 22:01:52 2026] 127.0.0.1:55030 Accepted
[Wed Oct 14 22:01:52 2026] 127.0.0.1:55030 Closing
[Wed Oct 14 22:01:52 2026] 127.0.0.1:55036 Accepted
[Wed Oct 14 22:01:52 2026] 127.0.0.1:55036 Closing
[Wed Oct 14 22:01:53 2026] 127.0.0.1:55046 Accepted
[Wed Oct 14 22:01:53 2026] 127.0.0.1:55046 Closing
[Wed Oct 14 22:01:53 2026] 127.0.0.1:55060 Accepted
[Wed Oct 14 22:01:53 2026] 127.0.0.1:55060 Closing
[Wed Oct 14 22:01:54 2026] 127.0.0.1:55076 Accepted
[Wed Oct 14 22:01:54 2026] 127.0.0.1:55076 Closing
[Wed Oct 14 22:01:55 2026] 127.0.0.1:33656 Accepted
[Wed Oct 14 22:01:55 2026] 127.0.0.1:33656 Closing
[Wed Oct 14 22:01:55 2026] 127.0.0.1:33662 Accepted
[Wed Oct 14 22:01:55 2026] 127.0.0.1:33662 Closing
[Wed Oct 14 22:01:56 2026] 127.0.0.1:33678 Accepted
[Wed Oct 14 22:01:56 2026] 127.0.0.1:33678 Closing
[Wed Oct 14 22:01:57 2026] 127.0.0.1:33680 Accepted
[Wed Oct 14 22:01:57 2026] 127.0.0.1:33680 Closing
[Wed Oct 14 22:01:57 2026] 127.0.0.1:33696 Accepted
[Wed Oct 14 22:01:57 2026] 127.0.0.1:33696 Closing
[Wed Oct 14 22:01:58 2026] 127.0.0.1:33702 Accepted
[Wed Oct 14 22:01:58 2026] 127.0.0.1:33702 Closing
[Wed Oct 14 22:01:58 2026] 127.0.0.1:33718 Accepted
[Wed Oct 14 22:01:58 2026] 127.0.0.1:33718 Closing
[Wed Oct 14 22:01:59 2026] 127.0.0.1:33728 Accepted
[Wed Oct 14 22:01:59 2026] 127.0.0.1:33728 Closing
[Wed Oct 14 22:01:59 2026] 127.0.0.1:33740 Accepted
[Wed Oct 14 22:01:59 2026] 127.0.0.1:33740 Closing
[Wed Oct 14 22:02:00 2026] 127.0.0.1:33752 Accepted
[Wed Oct 14 22:02:00 2026] 127.0.0.1:33752 Closing
[Wed Oct 14 22:02:01 2026] 127.0.0.1:33766 Accepted
[Wed Oct 14 22:02:01 2026] 127.0.0.1:33766 Closing
[Wed Oct 14 22:02:02 2026] 127.0.0.1:33768 Accepted
[Wed Oct 14 22:02:02 2026] 127.0.0.1:33768 Closing
[Wed Oct 14 22:02:02 2026] 127.0.0.1:33772 Accepted
[Wed Oct 14 22:02:02 2026] 127.0.0.1:33772 Closing
[Wed Oct 14 22:02:03 2026] 127.0.0.1:33788 Accepted
[Wed Oct 14 22:02:03 2026] 127.0.0.1:33788 Closing
[Wed Oct 14 22:02:03 2026] 127.0.0.1:33790 Accepted
[Wed Oct 14 22:02:03 2026] 127.0.0.1:33790 Closing
[Wed Oct 14 22:02:04 2026] 127.0.0.1:33792 Accepted
[Wed Oct 14 22:02:04 2026] 127.0.0.1:33792 Closing
[Wed Oct 14 22:02:05 2026] 127.0.0.1:51346 Accepted
[Wed Oct 14 22:02:05 2026] 127.0.0.1:51346 Closing
[Wed Oct 14 22:02:06 2026] 127.0.0.1:51350 Accepted
[Wed Oct 14 22:02:06 2026] 127.0.0.1:51350 Closing
[Wed Oct 14 22:02:06 2026] 127.0.0.1:51358 Accepted
[Wed Oct 14 22:02:06 2026] 127.0.0.1:51358 Closing
[Wed Oct 14 22:05:17 2026] 127.0.0.1:40088 Accepted
[Wed Oct 14 22:05:17 2026] 127.0.0.1:40088 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Oct 14 22:05:17 2026] 127.0.0.1:40088 Closing
[Wed Oct 14 22:05:18 2026] 127.0.0.1:40098 Accepted
[Wed Oct 14 22:05:18 2026] 127.0.0.1:40098 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Oct 14 22:05:18 2026] 127.0.0.1:40098 Closing
[Wed Oct 14 22:05:59 2026] 127.0.0.1:37430 Accepted

Other app logs: downloads.log