Update to Web App QA & Release Copilot

{
  "description": "Verify release pipeline, migrations, feature flags, rollback and deployment sequencing.",
  "included_files": [],
  "name": "review-deployment-rollout",
  "skill_md_contents": "---\nname: review-deployment-rollout\ndescription: Verify release pipeline, migrations, feature flags, rollback and deployment sequencing.\n---\n\n# Review Deployment Rollout\n\n**Use when:** The request concerns shipping, promoting staging to prod, canary releases, database migrations or rollback plans.\n\n## Workflow\n1. Confirm artifact identity, environment, deployment trigger, approvals and required smoke suite.\n2. Map changes and dependencies that cannot simply roll back (database schema, externally emitted events, cached objects).\n3. Check preview/staging parity, config/secret differences, feature flags and environment protections.\n4. Design staged rollout with observation metrics and explicit abort/rollback thresholds appropriate to impact.\n5. Require actual approval before initiating deploy, rollback, DNS, database or public traffic changes.\n6. If authorized tools exist, observe deployment status and preserve evidence; otherwise provide the plan without claiming execution.\n\n## Non-negotiable checks\n- Deploy success is not proof of application health.\n- Do not assume schema rollback is safe.\n\n## Deliverable\nRunbook with preflight, launch, smoke, canary, rollback/forward-fix and owners.\n\n## References\n- Read `../../references/deployment-and-rollout.md` when relevant.\n- Read `../../references/release-gates.md` when relevant.\n\nOnly claim tests, browser access, scans, deployments or specialist execution supported by actual tool evidence. Retain original user constraints and avoid unsolicited code changes.\n"
}