dispatch-2: record parallel pickups, outputs and resource interventions

fleet/LOG.md

@@ -74,3 +74,7 @@
 - Clean roster47953970 durable landedbbc1be79 at13:37:27, normal gate exit0; initial submission13:26:20, rejection13:28:15, environment-corrected retry13:30:35 (full gate~6m53s). No gate/test/kit change. Created worktrees bitvid-storage-cors/bitvid-playback-qa and launched clean-env windows pid249026/pid249041 ~13:38UTC. Host status confirms4 alive windows; storage read/next-action13:38:24 verified, QA acknowledgment pending. Current routingf3c0ffd3 second conservative admin full gate adds serial resource delay; item5 full request13:32:54 remains queued.
 
 - storage-cors pickup13:38:24, concrete offline loss report13:39:21 (~57s later). Independent dispatch strict reproduction exits1 existing origin false!=true,5 characterization controls complete, no network. Routed preserve-verbatim rules/new default uncovered-origins/no-read-failure overwrite/idempotence to owned helper+SDK export/new test. QA .task records local fallback investigation start13:38:36, mailbox read/next-action event still pending; no browser opened.
+
+- QA pickup/proposal13:39:50 received/consumed13:41; actual coordinator/strategy/service scratch3/3. Reviewed local native Chromium+Firefox3 scenarios each, VP8 dimensions64x64/currentTime>0 on actual mirror and substituted torrent IO;0external. Product/existing tests read-only. Approved new dependency-free regression retention with meaningful mutants; no live WebTorrent/peers/full-app claim.
+- QA coordination intervention: ran browsers during administrative gate before reading explicit wait mail/awaiting dispatch clearance, then self-reported and closed owned browser/server. No browser errors observed does not prove no contention; remaining browsers serialized. All3 read/next-action events now verified, storage implements demonstrated origin loss, client ready waiting full, QA retaining regression.
+- Suggested future kit consideration only (not implemented): surface NODE_TEST_CONTEXT/capture failures directly; distinguish stale rejected result from in-flight same-SHA retry; compute docs-only delta at drain time to avoid conservative duplicate admin gates. These gaps cost measurable trial latency. No kit/scheduler change.