docs(qa): continue across auto-compaction without the user (file-state is authoritative)

Don't hand back when context fills: harness auto-summarizes + you continue from the committed
run-state + coverage. Can't self-invoke /compact and don't need to. Commit before interruptible
work; session-start ritual recovers stuck sessions. Only true blockers (denied gated action /
macOS) stop the run.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

ClaudeQAPlan.md

@@ -36,9 +36,15 @@ confirms + enumerates this; the fix phase applies couple-shared everywhere.
   findings are still logged and fixed in the fix phase.
 - **"Once executed, complete it":** never declare done before the Definition of Done is met — keep cycling fix → re-QA
   until flawless, then stop.
-- **Context limits ≠ stopping.** If a context window fills, that's a checkpoint, not a stop: make sure the run-state
+- **Context limits ≠ stopping — do NOT hand back to the user when context fills.** The harness auto-summarizes a long
-  header + MD files are current and committed; the resume command continues automatically. Keep the loop alive across
+  conversation and continues in the next window; you continue **without the user**. (You cannot self-invoke `/compact`
-  sessions until flawless.
+  — and you don't need to; auto-compaction handles it.) The **committed `ClaudeReport.md` run-state + `ClaudeQACoverage.md`
+  are the authoritative state** and survive any compaction — after a summary, **re-read them and continue at the next
+  chunk**. Never pause a run merely because context is getting long; only stop for a true blocker (a denied gated action
+  even with standing auth, or the macOS requirement for iOS).
+- **Commit before anything interruptible** so a mid-chunk compaction never loses progress. Keep chunks atomic; if a
+  chunk is cut off mid-way (e.g., a game session left active), the **session-start ritual recovers it** (clear the stuck
+  session via in-app "End their game", then redo that chunk). Right-sized chunks (see Batch sizing) make this rare.
 - **Don't pause for "by-design vs bug":** log the ambiguous finding and keep going (don't unilaterally rewrite
   deliberate design — the log captures it). Never halt the run to ask.
 - **Only true stop = a gated action you cannot perform.** Production deploys, admin Firestore writes/seeds, and

ClaudeReport.md

@@ -3,7 +3,7 @@
 > **RUN-STATE: Round 2 | Pass B in progress (1 game/chunk) | This or That ✅ full playthrough. NEXT ACTION: play How Well → Desire Sync → Connection Challenges → Memory Lane → Spin the Wheel → Date Match (premium ones need a Sam-premium toggle). Then Pass C deep/stateful screens + nav/back; live notification matrix; D3 non-member test; Pass F (incl. F-OBS load-failure handling).**
 > R2-1 DONE: A-001 couple-shared re-verified live (Desire Sync/Memory Lane/Wheel enter when partner premium; free→paywall). **D-001 (P1) FIXED+DEPLOYED** (capsules/challenges rules; Memory Lane + Connection Challenges now load). Sam reverted to free (baseline).
 > Round 1 complete (all 5 passes run report-only; P0–P2 found were fixed in-line). Fixes: A-001 (e8892a9), E-001 (ce12abb). Open P3: A-003, B-001, E-002.
-> **EXECUTION MODE: autonomous run-to-completion — do NOT stop; fix anything that blocks progress and continue; keep cycling fix→re-QA until a flawless round.**
+> **EXECUTION MODE: autonomous run-to-completion — do NOT stop; fix blockers inline; keep cycling fix→re-QA until flawless. Do NOT hand back when context fills — the harness auto-compacts and you continue from THIS run-state (re-read it + coverage after any summary). Commit before interruptible work; recover stuck sessions via the session-start ritual.**
 > **STANDING AUTHORIZATION (user, 2026-06-24): may `firebase deploy --only firestore:rules` + has admin access (Firestore reads/writes/seeds + entitlement toggles) — run these without pausing. Only the macOS requirement for iOS (Parts 2/3) remains a hard stop.**
 > Playbook: `ClaudeQAPlan.md`. Coverage matrix: `ClaudeQACoverage.md`. Report-only during passes (no fixes until the fix phase).
 > Devices: emulator-5554 (QA=`Y05AKO`) + emulator-5556 (Sam=`imDjjO`), paired (coupleId `Xal3Kw3gjSdn0niERYKJ`). Build == HEAD `64f0a7e`.