docs: fold #54 and #55 into v0.5.0 Chunk 2 command rewrites

Add performance/security testing (#55) and regression test suite (#54)
requirements to planning and retrospective command rewrites. Update
GitHub Issues table to reflect current status.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Jeffallan

docs/v0.5.0-plan.md

@@ -196,14 +196,15 @@ python scripts/update-docs.py --check
 
 ### Chunk 2: Decouple Non-Discovery Commands
 
-**Phase:** 2 (partial) | **Depends on:** Chunk 1 | **GitHub Issues:** #62
+**Phase:** 2 (partial) | **Depends on:** Chunk 1 | **GitHub Issues:** #62, #54, #55
 
 | What | Detail |
 |------|--------|
 | Rewrite in place | 5 existing commands — abstract Jira/Confluence operations |
 | Skip | `complete-sprint.md` — being deleted, no point decoupling |
 | Per-file changes | Add Phase 0 config resolution, abstract all hardcoded operations, add routing table |
-| Scope | 5 files, ~57 references abstracted |
+| Fold in | Performance & security testing integration (#55), regression test suite (#54) |
+| Scope | 5 files, ~57 references abstracted + testing sections added |
 
 #### Commands to Decouple
 
@@ -220,6 +221,29 @@ Each command gets:
 2. **Abstract operations** — All Jira/Confluence verbs replaced with generic verbs
 3. **Routing table** — Footer section pointing to backend-specific reference files
 
+#### Testing Integration (#54, #55)
+
+The following sections are added during the Chunk 2 rewrite — not as a separate chunk:
+
+**`planning:epic-plan`** — add to Testing Strategy section:
+- Performance baselines (p95 response time, page load, query time)
+- Performance SLAs (targets per metric)
+- Performance testing triggers (DB changes, API changes, large data, latency-sensitive features)
+- Security testing triggers (auth changes, PII handling, API changes, permissions)
+- Regression impact analysis (existing features at risk, affected flows, existing tests)
+
+**`planning:impl-plan`** — add per-ticket:
+- Performance test requirements (benchmarks, load tests, query performance targets)
+- Regression test requirements (existing tests to run, new tests to add, critical paths)
+- Security test flag (when ticket touches auth, input validation, file uploads, encryption)
+
+**`retrospectives:complete-epic`** — add metrics sections:
+- Performance metrics (API p50/p95/p99, slow queries, regressions, load test results)
+- Security metrics (vulnerabilities found by severity, remediated count, reviews conducted)
+- Regression metrics (suite size, pass rate, regressions caught pre-prod vs escaped, flaky test count)
+
+Note: Security and performance checks during execution are handled by the adversarial review phase (Layer 3 — `/review-ticket` and `/qa-validate`), not by modifying `execute-ticket` or `complete-ticket`. Automated CI execution of regression suites is a consumer-project CI concern, not a skill library concern.
+
 #### Verification
 
 ```bash
@@ -678,20 +702,21 @@ All 12 per-command YAML definition files created in Phase 1 (completed):
 |-------|-------------|----------|--------|
 | #62 | Core workflow generalization | 1, 2, 3 | Open |
 | #103 | Epic creation gap | 3 | Open |
-| New | Backend adapter reference files | 1 | To create |
-| New | Intake commands | 4 | To create |
-| New | Discovery command rework | 3 | To create |
-| New | Feature-forge integration | 5 | To create |
-| New | Namespace change + directory restructure | 6 | To create |
-| New | YAML workflow definition schema + DAG manifest | Pre | To create |
-| New | Narrative document restructure | 7 | To create |
-| New | CI portability check | — | To create |
+| #54 | Regression test suite integration | 2 | Open — folded into command rewrites |
+| #55 | Performance & security testing integration | 2 | Open — folded into command rewrites |
+| #119 | Backend adapter reference files | 1 | Open |
+| #120 | Intake commands | 4 | Open |
+| #121 | Discovery command rework | 3 | Open |
+| #122 | Feature-forge integration | 5 | Open |
+| #123 | Namespace change + directory restructure | 6 | Open |
+| New | YAML workflow definition schema + DAG manifest | Pre | Completed |
+| New | Narrative document restructure | 7 | Completed (#125) |
 
 ### Deferred to v0.6.0 (Global-to-Local Config Migration)
 
 | Issue | Description |
 |-------|-------------|
-| #50-55 | Context persistence, state validation, error recovery, shared templates, testing infra |
+| #50-53 | Context persistence, state validation, error recovery, shared templates |
 | #109 | Common-ground local storage |
 
 ### Deferred to v0.7.0+ (Enhanced Skill Routing + Common-Ground)