dispatch-2 client-reliability-5: continue bounded active probe investigation

docs/TODO.md

@@ -2,6 +2,9 @@
 
 ## dispatch
 
+- 2026-10-20: continuing owner direction: item5 investigation assigned to same worker, active URL media last-owner/shared-owner controls first. Remaining: reproduction and narrow fix routing or next evidenced TODO. No product fix assumed; active abort/live playback/CPU-RSS unverified.
+
+
 - 2026-10-20: item4 done: product89ccb907,closuref116f7c8 durable landed. Dispatch independent URL tests20/20,build/artifact exit0,previewHTTP200 and index matches dist. Worker full427/427,focused22,13 mutants,lint11,browser smoke recorded. Worker idle; next active-probe candidate needs fresh reproduction/routing. Actual playback/live peers/CPU-RSS/full Stage3 unfinished.
 
 

docs/agents/backlog/client-reliability-5.json

@@ -0,0 +1,9 @@
+{
+  "id": "client-reliability-5",
+  "area": "client-reliability",
+  "status": "open",
+  "title": "Reproduce remaining active URL or torrent probe lifecycle defect before scoping a fix",
+  "blockedOn": null,
+  "addedOn": "2026-10-20",
+  "filedAt": "3f627f5df3da7bcd28d910d9f8161844fa77ff74"
+}

docs/agents/prompts/client-reliability.md

@@ -1,6 +1,14 @@
 # Area: Client reliability (client-reliability)
 
-## Current assignment: client-reliability-4 — queued URL probe fix
+## Current assignment: client-reliability-5 — active probe investigation
+
+Interpreter checkpoint2026-10-20 confirms continuing development under existing direction. Claim item5 after non-destructive merge of unstable. Read RULE-CHANGES, KNOWN_ISSUES, PROGRAM, and performance-efficiency-plan Stage3. Items3/4 are completed: queued torrent/URL cancellation shipped; do not repeat their full qualification.
+
+Investigate active URL/torrent probe lifecycle at HEAD. Start with actual URL observer→controller last-owner disposal during active media work; compare a shared live-owner control, completion/cleanup and a later same-source request. Controlled external fetch/media events only; no public traffic. Measure active resource retention, settlement, slot release and stale/cache effects before disposal, after disposal and after controlled completion. Distinguish bounded timeout behavior and intentional active caching from a demonstrated resource/lifecycle defect; missing AbortSignal alone is insufficient. Inspect active HEAD/HLS/torrent read-only only if needed to identify the smallest next defect. No assumption the old plan is current.
+
+Investigation/evidence only: no product edits, no committed regression changes, no policy/limits/TTL tuning. Scratch diagnostics and your evidence/backlog notes permitted. Send dispatch exact HEAD, reproduction command, expected/actual counts, failing assertion/natural exit after cleanup, shared-owner control, smallest proposed fix files and acceptance. Dispatch will independently assess and route implementation. If no defect reproduces, report an evidence-backed next TODO candidate rather than speculate or silently stop. Preserve dirty/queued work. No subagents needed. No deploy/push/spend/wallet/production-data/scheduler/kit changes; preview3000 preserved. Mailbox event on blocker and completed investigation. Archived briefs below are historical, not new work authorization.
+
+## Archived completed assignment: client-reliability-4 — queued URL probe fix
 
 Investigation is complete: at4c54858c real observer/controller/cache gives4 HEAD requests,3 active media probes and1 queued. Dispose/remove last feed then release a slot: obsolete media starts1(expected0); --expect-fixed naturally fails exit1 after cleanup. Shared live-owner control passes exit0, healthy badge, settled4/active0/queued0. Dispatch independently reproduced both against dispatch code at604c8c61 using /tmp/bitvid-dispatch-4-url-lifecycle.mjs. No public IO. Your detailed investigation evidence remains authoritative for fixture details.
 

fleet/LOG.md

@@ -57,3 +57,8 @@
 - Durable product submission7055496b landed89ccb907; closure94676453 landedf116f7c8, backlog done. Worker evidence427/427 full files,22 focused,13 reverted mutants,lint11/11,build/artifact and native Chromium+Firefox controlled IO smoke. These full/browser counts are worker-derived, not dispatch reruns.
 - Dispatch synced product89ccb907; direct Node focused lifecycle12/12,mirrors4/4,controller4/4 exit0. Initial inherited NODE_TEST_CONTEXT skipped tests; discarded that apparent success and reran direct files with env unset. Build+artifact exit0. Sandbox HTTP namespace returned000; authorized host localhost check returned200 and served index matched dist byte-for-byte (cmp exit0). Existing server untouched.
 - Product fixes obsolete queued URL starts1→0, preserves shared live owners/retry/mirrors/concurrency/hidden reveal. No active HEAD/media/HLS/torrent abort, actual decoding/playback fallback/live peers,CPU-RSS/full Stage3 qualification. Worker idle; no new item assigned. Next remaining candidate is active-probe cancellation, requiring fresh reproduction and bounded routing.
+
+## 2026-10-20 — Continue active probe investigation
+
+- Interpreter checkpoint continues owner development direction; same single worker assigned item5 read-only active probe reproduction, prioritizing active URL media last-owner/shared-owner controls. No new worker or product fix scope yet. Dispatch will assess evidence and route smallest demonstrated defect; absent a defect choose next evidenced TODO.
+- MCP mailbox_read stalled; terminated its wait, global fleet mailbox read consumed the actual instruction successfully. CLI fallback used, no pane scraping/kit changes. Item4 dispatch evidence is durable3f627f5d, not still queued as earlier handoff wording said. Full/browser validation remains prior worker-derived; no repeat tests for administrative assignment.

fleet/RULE-CHANGES.md

@@ -9,6 +9,9 @@ a landing rule changes.
 
 ## 2026-10-20
 
+- client-reliability-5 assigned to existing worker: read-only active URL/torrent cancellation reproduction at current HEAD, starting active URL media last-owner/shared-owner controls. Evidence notes only; product/test changes need demonstrated defect and dispatch routing. Continue selecting bounded next actions under existing owner direction; no new routine approval required. No scheduler or external authority change.
+
+
 - client-reliability-4 reproduced queued URL media work after last-feed disposal (obsolete starts1, expected0); dispatch independently confirmed failure and shared-owner control. Investigation restriction superseded for bounded implementation: urlHealthObserver.js, ui/urlHealthController.js, focused tests/integrity/evidence. Active abort, HEAD/HLS/torrent, shared observer/app/cache modules, limits/TTLs remain excluded. Normal gates and durable landing required.