CATEGORY|OBSERVATION|HANDLING
PAIR|Second browser reused a one-time pairing URL and received Invalid pairing token|Rejected setup; copied only fresh isolated browser session privately
STARTUP|Vite module startup and concurrent work delayed mount; initial screenshot was splash|Rejected splash and screenshot timeouts; mounted fixture required for credit
CPU|App reported fs-02 froze22s, CPU load29 on4cores; concurrent independent auditor/native work untouched|Stopped own unlimited recorders; one-thread5fps recorders; do not mask overload toast
IPC|Initial send.py45s timeout could expire while overloaded screenshot was pending|Rejected incomplete chapters; captured PIDs paused/killed; clean command/result files before retry
FIXTURE|Prior desktop sidebar drift came from incremental shell seeding|Round3 uses read-only SQLite backup of fully seeded stopped round2 fixture for both browsers
SCOPE|Strict20minute capture/upload budget|No native work, source edits, commits, PR edits/comments/push/watch; partial coverage explicit
AUTH|Head returned to pair screen/n=0 during dark recovered500ms repeat|Rejected unstable gate and subsequent head chapters; shared refresh-session invalidation is inferred, not proved; minted independent private credential for bounded finalR3 attempt
SIDEBAR|Same shell text still drifted because real sidebar scroll offsets differed|Rejected initial comparisons; equal scrollTop0 before full-surface screenshots eliminated sidebar delta, no masking
FINALATTEMPT|Independent head retry could not proceed: Target page, context or browser has been closed|No extra credit; capture stopped and partial delivery published
PROVENANCE|Later pair-page navigation overwrote head manifest with2responses|All10retained actual loaded source responses independently rehashed against exact commits; no invented missing response, retained-source-verification.json records this limitation
