client-reliability-4 dispatch-2: route reproduced queued URL cancellation fix

docs/TODO.md

@@ -2,6 +2,9 @@
 
 ## dispatch
 
+- 2026-10-20: item4 reproduction confirmed independently: obsolete URL media starts1(expected0), shared owner control pass. Worker routed to queued URL ownership/cancellation in observer/controller and focused tests. Remaining: implementation, mutant/full/browser gates, landing, preview refresh; active abort excluded.
+
+
 - 2026-10-20: item4 assigned to existing worker for investigation only: reproduce remaining URL/active torrent cancellation at HEAD, then route a narrow fix. No product fix yet; live playback/CPU-RSS remain unverified. Owner continuation relayed; quiet-hours exception does not change schedule.
 
 

docs/agents/prompts/client-reliability.md

@@ -1,6 +1,18 @@
 # Area: Client reliability (client-reliability)
 
-## Current assignment: client-reliability-4 — investigation only
+## Current 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.
+
+Implementation now authorized for item4. Temporary explicit ownership: js/urlHealthObserver.js, js/ui/urlHealthController.js, focused URL lifecycle tests, relevant existing URL health tests, Test Integrity Note and area evidence/backlog notes. Use existing onCardUnregister boundary. No shared cardObserver/VideoListView/app/state-cache module changes without evidence and routing. No HEAD/active media abort, HLS/torrent changes, cache policy/TTLs, mirror order, concurrency, signers, kit or styling changes. Existing callback consumers must remain compatible without editing app.js. If that cannot work safely, report before broadening.
+
+Before edits read current rules and test-integrity standard, merge unstable and preserve investigation notes. Retain a real observer→controller→queue regression with controlled external IO. Cancel queued work only after its last live owner disappears; settle cancellation without negative cache, mirror fallthrough, stale UI mutation or deleting newer inflight records. Preserve live shared owners and existing event/source/playable-mode dedup; later same-source registrations can retry. Keep three-media concurrency and healthy hidden-card reveal. Already-active probes retain prior lifecycle/cache behavior.
+
+Verify last-owner obsolete starts0, shared live owner remains healthy, cancellation settlement and same-source retry, disposed/reused registration stale callbacks, mirror order, concurrency and hidden-card reveal. Every new scenario needs a deliberately broken mutant that fails; preserve assertions and no sleeps/retries. Run focused suites, npm run lint, full npm test with existing60s/file diagnostic bound, npm run build/artifact check and local Chromium/Firefox controlled lifecycle/source-health smoke if available (reserve browser in .task). Report actual playback/fallback gaps; do not claim CPU/RSS benefit from probe counts.
+
+Commit with item4 id, merge unstable (never rebase), verify merged tree and normal landing gate. Durable landed status plus unstable ancestry before close. Send dispatch mailbox on blocker, product landing and final completion including SHA/checks/counts/unverified scope; dispatch owns independent verification and preview refresh. No further item without routing. No subagents needed. No deploy/push/spend/wallet/production-data/scheduler/kit changes.
+
+## Archived investigation: client-reliability-4
 
 Owner continuation relayed by interpreter on 2026-10-20 explicitly permits this bounded step during quiet hours. No recurring schedule/config change.
 

fleet/LOG.md

@@ -49,3 +49,5 @@
 
 - Interpreter relays owner: "ok lets continue development. Whats being worked on? And whats next?" Requested continuation is a quiet-hours exception only; approval limits unchanged. Same single worker assigned item4 investigation: reproduce URL queued/active or torrent active cancellation at HEAD before any product fix. Dispatch owns scoping/landing/preview, worker owns reproduction/evidence; no new worker. Next candidate is the narrowest demonstrated URL queued-owner defect; no defect assumed.
 - Item3 landing7d20a509 remains durable and ancestor of unstable604c8c61. Prior426-file validation is evidence-derived, not rerun. Remaining: reproduction, fix routing, actual playback/live peers/CPU-RSS qualification.
+
+- Item4 evidence accepted: dispatch independently ran last-owner --expect-fixed at604c8c61, exit1 with obsolete starts1!=0 after cleanup; shared-owner exit0, live badge healthy, settled4/active0/queued0. Routed same worker to queued URL cancellation fix in observer/controller plus focused tests. Active abort excluded. No product change landed or playback/CPU qualification yet.

fleet/RULE-CHANGES.md

@@ -9,6 +9,9 @@ a landing rule changes.
 
 ## 2026-10-20
 
+- 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.
+
+
 - Owner continuation relayed by interpreter permits the requested bounded development step now despite quiet hours; recurring schedule/config unchanged. client-reliability-4 is read-only source-health cancellation reproduction at current HEAD, evidence notes only. Product/test fixes require dispatch routing after reproduction; mailbox tools now deliver short wakes, superseding prior no-wake limitation for updated runtime. No unattended monitoring claim.
 
 ## 2026-10-19

test_logs/TEST_LOG_2026-10-20_03-09-00_dispatch-url-reproduction.md

@@ -0,0 +1,6 @@
+# Dispatch URL cancellation reproduction
+
+- Code HEAD604c8c61, worker reproduction copied to /tmp/bitvid-dispatch-4-url-lifecycle.mjs with root redirected to dispatch. Real controller/observer/cache, controlled fetch/media boundaries, no public traffic.
+- node /tmp/bitvid-dispatch-4-url-lifecycle.mjs last-owner --expect-fixed: exit1, natural assertion1!==0 after cleanup. Before4 HEAD/3 active/1 queued; disposal retains queue; release starts1 obsolete media. Final settled4/active0/queued0.
+- node /tmp/bitvid-dispatch-4-url-lifecycle.mjs shared-owner: exit0, live badge healthy, settled4/active0/queued0.
+- No lint/full/browser tests rerun for reproduction; no product edits. Active abort/playback/CPU-RSS unverified.