dispatch-2 client-reliability-2: route retained relay cleanup to existing worker

This commit is contained in:
thePR0M3TH3AN committed 2026-10-19 16:20:10 -04:00
1 parent f303ab0e72
commit 16f6dca41e
8 files changed
+44 -1

No files matched your search

+2
View File
@@ -2,6 +2,8 @@
## dispatch
- 2026-10-19 checkpoint: reviewed dbdac18d/6da037f5, independently verified profile-modal27/27 in2.46s and isolated race assertion62ms/process timeout10s. Routed client-reliability-2 to the existing worker for one-test harness cleanup. Preserve separate commits and normal full gates; no preview rebuild before verified landing.
- 2026-10-19: dispatch-1 startup goal and one-worker proposal landed at fa538097; preparation complete. Baseline at d9059116: lint 11/11, unit run completed 219 files before profile-modal suite timed out at 60s; isolated unrestricted rerun reproduced timeout; 205 files remain untested. fleet/TEAM-PROPOSAL.md proposes one client-reliability worker for this blocker, with queued torrent-probe lifetime as a later candidate. Await first-worker approval before adding/launching it. No product edits or workers started.
- 2026-10-19: dispatch-2: first worker approved through desktop-chat relay, routine local work authorized within GOAL. Roster landed at 9e6c310d and client-reliability worker launched in its own tmux window (pid 138193); fleet-bitvid:preview on port 3000 preserved (HTTP 200). Next: monitor blocker/fix evidence, normal landings, and refresh preview after verified product changes. A clean NODE_TEST_CONTEXT-free isolated reproduction also timed out at 60s; one-time roster-only validation is recorded in PROGRAM.md. No product fixes landed yet.
+3 -1
View File
@@ -9,7 +9,7 @@ Read fleet/GOAL.md and PROGRAM.md. Robustness/usability/TODO work is authorized.
| area | item | state | next step |
| --- | --- | --- | --- |
| dispatch | dispatch-2 | active coordination | roster landed 9e6c310d; one worker running; monitor results, owner updates, and preview refresh |
| client-reliability | client-reliability-1 | running in fleet-bitvid:client-reliability | classify/fix reproducible profile-modal suite timeout, preserve assertions, mutation-check regression and run full gates |
| client-reliability | client-reliability-1 and client-reliability-2 | profile fix committed dbdac18d/6da037f5; follow-up routed | merge updated prompt; fix retained relay work in the race test, then normal full gate before landing |
## Evidence and local preview
@@ -20,3 +20,5 @@ Preserve fleet-bitvid:preview serving dispatch dist at http://127.0.0.1:3000. Af
## Bootstrap exception
One administrative roster/brief commit uses temporary exact-scope validation because the worker's assigned existing hang blocks full-suite completion. Persistent gate settings, product code, and tests must be unchanged. Subsequent code uses normal full gates. No additional owner approval pending within routine scope.
Latest checkpoint: independent profile-modal27/27 in2.46s. Worker full run226 file exits before race-suite retained relay work;198 untested. Independent isolated race assertion62ms, process timeout10s/exit124. Preview unchanged; no test fix landed yet.
@@ -0,0 +1,9 @@
{
"id": "client-reliability-2",
"area": "client-reliability",
"status": "open",
"title": "Make Nostr initialization race test hermetic and release retained relay work",
"blockedOn": null,
"addedOn": "2026-10-19",
"filedAt": "f303ab0e72ac60b49c5e1bd712b080de2a95a483"
}
+10
View File
@@ -1,5 +1,15 @@
# Area: Client reliability (`client-reliability`)
## Current bounded follow-up: client-reliability-2
Dispatch grants temporary ownership of tests/race/nostr-client-init-race.test.mjs, its Test Integrity Note, and client-reliability-2 backlog/notes. This extends the initial scope; no second worker or Nostr product-code ownership is granted. Merge unstable to receive this prompt and item before claiming it. Keep the existing profile-modal commits separate. Both items await normal full-gate success before landing.
Evidence: race assertion passes in about 61ms but the process retains public-relay retries and exceeds isolated 10s/full-run 60s diagnostic bounds. Dispatch independently reproduced this (assertion 62ms, process exit124), and independently verified your profile-modal tree 27/27 in2.46s.
Inspect the real post-init subscription boundary and cleanup. Make the harness hermetic, preserve concurrent-init/pool-ready/post-init-subscription assertions, and exit naturally without public relay traffic or retry timers. Read docs/nips/01.md and relevant subscription/lifecycle documentation before Nostr-related investigation. Product Nostr code, shared helpers, and the global runner remain excluded; report exact evidence/file needs before broader edits.
No force-exit, unref-only masking, retries, added sleeps, loose assertions, quarantine, or timeout increases. A deterministic deferred barrier may replace the existing mock delay if appropriate. Pin the actual boundary with a regression and deliberately broken variant; record the integrity note. Run the race file to natural completion, the profile-modal suite, lint, and then full npm test with the existing diagnostic bound. Commit separately with client-reliability-2, merge unstable, verify that tree, and submit through unchanged normal landing gates once the full suite is green. Route any further unowned blocker with exact counts instead of broadening yourself.
## Role and first assignment
Improve client robustness and usability through small, reproducible fixes from the TODO backlog. Start with client-reliability-1: classify and fix the profile-modal controller suite hang, then report before picking a different subsystem. You are the only worker; dispatch owns staffing and priorities.