What problem does it solve? Automated tests often assert what the code does today rather than what a real user would experience, so defects like search that only reads the first page of results survive every test. This Skill drives real user journeys through the live UI as named personas and ends each journey in a claim that can be false, producing actionable failures instead of vague impressions. ## Core Features & Use Cases - Persona-based journeys: Two enforced personas — a newcomer on a fresh empty account and a frequent user seeded to at least 25 books — catch empty-state problems and scale-related defects like pagination and truncation bugs. - Evidence tooling: Per-step x-trace-id labels, a log collector (collect_run_evidence.py) that exits non-zero when a correlated query matches nothing, and a humanRun.ts helper that captures a full-page snapshot per step, pass or fail. - Calibration discipline: Every journey must be validated by deliberately breaking the behavior it protects and watching the test go red, ensuring checks can actually fail. - Use Case: A user with 83 books searches their library by exact title and gets nothing because the frontend filters only the first 20 loaded rows; the frequent persona journey catches this, while a fresh-account suite would report success forever. ## Quick Start Run the persona journey Playwright spec against the local lw-iso frontend on port 25174 and review the per-step snapshots and collected logs for any failing claim.