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.
 

fleet/GOAL.md

@@ -22,3 +22,9 @@ Work through the existing TODO backlog, find and fix bugs, and make the client m
 - No deploys, spending, production data, or real-wallet operations; conservative session-manager defaults, not additional owner rulings.
 - First worker approval received 2026-10-19 via Codex desktop chat relay; routine staffing, fixes, tests/builds, and local unstable landings are authorized within this goal. Record relay provenance; no repeated routine approval required.
 - No scheduler or cron activation is implied by fleet startup.
+
+## Continuing owner direction — 2026-10-20
+
+> "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 bounded robustness/usability/backlog work after the three-worker trial. Use fleet/QUALITY.md to track evidence and remaining gates. Passing units alone does not establish project readiness. Keep workers useful where scopes split safely; reduce idle staffing when useful independent work runs out. Stage reproductions/audits before product fixes, preserve normal local unstable landing and restricted-action limits. Amber/cloud/live peers/manual release qualification stays explicitly open until authorized real evidence exists.

fleet/LOG.md

@@ -93,3 +93,8 @@
 - Independently verified storage699d7292->d3f4c215 and closure032f76bc->7f99c045,durable status/log/ancestry0. Worker full428/428,focused13/3files,9new,10restored mutants,lint11/build,normal gate0 are evidence-derived. Dispatch synced and ran CORS regression9/9 natural exit0,build/artifact0,preserved previewHTTP200+index byte-equal dist. No live provider/IAM/serialization/noCAS concurrent writer qualification.
 - Operator14:49:19 found dispatch idle/unread5 and nudged;completed storage release14:09:38 was consumed this foreground checkpoint. Actual QA grant authored14:49:35,read14:49:46(11s),request13:43:52→grant65m43/read65m54;release→grant39m57. Initial grant body incorrectly said14:11;corrected promptly. It was a timestamp error,not a nonexistent earlier send/intended grant;do not classify38m35 as delivery latency.
 - QA now owns full/normal test-landing slot,merged checks/full starting,product read-only/no new browser/build. Two durable product fixes from trial;QA retained regression still pending normal full gate/landing. After integration assess parallel implementation outputs against serialized validations and wake latency;no overall speedup or unattended progress claim. No scheduler/kit change.
+
+## 2026-10-20 — Persistent quality objective and immediate next investigations
+
+- Owner exact direction relayed "ok try to keep them working until the project is in a good place." Recorded GOAL/PROGRAM;QUALITY matrix distinguishes current local proof from Amber/cloud/peer/manual gates across feed/playback/profile/storage/mobile/validation/preview. No readiness claim from unit counts.
+- Existing client worker item6 assigned profile-history actual-removal wiring gap from TODO2;existing storage worker item2 temporarily lent to independent feed/view tombstone gap TODO1. Investigation/evidence only before routing,cheap focused checks while QA full/normal slot active. No extra agents,new product definitions or competing app/Nostr/URL writes.

fleet/QUALITY.md

@@ -0,0 +1,23 @@
+# Quality evidence and next milestones
+
+Updated2026-10-20. Goal: improve robustness/usability against pre-launch TODO and KNOWN_ISSUES. This is a local qualification matrix, not a project-ready/release declaration.
+
+| Area | Current local evidence | Next bounded work | Still unverified / release gate |
+|---|---|---|---|
+| Feed/load/navigation | Existing client tombstone/buffer guards and broad428-file normal gate; current CRUD spec includes delete-modal/cancel coverage | storage-cors-2 temporary read-only feed/view tombstone coverage audit, TODO1 seed→delete→stale refresh scenario | Full app/feed behavior and documented parallel Firefox hydration flakes; live zombie reports |
+| Playback/fallback/magnets | Queued torrent/URL lifecycle fixes7d20a509/89ccb907; mirror guard0bd0b1c3; independent URL18 scenarios. QA actual coordinator/service scratch4 and local Chromium/Firefox3 each, literal hash/webseed checks | playback-qa-1 retained regression full/normal landing currently active | Actual WebTorrent/live peers; full-app fallback; local decoded mirror/substituted torrent does not prove real torrent |
+| Profile/session/history | Profile fixture hang fixedde6918ce;27 focused historical scenarios and current broad suite. History lazy-init test injects fake renderer | client-reliability-6 read-only actual history removal wiring audit, TODO2 regression gap | Amber NIP46 identity/switch/logout across refresh, real signers; KNOWN_ISSUES isolated logout UI failure |
+| Storage/upload safety | CORS productd3f4c215,closure7f99c045; independent9 CORS scenarios,worker focused13/10mutants/full428/lint/build; content-addressed/cleanup safeguards documented | Complete CORS evidence/current integration; follow bounded caller/provider issues only if reproduced | Live bucket/IAM/provider serialization; concurrent read-modify-write has no CAS; no credentials/cloud writes tested |
+| Mobile usability | No fresh local mobile flow/visual qualification from trial | After current investigations, select bounded viewport navigation/modal/card smoke from TODO7; inspect before redesign | Real-device/manual accessibility and UX; visual baselines remain CI-canonical |
+| Trustworthy validation | Unchanged normal gates and restored failing mutants; latest product gate428 files. QA new regression full run in progress | Finish QA gate; retain exact counts, ancestry, fixture boundaries, failed mutants and Known Issues classification | Full broad E2E/release/manual cross-browser checks; never weaken assertions or treat mocked boundaries as live proof |
+| Preview | Preserved localhost3000,storage integrated7f99c045; build/artifact pass,HTTP200/index matches dist | Refresh after each verified product landing; QA is test-only so inspect product delta before rebuilding | Production/live-site state not touched or qualified |
+
+## Milestones
+
+1. Finish prepared trial outputs: two product fixes are durable; retained QA regression still needs full/normal landing. Report actual timings: implementation parallelism exists, but serialized duplicate full gates and39m57 dispatch wake/checkpoint lag prevent an overall speedup claim.
+2. Revalidate high-priority history and feed deletion gaps at current HEAD using real wiring plus controlled IO; route only reproduced defects or valuable mutant-proven regressions. No product changes authorized by investigation assignments.
+3. Establish fresh local core-flow/mobile baseline after those checks; keep live Amber/cloud/peer/manual release gates separate. Continue useful bounded work under existing authority; surface substantive blockers/owner product choices instead of inventing features or keeping agents busy.
+
+## Resource and operating limits
+
+QA currently owns full/normal gate; other investigations may use cheap focused local checks, no expensive full suite/build/browser without dispatch slot. Separate worktrees/branches; no competing product writers or app.js edits. Keep team at dispatch+3 existing workers while useful disjoint tasks exist. Clear inherited NODE_TEST_CONTEXT for CLI launches. Use mailbox/CLI/status recovery, actual send/consume times, no raw pane bodies or unattended-wakeup claim. No push/deploy/spend/real-wallet/production-data/scheduler/credentialed external operations.

fleet/RULE-CHANGES.md

@@ -9,6 +9,9 @@ a landing rule changes.
 
 ## 2026-10-20
 
+- Owner continuation now extends beyond trial until project quality is evidenced,tracked in QUALITY.md with local/live gates distinct. Existing client worker item6 investigates real profile-history removal wiring;storage worker item2 temporarily investigates feed/view tombstone coverage. Both read-only scratch/evidence,no product or committed tests before routing. QA retains expensive full/normal slot. Same3 workers,disjoint scope,no app.js writers/new features/kit/scheduler/external authority.
+
+
 - 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.