artifact-packaginglisted

# Delivery Check ## Goal Make the final PM delivery easy to review, share, and continue without creating extra default Markdown packages. ## Workflow 1. Verify `prd.md` exists and follows the PRD contract when PRD is in scope. If the user explicitly requested no PRD, verify the structured reference or document prototype is the primary delivery instead. 2. Verify a UI deliverable exists or is recorded when UI is in scope: an evidence-based prototype, existing UI extract, specification, or `prototype-<platform>.html`, each with fidelity and implementation-owner notes. 3. For implemented-feature PRD delivery, verify branch evidence was inspected and every visible feature behavior is represented in `prd.md` or recorded as an internal evidence gap. Reviewers should not need to manually inspect the branch to find missing requirement content. 4. Verify PRD and UI deliverable agree on scope, screens, states, logic, interactions, and tracking; keep blockers in internal evidence or an explicitly requested handoff. 5. Verify the PRD contains only its canonical product sections: version history, background, relevant research, requirement list, requirement details, applicable new copy, and concise tracking. Verify implementation evidence, risks/open confirmations, acceptance criteria, and validation results remain in the run trace or an explicitly requested handoff. 6. When `prd.html` exists, verify it is a readable document rendering of `prd.md`, not a UI prototype: normal document c