Merge branch 'unstable' into area/playback-qa

docs/TODO.md

@@ -2,6 +2,12 @@
 
 ## dispatch
 
+- 2026-10-20 trial current: all3 pickups verified; admin notes durableb922c186. Client item5 owns exclusive full/browser/product landing from13:43:51 (~10m57s wait); storage CORS ready9/9+8mutants,next slot; QA retained4/4+6mutants,third slot,browser released. Remaining: full merged-tree validation,durable product/test landings,preview refresh and final trial outcome. No real cloud/peers/CPU qualification.
+
+
+- 2026-10-20 parallel trial: rosterbbc1be79 durably green,3 workers launched/read-next-action verified. Item5 ready12f92732 focused28/6mutants/lint/build awaits full+browser; storage-cors real origin loss independently reproduced/fix routed; playback-qa controlled native local fallback3/browser reviewed,test retention approved. Remaining trial product/test full gates,orderly durable landings and preview; actual WebTorrent/live peers/CPU unverified. Initial gate transport/capture failure corrected only by clean environment; QA browser coordination deviation recorded.
+
+
 - 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.
 
 

docs/agents/prompts/client-reliability.md

@@ -1,6 +1,14 @@
 # Area: Client reliability (client-reliability)
 
-## Current assignment: client-reliability-5 — active probe investigation
+## Current assignment: client-reliability-5 — prevent orphaned mirror continuation
+
+Investigation at0c1dd7e8 found a narrow defect, independently reproduced by dispatch at47953970 (administrative roster only): after last-owner disposal during active primary media, primary error starts1 fresh mirror HEAD(expected0). /tmp/bitvid-dispatch-5-active-url.mjs mirror-disposed --expect-no-obsolete-head exits1 after cleanup/retry; mirror-shared control exits0/healthy,resources0/slots0. Bounded active retention/success caching itself is intentional and not a defect.
+
+Implement controller-only lifecycle guard before next mirror request: temporary ownership js/ui/urlHealthController.js, focused tests/url-health-lifecycle.test.mjs and your unique integrity/evidence notes. Existing ownership hook is sufficient. Do not change observer/app/shared cache/HEAD-media-HLS-torrent abort,TTLs/limits/mirror order. Ensure cancellation settles with explicit cancelled outcome, no negative cache, no stale UI or newer inflight deletion. Preserve shared/rejoining live owners and ordered mirrors, active healthy cache and normal timeout/retry behavior. No competing writers: storage-cors owns only storage helper; playback-qa product read-only.
+
+Read current rules/test integrity before edits; retain actual observer/controller/cache regression with controlled external IO and mock clock, no sleeps/retries. Test disposed active failure starts0 mirror HEAD; shared/rejoin owner continues; active success cache,timeout/retry and inflight identity preserved. Every new scenario needs reverted failing mutant. Relevant focused tests/lint/build; coordinate full suite/normal queue through dispatch before expensive run (roster full gate currently underway). QA initially owns shared browser: do not launch browser until dispatch allocates it; request availability and use only your own server/port. No blanket prior-suite reruns for administrative edits. Commit item5, merge unstable (never rebase), unchanged gate/durable ancestry before close. CLI/agent/lander launch must unset inherited NODE_TEST_CONTEXT test transport (operational environment correction, no assertion/gate change). Send blocker/product landing/final events with exact checks/counts/gaps. Dispatch owns preview3000 refresh. No subagents/kit/scheduler/external operations. Continue next actions via dispatch routing under existing owner direction.
+
+## Archived investigation: client-reliability-5
 
 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.
 

docs/agents/prompts/storage-cors.md

@@ -1,6 +1,12 @@
 # Area: Storage CORS reliability (storage-cors)
 
-## Assignment: storage-cors-1
+## Assignment: storage-cors-1 — preservation fix routed
+
+Implementation routed after worker and independent dispatch offline reproduction: adding second origin replaces the entire existing rule, existingRulesPreserved0/1. Dispatch command env -u NODE_TEST_CONTEXT node /tmp/bitvid-dispatch-storage-cors-reproduce.mjs exits1 at strict false!==true after all5 characterization controls. No cloud IO.
+
+Now implement only s3-multipart.js plus GetBucketCorsCommand export in s3-client.js and new storage-cors-preservation test/integrity note. Preserve every existing rule and all fields verbatim; add a separate existing-default-shaped rule for uncovered requested origins without broadening arbitrary rules. Idempotence: no PUT when existing equivalent default rule already covers all requested origins; explicitly test equivalent-rule detection and repeated calls. Missing config only on NoSuchCORSConfiguration; other read failures propagate with no PUT. Do not guess wildcard equivalence or merge restrictive/custom rule semantics. Preserve empty-origin no-op. Tests must use actual helper/command export, fake transport only, cover existing rules/wildcards/duplicates/no-config/read-denied/idempotence and bounded provider errors; do not silently replace on read failure. Do not change current default methods/headers/TTL as unrelated policy; if SDK/provider limits make safe preservation impossible, report before broadening. Offline mutants for every new scenario; preserve normal assertions/gates. Relevant focused storage suites/lint/build; request full-suite slot (client ahead), no browser/cloud need. CLI/test/lander launches clear NODE_TEST_CONTEXT. Commit item1, merge unstable, normal queue/durable ancestry before close; no premature qualification of real S3.
+
+Historical investigation context follows; its before-product restriction is superseded by the routed scope above.
 
 Bounded parallel trial: validate todo/TODO_2026-06-16_r2-followups.md CORS replace-not-merge report at current HEAD. Dispatch inspected ensureBucketCors in js/storage/s3-multipart.js: constructs PutBucketCors with requested origins only, no GetBucketCors. This is evidence for investigation, not proof every caller loses policy. Trace actual callers and required existing-origin behavior. Reproduce offline via real helper and fake S3 transport/SDK boundary: an existing origin/rule, adding a second origin, idempotent repeated call, missing config and read-failure cases. No cloud credentials/network/bucket mutation.
 

fleet/LOG.md

@@ -67,3 +67,17 @@
 
 - Owner parallel-trial approval relayed by interpreter and recorded verbatim in PROGRAM. Keep item5 client-reliability; add storage-cors-1 offline existing-origin preservation reproduction and playback-qa-1 independent local fallback qualification. Preflight public open PR count0. Inspection confirms helper constructs requested-origin-only PutBucketCors; QA gap documented in Stage3 and prior item4 report. Neither task assumes a new product defect.
 - Three worker target, disjoint branches/worktrees/files. QA browser first; focused offline work overlaps; full suites/product gates coordinated one at a time. Measure pickup latency, real outputs, gate/browser/tool stalls and durable queue outcomes. No credentialed cloud/live peers/production activity. Launch pending roster landing.
+
+- Trial intervention: original roster47953970 gate rejected13:28:15 at118th file,1047831-byte log with8877 binary0xff markers. Inherited NODE_TEST_CONTEXT=child-v8 emits Node test protocol; spawnSync default capture cap reproduced as ENOBUFS/SIGTERM. Clean diagnostic reached101 file starts with no failure markers then was intentionally stopped(exit143) to avoid overlapping full gates. Resubmitted unchanged roster13:30:35 with NODE_TEST_CONTEXT unset; log now plain text/no binary markers, normal gate unchanged. Original rejection evidence retained in trial notes. MCP deadline/read fallback and worker wake/claim delay also observed; item5 pickup confirmed13:27:49.
+- Item5 independently reproduced disposed active error starting1 obsolete mirror HEAD(expected0); shared-owner control exit0/healthy/resources0. Route same worker to controller-only mirror-continuation guard and focused regression; no active abort or policy changes. Waiting for first roster gate before new worker launch; no launch claimed yet.
+
+- 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.
+
+- Administrative drain completed: item5 routingf3c0ffd3->371e7902(normal gate exit0),storage routing4c7a897c+trial notes2a5ba463->b922c186 docs-only. Dispatch syncedb922c186. Client exclusive full/browser/normal product landing slot granted13:43:51,request13:32:54 (~10m57s resource wait),QA explicitly released browser. Storage next,QA third; normal queue unchanged.
+- Storage ready report9/9 new/original8fail/8mutants,offline lockfile install4s441packages,build pass; lint sandbox git-spawnEPERM requires approved unchanged rerun. QA retained4/4,6 restored failing mutants; same lint environment issue,temporary read-only deps linkage in own worktree. These are worker-derived,not independent reruns. No trial product/regression landing yet; preview preserved.

fleet/RULE-CHANGES.md

@@ -9,6 +9,12 @@ a landing rule changes.
 
 ## 2026-10-20
 
+- storage-cors-1 fix routed after worker+dispatch offline reproduction: preserve existing bucket CORS rules/fields; append default rule only for uncovered origins, idempotent no-PUT for equivalent coverage, only NoSuchCORSConfiguration permits absent config, other read errors no PUT. Own s3-multipart.js/s3-client.js+focused new test/integrity. No real cloud/credential operations or unrelated policy change; full gate slot follows client.
+
+
+- Item5 narrow fix routed after worker+dispatch reproduction: prevent fresh mirror HEAD after disposed last-owner active-media error; controller+focused URL lifecycle tests only. Preserve bounded active/cache/shared/rejoin/timeout semantics, no active abort. Parallel trial CLI/agent/lander launches clear inherited NODE_TEST_CONTEXT transport; exact gate/assertions unchanged. Original roster gate hit binary capture cap, not identified product assertion. No kit patch.
+
+
 - Owner authorizes bounded parallel trial via interpreter: dispatch plus existing client-reliability and two new areas storage-cors/playback-qa. Separate worktrees/disjoint write ownership; no competing app/grid/URL writers. QA initially owns browser; one expensive full gate at a time coordinated through dispatch. Each worker sends read/next-action and timed contention/evidence events. No new external authority or scheduler changes.
 
 

test_logs/TEST_LOG_2026-10-20_13-31-00_dispatch-trial.md

@@ -0,0 +1,11 @@
+# Parallel trial setup and item5 reproduction
+
+- Open PR preflight count0. Roster47953970 normal gate rejected13:28:15 exit1; no product assertion found. Gate log stopped118th file nip17-send-gift-wrap,1047831 bytes,8877 binary markers. Launcher NODE_TEST_CONTEXT=child-v8; host controlled spawnSync output2MiB gives ENOBUFS/SIGTERM/default cap. Original rejection stored here before same-SHA retry overwrites durable result: gate exit1, hashtag-preferences/relay diagnostics tail without failing assertion.
+- Clean-env diagnostic npm test with60s/file bound reached101 files with no failure lines; stopped own process group only,exit143, not a passing full-suite claim. Roster resubmitted with env -u NODE_TEST_CONTEXT; unmodified gate running, plain-text log0 binary markers. No kit/test/gate changes.
+- env -u NODE_TEST_CONTEXT node /tmp/bitvid-dispatch-5-active-url.mjs mirror-disposed --expect-no-obsolete-head: exit1 after cleanup/retry, obsoleteHeads1 expected0; HEAD1->2 after disposed primary error, resources1->0/slots1->0; final settles/null cache; later retry succeeds.
+- Same diagnostic mirror-shared:exit0, live healthy/old checking, shared1 initial HEAD/promise, mirror success/cache/retry reuse, final resources0/slots0. Actual observer/controller/cache; external fetch/media controlled, mock clock. Native decoding/playback/peers/CPU-RSS not qualified.
+
+- Corrected roster gate full normal install+npm-test passed exit0, durable47953970->bbc1be79 at13:37:27; initial attempt13:26:20,rejection13:28:15,clean retry13:30:35 (~6m53s gate). All required test files collected427, no quarantine/expectation changes. Host status confirmed new worktrees/branches/windows249026/249041 after launch.
+- Pickups: client13:27:49(tool deadline delay),storage13:38:24,QA proposal13:39:50/claimed investigation start13:38:36. Item5 focused28/28,6mutants/lint/build are worker-derived evidence; no full/browser yet.
+- QA browser.log reviewed (not independently rerun): Chromium+Firefox each3 local scenarios,decoded VP864x64/currentTime>0 with actual mirror/substituted torrent transport,0external. Browser overlapped admin gate without waiting explicit clearance; self-reported cleanup. No real peers/full-app/native torrent claim.
+- Trial remains in progress; product/test normal landings pending, preview unchanged.

test_logs/TEST_LOG_2026-10-20_13-40-00_dispatch-storage-reproduction.md

@@ -0,0 +1,5 @@
+# Storage CORS independent reproduction
+
+- Code matches rosterbbc1be79; dispatch administrative branch has no storage code delta.
+- env -u NODE_TEST_CONTEXT node /tmp/bitvid-dispatch-storage-cors-reproduce.mjs: exit1 strict existing-origin false!==true after5 characterization controls. Actual helper+SDK wrapper, offline SDK module and transport only. ExistingRulesPreserved0/1; repeated calls2PUTs,missing-config1PUT,read-denied fixture1PUT/read0,empty origins0IO.
+- Scoped preservation semantics routed; no lint/full/build/cloud qualification yet. No live bucket/credentials used.