Merge branch 'unstable' into area/storage-cors

docs/agents/CAMPAIGN-2026-10-22.md

@@ -1,6 +1,6 @@
 # Six-priority campaign — 2026-10-22
 
-Owner: "yeah lets get the fleet spun up and address all of these", relayed by interpreter at14:02:34Z. Routine YES14:03:29Z. Prior holds superseded only within this foreground scope. Baseline unstable fb54cea3. Team is dispatch plus three existing workers; windows alive, assignments sent after durable coordination landing. A sent assignment is not an acknowledgement.
+Owner: "yeah lets get the fleet spun up and address all of these", relayed by interpreter at14:02:34Z. Routine YES14:03:29Z. Prior holds superseded only within this foreground scope. Baseline unstable fb54cea3. Team is dispatch plus three existing workers; windows alive. Coordination c6022f21 landed c5b678f7 (durable status/log/ancestry checked). All three assignments acknowledged at c5b678f7: storage14:08:34Z, QA14:08:41Z, client14:08:44Z; each reports safe fast-forward and claim. No browser/expensive process started at acknowledgement; QA retains initial narrow slot. No current tool blocker reported.
 
 | Priority | Accountable owner / item | Immediate action | Acceptance / boundary |
 |---|---|---|---|
@@ -21,3 +21,9 @@ Owner: "yeah lets get the fleet spun up and address all of these", relayed by in
 6. Verify required focused/lint/mutants and unchanged normal gates; land via queue, verify durable status + unstable ancestry before closing. Integrated build/artifact/local preview and final six-row status, honest live/manual blockers.
 
 No deploy/push/spend/production data/real-wallet/credential/live signer/cron authority. No retries, sleeps, force exits, weaker assertions or speculative fixes. No background monitoring claim. Read KNOWN_ISSUES before debugging; existing Firefox flakes and logout failure are baselines, not presumed causes of this CI failure.
+
+## 14:12UTC evidence/routing checkpoint
+
+QA released first browser14:11:17Z: original3 scenarios pass but app bootstrap failed because Buffer CDN was denied, so not CI reproduction. Next exclusive narrow Firefox diagnostic authorized only with pinned genuine cached Buffer and actual readiness, preserving assertions and isolated control; no broad/full/build.
+
+Storage3 dispatch-independent scratch on7369f1fe/runtime-equivalentc5b678f7:7scenarios/3pass/4fail/network0, naturalexit1/29.89ms. Service snapshot/persistent cache leaks original deleted version; old tombstone unconditionally removes newer live active version in buffer; overlapped coordinator older result renders deleted reference at renderVideoList boundary. Two smallest service/buffer fixes routed in separate commits with mutants/controls; coordinator remains open/read-only pending faithful registered lifecycle evidence. No DOM/production proof.

docs/agents/prompts/storage-cors.md

@@ -1,3 +1,11 @@
+## Implementation routing 2026-10-22 — storage-cors-3
+
+Dispatch independently reproduced all7 scratch scenarios using dispatch imports at7369f1fe (runtime diff0 vsc5b678f7):3pass/4fail, naturalexit1/29.89ms/network0. Temporary ownership ONLY js/nostr/videoEventBuffer.js and js/services/nostrService.js plus new uniquely named focused regression/integrity/evidence files. This supersedes investigation-only restriction for these two boundaries; existing client.js and app/feedCoordinator.js remain read-only.
+
+Separate commits: first buffer timestamp-safe deletion (recordTombstone already protects strictly newer active content; remove no valid newer version), then service snapshot/persistent eligibility + obsolete affected-record cleanup. Retain failed baseline and independently failing mutants for every new scenario. Do not invent root/address/author rules or broaden deletion across authors; use existing authoritative tombstone semantics and verified conversion path. Cover deletion-marker ID differing from original; late older tombstone against newer live; late older content; multiple versions/unrelated roots/authors; deleted/invalid persistent entries; empty-result persistence so deleted-only caches do not resurrect; warm/second-load/latest-consumer and stale-subscription controls. Preserve live cache/moderation/access/ordering and publication semantics. Report any preexisting identity weakness separately rather than opportunistic rewrite.
+
+Coordinator stale-refresh result remains OPEN: current scratch pauses actual feed engine decorator and calls actual coordinator, but is not full registered UI lifecycle proof. Gather faithful registered-feed/view/disposal overlap evidence only after first fixes; no coordinator/app edits yet. No tests/runner/helpers changes to bypass contract. If new test needs explicit registration, ask dispatch for narrow ownership. Run focused suites, failing restored mutants and lint; request serialized full gate before product submit; QA holds narrow Firefox browser slot. Normal gates/durable ancestry mandatory. No real signer/cloud/relay/deletion/credential operations.
+
 ## Current assignment 2026-10-22: storage-cors-3 — feed/view tombstone stale-refresh
 
 Supersedes old idle/storage2 and deferred3 scope below. Read dispatch campaign brief, PROGRAM/RULE-CHANGES/KNOWN_ISSUES and docs/nips before Nostr investigation. Inspect own worktree and safely fast-forward clean branch to unstable; preserve any unexpected work; report SHA, claim item3, send read/next-action. Read actual tombstone/deletion/cache/view lifecycle; reproduce delete ingest followed by stale refresh/late older event/view switch with synthetic offline events/controlled IO. Check unrelated live/newer valid content and existing deletion semantics; do not invent new policy. Source read/scratch/unique evidence/backlog only; NO product/committed test edits until demonstrated defect and precise ownership routing. App/feed/services/Nostr shared modules remain read-only for now. No real signer/relay/cloud/credentials/delete; no browser/build/full suite/normal product submission yet, QA owns initial expensive/browser slot. Focused offline checks permitted, env -u NODE_TEST_CONTEXT. Report path and strict failed/control counts or already-fixed evidence, proposed smallest files/retained regression and remaining limits. No optional new storage work after this slice without campaign routing.