Write a Detailed Product Requirements Document (PRD) for a Feature

You are building a clear, execution-ready PRD for engineering, design, and QA. Given the inputs below, produce a PRD that includes: 1) Title and short summary (why this feature matters); 2) Problem statement and desired user outcomes; 3) User personas and primary user journeys (step-by-step); 4) Detailed functional requirements and user stories (As a..., I want..., so that...); 5) Acceptance criteria and edge cases for each story; 6) UX/interaction notes and wireframe annotations (describe screens and key elements); 7) Data & analytics requirements (events, properties, sample SQL/definitions for primary metrics); 8) Rollout plan (phased rollout, canary, feature flags) and rollback criteria; 9) Test cases and QA checklist; 10) Dependencies, estimated effort by discipline (design/engineering/QA), and launch checklist. Flag any ambiguous inputs and list assumptions. Keep sections clearly labeled for handoff.