diff --git a/docs/TODO.md b/docs/TODO.md index aabbbbbf..db184bb1 100644 --- a/docs/TODO.md +++ b/docs/TODO.md @@ -2,6 +2,9 @@ ## dispatch +- 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. + + - 2026-10-19 latest: item3 normal product landing7d20a509 and closure7fde734d verified; dispatch synced and preview rebuilt(HTTP200). Independent original five-card scenario now0 obsolete starts(previous1), lifecycle11/11. Worker evidence426/426 full files,lint11/11,14 rejected mutants,Chromium+Firefox controlled-IO lifecycle smoke. Worker idle; no new task launched in this mail checkpoint. Remaining: actual media fallback/live-peer qualification,CPU/RSS measurements,active-probe/URL cancellation and other performance-plan slices. diff --git a/docs/agents/backlog/client-reliability-4.json b/docs/agents/backlog/client-reliability-4.json new file mode 100644 index 00000000..a0f79de3 --- /dev/null +++ b/docs/agents/backlog/client-reliability-4.json @@ -0,0 +1,9 @@ +{ + "id": "client-reliability-4", + "area": "client-reliability", + "status": "open", + "title": "Reproduce remaining source-health cancellation defect at current HEAD before scoping a fix", + "blockedOn": null, + "addedOn": "2026-10-20", + "filedAt": "604c8c61f4783717eb0cff7ca7ca33efb59aac8a" +} diff --git a/docs/agents/prompts/client-reliability.md b/docs/agents/prompts/client-reliability.md index 95c33c0e..d432c801 100644 --- a/docs/agents/prompts/client-reliability.md +++ b/docs/agents/prompts/client-reliability.md @@ -1,6 +1,14 @@ # Area: Client reliability (client-reliability) -## Current assignment: client-reliability-3 +## Current assignment: client-reliability-4 — investigation only + +Owner continuation relayed by interpreter on 2026-10-20 explicitly permits this bounded step during quiet hours. No recurring schedule/config change. + +Claim item4 after merging unstable. Read RULE-CHANGES, KNOWN_ISSUES and docs/performance-efficiency-plan.md Stage3. At current HEAD reproduce whether disposed feeds retain/start URL-health queued or active probes, or active torrent probes. Inspect js/urlHealthObserver.js, js/ui/urlHealthController.js, js/gridHealth.js and js/webtorrent.js read-only. Prefer the URL queued-owner case first; old plan concurrency and lifecycle claims may be stale. Use actual observer/controller entry points with deterministic deferred external IO boundaries and no public network. Preserve shared live-owner behavior. Measure started, queued, disposed and settled counts; record exact command, SHA, expected/actual and natural exit. Do not infer a defect merely from missing AbortSignal. + +This assignment authorizes investigation and scratch/evidence notes only: no product or committed regression-test changes yet, no test weakening, no browser reservation unless needed, no broad Stage3 implementation. Report the smallest reproduced defect plus proposed files/acceptance to dispatch before fixing. If not reproducible, record why and return the next evidenced TODO candidate for routing. Commit evidence/backlog notes separately through normal queue if needed. Send mailbox on blocker and final investigation result; current mailbox tools deliver a short wake, so archived text below claiming no wake is historical. No subagents needed. No deploy/push/spend/wallet/production-data/scheduler/kit changes. Preserve preview3000. Existing completed item3 evidence follows for context; do not redo it or follow its old implementation steps. + +## Archived completed assignment: client-reliability-3 Improve robustness/usability with one bounded client-facing fix from pre-launch TODO #34 Stage3: cancel queued torrent health probes when the last card/feed owner is disposed. Prior items1 and2 are done, normally landed at de6918ce and closed at f9adfc8f (425/425 unit files, lint11/11). Do not redo them. diff --git a/fleet/LOG.md b/fleet/LOG.md index 72b8be86..0196478b 100644 --- a/fleet/LOG.md +++ b/fleet/LOG.md @@ -44,3 +44,8 @@ - Dispatch independently reran the original actual five-card reproduction:4 active,observer disconnected,0 obsolete starts after disposal (baseline1); exit0. Landed lifecycle suite11/11,exit0 naturally,309.36ms. Dispatch npm run build including artifact verification exit0; previewHTTP200, existing server preserved. - Not verified: actual media fallback/live peers,CPU/RSS benefit,active abort/URL cancellation,whole Stage3,signer/wallet/production. One worker now idle with empty backlog; next ownership/cancellation slices remain unassigned until bounded evidence/scoping. No deploy/spending/scheduler/kit changes. - Completion reporting now worked: two evidence messages were delivered and read. This new-mail turn resumed dispatch; file-mailbox code still has no session-wake behavior, so no unattended-monitoring claim. + +## 2026-10-20 — Owner resumes bounded development + +- 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. diff --git a/fleet/RULE-CHANGES.md b/fleet/RULE-CHANGES.md index 14ec8445..a94e438b 100644 --- a/fleet/RULE-CHANGES.md +++ b/fleet/RULE-CHANGES.md @@ -7,6 +7,10 @@ override a stale system prompt. Nothing filters them down to a window of days. The session manager adds a line here whenever a rule, a prompt, a tool's usage, or a landing rule changes. +## 2026-10-20 + +- 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 - client-reliability-3 redirects the existing single worker to queued torrent-probe ownership in js/gridHealth.js, an optional small queue helper, and focused lifecycle tests. Prior validation tasks are done. Active probes, URL checks, WebTorrent implementation, cache/concurrency policy and kit remain out of scope. Completion must send dispatch mailbox evidence; mailbox delivery is not a session wakeup. No scheduler/kit changes.