Merge branch 'unstable' into area/storage-cors

This commit is contained in:
thePR0M3TH3AN committed 2026-10-22 10:22:14 -04:00
commit 89f8923c6e
5 files changed
+18

No files matched your search

+2
View File
@@ -2,6 +2,8 @@
## dispatch
- 2026-10-22 client9 HEAD independently11modes(3fail/8controls pass),finalowner fetch/timer retained(no media slot leak);controller HEAD-only fix+strict contract/identity/ignoringabort regressions routed. HLS/torrent/RangeGET remain open;QA offline genuineBuffer rebuild prep, mobile/Amber staged.
- 2026-10-22 storage3 independent7/3pass/4fail: buffer newer-version loss and service deleted snapshot/cache leakage routed separate small commits; coordinator stale render still open/read-only pending registered lifecycle evidence. QA3 app-less3pass not CI proof; genuine cached Buffer followup granted exclusive narrow browser.
- 2026-10-22 resumed six-priority campaign: Firefox QA3, active cancellation client9, tombstones storage3 now; playback dispatch4, Amber dispatch5, mobile dispatch6 staged with acceptance criteria. See docs/agents/CAMPAIGN-2026-10-22.md. All six remain unfinished; old idle/quiet-hours hold superseded for this foreground scope. Final integrated checks/build/preview and live/manual disclosure outstanding.
@@ -1,3 +1,11 @@
## Implementation routing 2026-10-22 — client-reliability-9 HEAD only
Dispatch independently ran11 scratch modes via dispatch imports at169d894f (runtime identicalc5b678f7):3 fail naturally(disposed/same-turn/later),8 pass(shared/cross/legacy/live-success/error/timeout/late-success/error),cancelled0. Final owner retains1HEAD/0abort/1timer5000ms/unsettled/original inflight; media slots0/queue0. Minimal implementation authorized ONLY js/ui/urlHealthController.js HEAD probe lifecycle cancellation hook/cleanup plus tests/url-health-lifecycle.test.mjs or unique HEAD lifecycle tests and strict integrity/spec/evidence notes. Existing observer/cache/app/HLS/torrent modules remain read-only.
Explicit spec correction permitted: prior queued/media-only completion does not fulfil source-backed Stage3 active HEAD last-owner cleanup. Preserve failed baseline and existing live/shared/legacy controls; equally strict or stricter changed expectations with Test Integrity Note. Release final-owner HEAD by marking cancelled synchronously, abort transport, settle null promptly without waiting for ignored abort/timeout, remove timer/hook exactly once; no cache, stale badge, fallback media/mirror start or replacement deletion. Fresh same-turn and later owner must start fresh request, old success/error/timer/finalizer cannot affect it. Preserve live HEAD success/error/timeout fallback, shared/cross/ownerless legacy ownership, media-hook handoff and FIFO/queue bounds. Add transport ignoring abort, missing AbortController, cancellation-before-start/at-handoff, late callbacks and replacement controls where applicable. HEAD only, do not conflate Range GET task or HLS/torrent completion; measure those later separately.
Focused regression + restored failing mutants + lint now, request serialized full/browser slot when ready, no expensive job or normal product submission without grant. QA has conditional next narrow Firefox slot. Normal local queue/gates/durable ancestry required. No retries/sleeps/force exits/relaxed expectations, external/signer/cloud/credential authority unchanged.
## Current assignment 2026-10-22: client-reliability-9 — remaining active cancellation
This supersedes the old item8/idle scope below. Read current dispatch campaign brief, PROGRAM/RULE-CHANGES/KNOWN_ISSUES and test integrity. All worktrees were clean at dispatch inspection; inspect your own status then fast-forward own branch to unstable if safe (never discard work); report exact SHA and ack next action. Claim item9. Start actual observer/controller active HEAD-request last-owner/shared/same-turn+later rejoin offline measurements. Use controlled fetch/abort, count settlement/slot/cache/mirrors/stale callbacks; retain live success/error/timeout/FIFO and replacement identity controls. HEAD first, HLS/torrent separately tracked, no wider completion claim. Source/scratch/unique evidence only; NO product or committed test changes until demonstrated defect and dispatch routing/spec note. Do not inherit previous item8 implementation permission for HEAD. Own future health files as roster, app/services/cache read-only. No full suite/build/browser/normal product submission yet; QA has initial expensive/browser slot. env -u NODE_TEST_CONTEXT for commands, no force exit/retries/sleeps. Send read/next action, reproduced result/blocker and READY for checks. After this slice, playback and Amber remain staged in campaign; await bounded routing, not optional self-selection.