eng-quality-handoff

# Collaborative Quality Handoff ## Intent - Make it effortless for reviewers, QA, and partners to understand, validate, and extend your work. - Ensure ownership persists after merge via clear action items and shared context. ## Workflow 1. **Narrate the change** - Summarize problem, approach, and tradeoffs in the PR/issue using concise bullets. - Link related tickets, specs, dashboards, or smart-contract addresses. 2. **Surface review focus** - Call out risky areas, migrations, or TODOs explicitly; request specific expertise if needed. 3. **Attach evidence** - Provide test results, captures, or transaction hashes inline so reviewers don’t need to rerun everything. 4. **Plan follow-ups** - Create tasks for deferred work, debt, or experiment cleanups with owners and timelines. 5. **Stay available** - Monitor review threads, CI pipelines, and post-merge telemetry; respond quickly and document resolutions. ## Verification - Review checklist complete (tests attached, docs/flags updated, reviewers assigned). - Outstanding issues tracked with owners; no “known issue” left implicit. - After merge, confirm deployment/monitoring links are shared with relevant teams.