docs(24): create phase plan

.planning/ROADMAP.md

@@ -685,15 +685,27 @@ Phases execute in numeric order. v1.0 (Phases 1-9.1) shipped 2026-07-10. v2.0 (P
 **Plans:** 7 plans in 4 waves
 
 Plans:
+**Wave 1**
+
 - [ ] 24-01-PLAN.md — Foundation: AWS SDK install, migration 102 (zones/records/history/audit tables), shared types, credential factory, BWS + DNS-egress checkpoint *(wave 1)*
+
+**Wave 2** *(blocked on Wave 1 completion)*
+
 - [ ] 24-02-PLAN.md — Route53SyncService: zone/record mirror sync with pagination, soft-delete, and `sync_detected_drift` change history *(wave 2)*
 - [ ] 24-03-PLAN.md — Record validation (D-01 NS/SOA allowlist, AWS error sanitizer) + pending/committed/failed audit lifecycle persistence *(wave 2)*
 - [ ] 24-04-PLAN.md — Health check: auth probe + D-12 live NS-delegation comparison, registered in integration-health *(wave 2)*
+
+**Wave 3** *(blocked on Wave 2 completion)*
+
 - [ ] 24-05-PLAN.md — `/api/route53/*` read routes, sync trigger, and CRUD write routes with `requireAdmin()` gating *(wave 3)*
 - [ ] 24-06-PLAN.md — Scheduler entries (`route53-incremental`, `route53-full`) + `/admin/sync` tile *(wave 3)*
+
+**Wave 4** *(blocked on Wave 3 completion)*
+
 - [ ] 24-07-PLAN.md — `/admin/sync/route53` detail page, record editor dialog, end-to-end phase verification *(wave 4)*
 
 **Success Criteria:**
+
 1. Route 53 hosted zones and records sync into Postgres on a schedule, matching AWS as source of truth
 2. Create/update/delete operations initiated from Pulse propagate to Route 53 via the AWS API
 3. Every sync and CRUD operation is logged with actor, timestamp, and before/after values

.planning/STATE.md

@@ -2,10 +2,10 @@
 gsd_state_version: 1.0
 milestone: v3.0
 milestone_name: Phishing Triage Automation
-status: Awaiting next milestone
+status: executing
 stopped_at: Phase 24 context gathered
-last_updated: "2026-08-05T22:31:11.421Z"
+last_updated: "2026-08-05T23:18:04.601Z"
-last_activity: "2026-07-21 — Completed quick task 260721-n49: fix classifier to resolve per-company Mimecast tenant instead of always using the global tenant"
+last_activity: 2026-08-05 -- Phase 24 planning complete
 progress:
   total_phases: 9
   completed_phases: 9
@@ -27,8 +27,8 @@ See: .planning/PROJECT.md (updated 2026-07-14)
 
 Phase: Milestone v3.0 complete
 Plan: —
-Status: Awaiting next milestone
+Status: Ready to execute
-Last activity: 2026-07-21 — Completed quick task 260721-n49: fix classifier to resolve per-company Mimecast tenant instead of always using the global tenant
+Last activity: 2026-08-05 -- Phase 24 planning complete
 
 ## Performance Metrics