docs(playback): playback-qa-1 record merged full gate evidence

docs/agents/backlog/playback-qa-1.json

@@ -6,5 +6,5 @@
  "blockedOn": null,
  "addedOn": "2026-10-20",
  "filedAt": "0c1dd7e86be3e28edc96aca47f7753a98990dde0",
- "notes": "Baseline bbc1be79; actual coordinator/strategy/PlaybackService + magnet helpers retained 4/4 focused scenarios; six isolated mutants rejected/restored. Native Chromium154+Firefox146 3 scenarios each: real local mirror + substituted torrent transport decode64x64/time>0; terminal fail settles; zero external requests. No real WebTorrent/full app/Stage3 qualification. Dispatch approved retention13:41:49Z; full+submit slot third after client/storage, explicit grant pending. Browser/server released; early browser overlap scheduling intervention documented in docs/testing/playback-qa-1-evidence.md. Lint11/11 exit0 after approved git-spawnEPERM rerun."
+ "notes": "QA granted14:49:35Z/consumed14:49:46Z after request13:43:52Z (65m43 to grant,11s pickup; storage release→dispatch grant39m57 foreground/wakeup lag). Merged unstable7f99c045→124be143; focused4/4,lint11/11 and full env -u NODE_TEST_CONTEXT UNIT_TEST_TIMEOUT_MS=60000 npm test exit0 all429 unit files. Regression025771a8; six isolated mutants rejected/restored. Browser Chromium+Firefox3 scenarios each passed bounded native VP8 decode; zero external requests, no real WebTorrent/full app/wholeStage3 qualification. Browser scheduling intervention recorded. Preparing unchanged normal queue submission and durable landing verification; no new item."
 }

docs/testing/playback-qa-1-evidence.md

@@ -182,3 +182,18 @@ Merged local unstable into own branch at `acb2fdef3baf74c2526babf79eea8a2451a3aa
 sandbox ORIG_HEAD lock initially read-only, then approved elevated local merge succeeded.
 Post-merge focused check:4/4, exit0; `git diff --check`: exit0. New RULE-CHANGES read.
 Full+submit scheduling explicitly waits behind client then storage per dispatch13:43:52Z.
+
+## Granted merged integration check
+
+Authoritative dispatch mailbox grant header:2026-10-20T14:49:35Z; consumed14:49:46Z.
+Its initial body said14:11; dispatch corrected this explicitly in14:49:55 mail, consumed14:50:25Z.
+Request13:43:52→grant14:49:35=65m43s resource/coordination wait; grant consumption11s.
+Storage release14:09:38→grant14:49:35=39m57s dispatch foreground/wakeup latency, not worker/test time.
+The earlier worker reply interpreted14:11 as intended grant time; this was incorrect. It was a stale body timestamp only, with no14:11 send or delivery delay. Dispatch wake/checkpoint lag39m57s is the valid delay metric; grant consumption was11s.
+
+Merged verified unstable7f99c045 into own branch at `124be14310a314bd4ca99d075a7aacc207c238ac`.
+`env -u NODE_TEST_CONTEXT node tests/fleet-playback-fallback.test.mjs`: exit0,4/4.
+`env -u NODE_TEST_CONTEXT npm run lint`: exit0,11/11 on merged tree (approved outside sandbox for git spawn).
+`git diff --check`: exit0.
+`env -u NODE_TEST_CONTEXT UNIT_TEST_TIMEOUT_MS=60000 npm test`: exit0, all429 unit files passed, including the new regression; completed14:55:44Z. Actual process exit was checked, not a log-reading command. No timeout/failure or assertion changes.
+No browser/build repeat: relevant playback/magnet chain unchanged by predecessor landings.