Update to Web App QA & Release Copilot

{
  "description": "Choose targeted regression coverage from changed code, dependency graphs and business risk.",
  "included_files": [],
  "name": "plan-regression",
  "skill_md_contents": "---\nname: plan-regression\ndescription: Choose targeted regression coverage from changed code, dependency graphs and business risk.\n---\n\n# Plan Regression\n\n**Use when:** A PR, feature flag, dependency update, database migration or bug fix has changed and the user needs a bounded regression plan.\n\n## Workflow\n1. Inventory files/routes/services, schema migrations, config, dependencies and intended behavior changes.\n2. Trace upstream/downstream consumers, feature flags, permissions and shared components; separate direct from adjacent risk.\n3. Classify scenarios: Must retest; Targeted regression; Smoke only; Out of scope. Make exclusions explicit.\n4. Prioritize by likelihood, severity, reversibility and frequency of affected user journeys.\n5. State execution responsibility and CI/environment requirements, then propose a fast pre-merge suite plus a post-deploy smoke set.\n6. For a risky migration, include data reconciliation, snapshot/backups, forward fix and rollback constraints.\n\n## Non-negotiable checks\n- Never default to an unrelated full regression suite.\n- Do not claim scope completeness without source or dependency evidence.\n\n## Deliverable\nRisk-ranked test matrix and what is deliberately excluded.\n\n## References\n- Read `../../references/scope-and-risk.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"
}