review-checklistlisted

# Delivery Review ## Goal Decide whether the PRD and UI delivery is ready for stakeholder review, engineering handoff, or launch. ## Workflow 1. Check `prd.md`, UI deliverable references, portable HTML when present, and optional exports against their contracts. 2. Identify gaps by severity: Critical, High, Medium, Low. 3. Record artifact, evidence, owner, required-before phase, and status for each finding. 4. Verify source IDs, requirement links, acceptance links, tracking links, UI delivery references, and local file references resolve. 5. Verify validation evidence is concrete and not a stale placeholder. 6. Audit every requirement for visual evidence, visible-copy, and measurement coverage. A missing `多语言需求` or `埋点需求` section is acceptable only when the requirement coverage review explicitly records `not_needed` with source-backed rationale; do not approve a PRD whose coverage is absent. 7. For implemented-feature PRDs, verify that generated outputs were not used as current product facts, that a rewrite uses a new run folder, and that every placeholder follows a recorded capability chain rather than an untried fallback: existing-preview discovery, project-runtime reuse or activation through the actual project configuration, target test-state recovery, then Playwright, Chrome DevTools, and Computer Use attempts. A fixed port is never the contract; `skipped` is invalid for a required placeholder, and each attempt needs a durable local result reference. 8. Route each find