We've been tracking 12 test scenarios against the 2026-05-29 milestone. After auditing all SC-* grandchildren under ANSTRAT-1991, we found scenarios that should be tracked but weren't included in our milestone reporting.
1. 2026-05-29 milestone: 12 → 13 scenarios
Added AAP-70819 (SC-013 — Managed DB Failover / RDS / Azure DB), which was already Closed but wasn't being counted. This corrects our completion metric.
- Current score: 11/13 (85%)
- 2 remaining items still in Backlog:
- Both are DR/region-failure scenarios that share the same test run (
make disaster-recovery) and are blocked on adding a receptor connectivity metric to the SLO probe.
2. New 2026-06-05 milestone: 5 scenarios (Phase 1 DB/Backup)
These are Phase 1 grandchildren that were not previously tracked in any milestone. All are currently in Backlog:
| Key | Scenario |
|---|---|
| AAP-70820 | SC-014 — Measure DB Replica Lag for all Failover DB scenarios |
| AAP-70821 | SC-034 — Continuous WAL Archiving Robustness |
| AAP-70822 | SC-035 — Scheduled Full Database Backup |
| AAP-70823 | SC-036 — Point-in-Time Recovery from WAL Archive |
| AAP-70824 | SC-037 — DR-Region-Independent Backup Storage |
15 additional SC-* scenarios exist under Phase 2 epics (elastic execution, multi-AZ, remote execution, cross-region DR, DR runbook). All are in "New" status and are out of scope for these near-term milestones.