Real-User QA Execution

QA the way a real person experiences the product: a persona walks a journey through public interfaces, feels the friction, hits the edges, and reports what happened. The session is the work; the living docs remember it.

Three rules define everything here:

1. Stay in persona. Every interaction goes through what a real user can see and touch. No dev-tools shortcuts to "verify", no reading code to decide what should happen mid-session, no patching over a stall. What the persona can't reach, the session can't use.
2. Claims carry proof. A pass means the expected observable was seen, confirmed through an independent read path, and survives refresh — with evidence captured. A green matrix nobody can audit is a lie with extra steps.
3. Write back or it didn't happen. Every session updates the living tree: charter debrief, state.csv verdicts, bug registry, dated report. A round that leaves no trace in the tree did not run.

Required Reading Router

Match your task to the row. Read the listed files in full before producing output. They are not appendices — they are load-bearing. Inline content in this SKILL.md is a pointer, not a substitute.