land: area/dispatch 402500d3d2 (dispatch)

docs/TODO.md

@@ -2,6 +2,9 @@
 
 ## dispatch
 
+- 2026-10-20 owner continuous-quality direction recorded;fleet/QUALITY.md tracks local vs real release evidence. QA full/normal slot active;client item6 profile-history wiring audit and storage item2 feed/view tombstone audit assigned now,read-only before fix routing. Remaining:actual coverage/reproduction decisions,current QA landing,local mobile/core-flow baselines and unqualified live gates.
+
+
 - 2026-10-20 storage productd3f4c215/closure7f99c045 verified;dispatch CORS9/9/build-artifact/previewHTTP200+dist match. QA exclusive full/normal slot actual grant14:49:35/read14:49:46 after65m54wait;storage-release→grant39m57 wake gap. Remaining:QA durable regression landing,final trial throughput/stall assessment,next bounded routing. Actual cloud/IAM/noCAS concurrent safety/live peers unverified.
 
 

docs/agents/PROGRAM.md

@@ -13,6 +13,13 @@ Work through the existing TODO backlog and fix reproducible bugs that make the c
 
 ## Rulings log (newest first)
 
+### 2026-10-20 — Continuing quality objective, relayed by interpreter
+
+> "ok try to keep them working until the project is in a good place." — owner, relayed by interpreter; not represented as typed in dispatch.
+
+Continue the existing robustness/usability backlog beyond the trial, with bounded evidence-first tasks and adaptive staffing. Local proof and real Amber/cloud/live-peer/manual release gates stay distinct. This does not add push/deploy/spend/real-wallet/production-data/scheduler authority or authorize new product definitions. Track current quality and next work in fleet/QUALITY.md.
+
+
 ### 2026-10-20 — Bounded parallel trial, owner words relayed by interpreter
 
 > "id really like to stress test the multi agent process so if it needs more agents to get more done faster. do it" — owner, relayed by interpreter; not represented as typed by owner in dispatch.

docs/agents/backlog/client-reliability-6.json

@@ -0,0 +1,9 @@
+{
+  "id": "client-reliability-6",
+  "area": "client-reliability",
+  "status": "open",
+  "title": "Audit real profile history removal wiring and historical no-op regression coverage",
+  "blockedOn": null,
+  "addedOn": "2026-10-20",
+  "filedAt": "7f99c0456931c917082d6a6680c79655221dcc82"
+}

docs/agents/backlog/storage-cors-2.json

@@ -0,0 +1,9 @@
+{
+  "id": "storage-cors-2",
+  "area": "storage-cors",
+  "status": "open",
+  "title": "Audit feed/view tombstone stale-refresh regression gap with offline integration",
+  "blockedOn": null,
+  "addedOn": "2026-10-20",
+  "filedAt": "7f99c0456931c917082d6a6680c79655221dcc82"
+}

docs/agents/prompts/client-reliability.md

@@ -1,6 +1,12 @@
 # Area: Client reliability (client-reliability)
 
-## Current assignment: client-reliability-5 — prevent orphaned mirror continuation
+## Current assignment: client-reliability-6 — profile history wiring audit
+
+Owner continuing quality objective is in GOAL/PROGRAM; use fleet/QUALITY.md. Item5 done0bd0b1c3/closuredc852597. Claim item6,merge verified unstable non-destructively,read current rules/KNOWN_ISSUES/test integrity. High-priority TODO2 explicitly asks profile-pane remove wiring regression. Current controller comment says no-op onHistoryReady override was removed; current history-pane test injects fake renderer and validates lazy init,not real remove. Revalidate whole test corpus before assuming a gap.
+
+Investigation/scratch/evidence only now: trace actual ProfileModalController→createWatchHistoryRenderer→default removal→history controller/service with controlled local state/IO; verify local-only delete/clear and synced callback options only through fake publish boundary,no signer/relay/private data. Prove what current assertions cover and whether historical no-op override would escape them. Prefer actual wiring invocation over source-string assertions. Classify a remaining product failure separately from missing regression; send exact HEAD/commands/counts/reproduction or mutant result,proposed smallest retained test/fix scope. If already covered,close audit with evidence and next priority. No product or committed test changes until dispatch routes scope; no app/history service/cache ownership expansion. Your existing profile modal modules/tests read-only for investigation;unique notes/backlog allowed. QA owns full/normal gate;cheap focused checks only,no browser/build/full gate. No subagents/kit/scheduler/cloud/real signer/wallet/production activity. Send immediate read+next-action,then blocker/completion;keep .task current.
+
+## Archived completed 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.
 

docs/agents/prompts/storage-cors.md

@@ -1,6 +1,14 @@
 # Area: Storage CORS reliability (storage-cors)
 
-## Assignment: storage-cors-1 — preservation fix routed
+## Current assignment: storage-cors-2 — temporary feed/view deletion audit
+
+Storage item1 doneproductd3f4c215/closure7f99c045. Owner continuing direction calls for useful disjoint work now; this worker is temporarily lent to an independent read-only feed/view reliability slice. No other agent owns this slice. Claim storage-cors-2,merge verified unstable,read GOAL/PROGRAM/QUALITY/RULE-CHANGES/KNOWN_ISSUES plus NIP09/addressable deletion docs and centralized schema before Nostr-related investigation.
+
+High-priority pre-launch TODO1 asks seed→delete→assert-not-rendered feed/view regression; underlying tombstone guard and buffer tests exist. Dispatch inspected CRUD flow spec: settings/delete modal/cancel coverage is not proof of full stale-relay/reload suppression. Inspect all existing scenarios first;do not duplicate or misclassify known Firefox fixture flake as product bug. Trace actual client/buffer→feed/view boundary read-only. Build deterministic offline scratch at actual integration seam:seed visible owned synthetic video,apply local tombstone/delete event,deliver stale older version and refresh/cache hydration;assert card remains absent; include unaffected/live-video control. No public relay/signer/session actor publishing,real deletion/private data or app.js edits.
+
+Investigation/evidence only,no product/committed regression edits until dispatch scopes a demonstrated defect or mutant-proven coverage gap. Report exact HEAD/commands/counts,which actual renderer/cache/client boundaries are exercised,smallest proposed test/fix files and fixture limits. Do not call a mocked-only callback a full feed proof. Existing js/app.js,js/app/**,Nostr core,VideoListView,existing CRUD specs all read-only. Unique docs/testing/storage-cors-feed-* and own evidence/backlog allowed. QA owns current expensive gate:cheap focused offline checks only,no browser/build/full run. No subagents/kit/scheduler/cloud/real signer/wallet/production actions. Send immediate read+next-action and eventual evidence/blocker;keep .task current.
+
+## Archived completed 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.