Merge branch 'unstable' into area/storage-cors

This commit is contained in:
thePR0M3TH3AN committed 2026-10-22 10:31:14 -04:00
commit 984c219cd2
19 files changed
+1884 -11

No files matched your search

+6
View File
@@ -27,3 +27,9 @@ No deploy/push/spend/production data/real-wallet/credential/live signer/cron aut
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.
## 14:23UTC QA checkpoint / mobile routing
QA3 native Playwright runner + original instrumentedTest/global setup/3callbacks/assertions PASS3/0fail/0flaky/0skip/retries0, workers1/private genuine Buffer/public-deny/scratch static server. Worker naturalexit0,9955ms,release around14:22:11UTC. Original CI184pass/2fail/3flaky remains OPEN/unreproduced; no speculative fix. App-ready3 and isolated3 and original-timing3 are distinct prior controls, not repeated CI proof. Access to failed CI logs403/no E2E artifact limits diagnosis; offline mirror/serial/serviceWorker setting/server differ. Retain QA3 evidence and stage further reproduction only on new evidence.
Priority6 now ACTIVE via QA4: actual-app Chromium360/390/1280 Upload width+culprit/focus/touch measurement, strict overflow baseline preserved, no CSS/product edits before independent evidence+routing. QA exclusive bounded browser, no full/build. Priority1 remains open; priorities2/4 fixes ongoing,3/5 staged.
+4 -3
View File
@@ -1,10 +1,11 @@
{
"id": "dispatch-6",
"area": "dispatch",
"status": "open",
"status": "in-progress",
"title": "Reproduce and resolve mobile overflow touch focus accessibility",
"blockedOn": "Staged QA followup after Firefox; CSS owner assigned only after culprit evidence",
"blockedOn": null,
"addedOn": "2026-10-22",
"filedAt": "fb54cea3a2ba99b4860421724a5050af6b97c293",
"brief": "docs/agents/CAMPAIGN-2026-10-22.md"
"brief": "docs/agents/CAMPAIGN-2026-10-22.md",
"workerItem": "playback-qa-4"
}
+10 -8
View File
@@ -1,10 +1,12 @@
{
"id": "playback-qa-3",
"area": "playback-qa",
"status": "open",
"title": "Diagnose Firefox deterministic CI failure at fb54cea3",
"blockedOn": null,
"addedOn": "2026-10-22",
"filedAt": "fb54cea3a2ba99b4860421724a5050af6b97c293",
"brief": "docs/agents/CAMPAIGN-2026-10-22.md"
"id": "playback-qa-3",
"area": "playback-qa",
"status": "blocked",
"title": "Diagnose Firefox deterministic CI failure at fb54cea3",
"blockedOn": "CI-equivalent failing execution evidence unavailable: public logs403, no Playwright artifact; exact terminal assertions identified but controlled local Firefox runs pass. Await new actionable CI evidence; no further reruns routed.",
"addedOn": "2026-10-22",
"filedAt": "fb54cea3a2ba99b4860421724a5050af6b97c293",
"brief": "docs/agents/CAMPAIGN-2026-10-22.md",
"evidence": "docs/testing/playback-qa-3-investigation.md",
"checkpoint": "Public CI184passed/2failed/3flaky preserved; local exact Playwright3passed/0failed/0flaky/0skipped,workers1,retries0,naturalexit0; not fixed or done."
}
+10
View File
@@ -0,0 +1,10 @@
{
"id": "playback-qa-4",
"area": "playback-qa",
"status": "open",
"title": "Reproduce actual-app mobile Upload overflow and focus touch behavior",
"blockedOn": null,
"addedOn": "2026-10-22",
"filedAt": "e04549f816f6ec61f305e20df0ce2b59797c4651",
"brief": "docs/agents/prompts/playback-qa.md"
}
+10
View File
@@ -1,3 +1,13 @@
## Current assignment 2026-10-22 — playback-qa-4 mobile
QA3 narrow native runner passes3/0fail/0flaky/0skip, not CI qualification. Keep QA3 OPEN or blocked/deferred with exact unavailable failure-evidence reason; retain docs-only evidence+normal queue/durable status. No more speculative Firefox reruns/concurrency ramp.
Claim QA4 after rereading newest RULE-CHANGES. Preserve own dirty/unlanded evidence before merge unstable. Actual-app bounded Chromium at360x800/390x844/1280x720: verify genuine dependency mirror/hash and actual app readiness, then open Upload through actual UI; measure document/client/scroll widths, component bounding rectangles and exact overflow source. Preserve strict width<=viewport as originally failing; no separate relaxed pass replacing it. Capture actual critical touch-target sizes/reachability, focus-visible/Tab containment+close-focus restore, horizontal scroll/zoom behavior as feasible; distinguish measured local/browser checks from real device/AA audit. Use source trace/computed style to identify culprit, tokens/classes/rules, before suggesting minimal CSS file scope. No speculative redesign or token/color changes.
Investigation/source/scratch/unique evidence ONLY, no product/CSS/retained tests/helpers/config edits. Do not publish/seed real events or use real accounts/relays/signers/cloud/media. Use existing actual-app fixtures and verified genuine offline dependency mirror; no fake app substitute. Local mock relay/synthetic data only if needed; block other public HTTP/WS. If prep prevents actual boot, stop and report exact blocker before substituting.
Exclusive bounded Chromium browser slot GRANTED for this baseline, announce START/.task and RELEASE with UTC/exact SHA/commands/check counts/resource cleanup. Preserve preview3000/peer resources, use own private server. No broad/full/build or product submit before dispatch resource grant. After first demonstrated culprit or hard blocker report to dispatch for independent reproduction and precise CSS ownership. All6 campaign priorities remain tracked; no product fix to Firefox inferred from local pass.
## Current assignment 2026-10-22: playback-qa-3 — Firefox deterministic CI failure
Supersedes prior idle/QA2 scope below. Read current dispatch campaign brief, PROGRAM/RULE-CHANGES/KNOWN_ISSUES, harness and test integrity. Inspect own clean/unlanded state; fast-forward own branch safely to unstable, report SHA, claim QA3, send read/next-action. Interpreter reports run39536282396/job119013565277 failed Firefox at fb54cea3 while build/units/Chromium/visual passed; remote logs previously empty. This is reported evidence, not a diagnosed product failure. Inspect workflow/artifacts/read-only CI metadata if accessible; no credential disclosure/access, remote writes or workflow rerun. Identify failing step/assertion before smallest local deterministic reproduction, preserving first failure and natural exit. Do not assume known hydration flake is cause. Existing tests/helpers/config/product read-only until precise defect and dispatch ownership routing; scratch/new QA evidence only. Browser/expensive slot initially GRANTED for one narrow Firefox reproduction at a time, announce start in .task/mailbox and release promptly; no broad E2E/full npm test/build/normal product queue until separate slot. Other workers focused offline only. No retries/sleeps/weaker assertions/force exits/public fixture traffic; preserve preview3000 and peer servers. Report exact failure, command/counts/environment and unverified CI boundary. Mobile overflow/touch/focus is staged next after Firefox checkpoint; no CSS edits yet.