Playwright self-improving UI loop + Docker state sharing + credential flow

[KlementMultiverse]

3 Changes

1. Playwright Self-Improving UI Loop

Wire playwright-critic into the flow as a continuous improvement loop:

Phase 3 N4 (code written) → if frontend files changed:
  → spawn playwright-critic
  → MAP: crawl all pages, find all buttons/forms/links
  → TEST: click every button, submit every form, test edge cases
  → SCREENSHOT: capture every page state
  → COMPARE: diff against baseline screenshots (if exist)
  → REPORT: score + create GitHub issues for failures
  → IMPROVE: failures feed into next iteration
  → Save baseline screenshots for next run

Where it runs:

• Phase 3 N4.5 (after code, before review) — per-issue, if frontend changed
• Phase 4 Step 45 (/design-audit) — full crawl, all pages
• Phase 5 (/retro) — visual regression check before merge

2. Docker State Sharing Across Phases

Run docker-state.sh once after S7 scaffold, save to docs/docker-state.json.
All subsequent phases READ that file — never re-create unless changed.

Phase	Current	Proposed
A S7	Creates files, no state	Creates files + captures state
Phase 0	No capture	Reads docs/docker-state.json
Phase 2	No capture	Reads docs/docker-state.json
Phase 3	Captures fresh each time	Reads, only re-captures if changed
Phase 4	Health check only	Reads + validates

3. Credential Discovery Flow

Phase A S2 Q5 already asks about credentials. Enhance:

• Auto-detect existing credentials (~/.aws/credentials, ~/.claude/.env)
• Show user what's available vs what's needed
• Generate .env.example with all required vars
• Never hardcode — always env vars

Acceptance Criteria

• playwright-critic wired into Phase 3 N4.5
• Screenshot baseline saved and compared
• Docker state captured once, shared via docs/docker-state.json
• Phase files read docker state instead of re-capturing
• Q5 credential flow checks existing keys
• Tests for all changes

@coderabbitai plan