Tests that need a human to verify, surfaced from each phase's VERIFICATION.md. Pick one, sign in below by editing .planning/uat-state.json (or ask Claude to do it), drop screenshot evidence into .planning/uat-evidence/<test-slug>/, then mark it pass or fail. The publish skill closes the loop into .planning/ on the next run.
From Phase 5 onward we're testing on TestFlight. Builds ship via /testflight; tester comments + screenshots come back automatically via /franks-fed-pull-feedback and land in .planning/inbox/testflight-feedback.md for triage. Read the TestFlight pipeline doc for the full procedure — including the Phase 5 walkthrough next week (VoiceOver, Dynamic Type, Reduce Motion, contrast, 44pt, and the "pretend a pet died" dignity test).
.planning/uat-state.json + 03-VERIFICATION.md + 04-VERIFICATION.md