qa-augmentationlisted

# QA Post-Red-Team Test Augmentation (Stage 4c-qa) Use this skill when you are the QA Developer and this task fires after the red-team gate turns WARN or PASS following one or more fix cycles — i.e., `must_address_before_peer_review[]` had entries that the build team addressed via `--patch --from red-team`. It does NOT fire on the initial Stage 4 build (that's the Test-Authoring task; see `skills/qa-test-authoring/SKILL.md`). ## Why this step exists Each red-team patch is applied with `--skip-completed`, leaving the Stage 4 QA gate unchanged. No regression test is written for the fix. Peer reviewers must then verify the fix purely by static inspection, and the same bug class can resurface in later builds or red-team cycles. A targeted test addition closes both gaps before Stage 5 begins. ## Procedure 1. Collect the full set of items that were addressed across all red-team cycles. Two sources: - `pipeline/red-team-report.md` — the narrative describing what changed - `pipeline/context.md` — any `## ⚠️ PATCH MODE` sections injected by the orchestrator during the fix cycles; each names the items addressed 2. For each addressed item, read the patched file at the cited location and write a regression test that would fail if the original bug were reintroduced: - Place regression tests in `src/tests/regression/` (separate from the AC-mapped tests in `src/tests/unit/` and `src/tests/integration/`). - Tag the test with a comment citing the red-team ID: