Update to Web App QA & Release Copilot

{
  "description": "Verify API contracts, state transitions and data correctness affected by a web release.",
  "included_files": [],
  "name": "audit-api-data",
  "skill_md_contents": "---\nname: audit-api-data\ndescription: Verify API contracts, state transitions and data correctness affected by a web release.\n---\n\n# Audit Api Data\n\n**Use when:** Requests involving API failures, frontend/backend inconsistencies, cache invalidation, migrations, persistence or data loss.\n\n## Workflow\n1. Map request/response contracts, schema versions, auth context, data shapes and client-visible error behavior.\n2. Inspect create/update/delete paths for validation, idempotency, retries, concurrency and stale cache behavior.\n3. For migrations, verify compatible rollout ordering, backfill, dual-read/write risks and rollback limits.\n4. Test data isolation and integrity in authorized staging/synthetic environments, avoiding destructive production checks.\n5. Design reconciliation queries or fixtures and identify monitoring signals for partial failures.\n6. Mark missing DB access as unverified; never infer rows, transactions or successful migrations.\n\n## Non-negotiable checks\n- Do not mutate production records without explicit approval and a rollback or forward-fix plan.\n- Never put PII into diagnostic artifacts unless authorized and minimized.\n\n## Deliverable\nContract matrix, integrity risks, replay/migration checks and evidence.\n\n## References\n- Read `../../references/api-data-integrity.md` when relevant.\n- Read `../../references/security-privacy.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"
}