Update to Web App QA & Release Copilot

{
  "description": "Verify that a deployed application remains healthy for real user flows.",
  "included_files": [],
  "name": "verify-postrelease",
  "skill_md_contents": "---\nname: verify-postrelease\ndescription: Verify that a deployed application remains healthy for real user flows.\n---\n\n# Verify Postrelease\n\n**Use when:** A deployment has occurred and the user wants smoke results, regression signals, monitoring verification or incident triage.\n\n## Workflow\n1. Identify deployed release and environment from actual deployment evidence, not a presumed version number.\n2. Check supported monitoring: errors, latency, availability, auth, conversion/critical workflow signals, dependencies and business metrics.\n3. Run approved synthetic smoke flows without destructive writes; use test tenants/fixtures where appropriate.\n4. Compare pre/post windows using matched traffic cohorts and observe canary/feature flag segments when applicable.\n5. If alarming metrics or critical failures appear, surface the rollback/forward-fix decision and approval requirements.\n6. State monitoring gaps and insufficient observation windows explicitly, avoiding “all clear” without evidence.\n\n## Non-negotiable checks\n- Do not invent health metrics or production test results.\n- Do not perform unauthorized live writes or rollback automatically.\n\n## Deliverable\nPost-release evidence, anomalies, incident escalation and recommended disposition.\n\n## References\n- Read `../../references/deployment-and-rollout.md` when relevant.\n- Read `../../references/evidence-model.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"
}