playtest-report

## Phase 1: Parse Arguments Resolve the review mode (once, store for all gate spawns this run): 1. If `--review [full|lean|solo]` was passed → use that 2. Else read `production/review-mode.txt` → use that value 3. Else → default to `lean` See `docs/framework/director-gates.md` for the full check pattern. Determine the mode: - `new` → generate a blank playtest report template - `analyze [path]` → read raw notes and fill in the template with structured findings --- ## Phase 2A: New Template Mode Generate this template and output it to the user: ```markdown # Playtest Report ## Session Info - **Date**: [Date] - **Build**: [Version/Commit] - **Duration**: [Time played] - **Tester**: [Name/ID] - **Platform**: [PC/Console/Mobile] - **Input Method**: [KB+M / Gamepad / Touch] - **Session Type**: [First time / Returning / Targeted test] ## Test Focus [What specific features or flows were being tested] ## First Impressions (First 5 minutes) - **Understood the goal?** [Yes/No/Partially] - **Understood the controls?** [Yes/No/Partially] - **Emotional response**: [Engaged/Confused/Bored/Frustrated/Excited] - **Notes**: [Observations] ## Gameplay Flow ### What worked well - [Observation 1] ### Pain points - [Issue 1 -- Severity: High/Medium/Low] ### Confusion points - [Where the player was confused and why] ### Moments of delight - [What surprised or pleased the player] ## Bugs Encountered | # | Description | Severity | Reproducible | |---|-------------|----------|---------...