From 493d6daf6ce25f4bf400ee7bbe09a91096708ba1 Mon Sep 17 00:00:00 2001 From: lorentz Date: Wed, 5 Aug 2026 20:39:58 -0400 Subject: [PATCH] docs(phase-24): update tracking after wave 3 (plans 24-05, 24-06 complete) Co-Authored-By: Claude Sonnet 5 --- .planning/ROADMAP.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.planning/ROADMAP.md b/.planning/ROADMAP.md index ac1405d..3fc419e 100644 --- a/.planning/ROADMAP.md +++ b/.planning/ROADMAP.md @@ -682,7 +682,7 @@ Phases execute in numeric order. v1.0 (Phases 1-9.1) shipped 2026-07-10. v2.0 (P **Goal:** Sync DNS zones/records from AWS Route 53 into Postgres, support full CRUD back to Route 53 from Pulse, track record-level changes over time, log every sync and CRUD operation for audit, and integrate into the existing per-system sync section (scheduler, admin UI, health checks) alongside Autotask/Datto RMM/Veeam. AWS credentials are resolved via BWS (Bitwarden Secrets Manager), not plaintext env vars. **Requirements**: SC-1, SC-2, SC-3, SC-4, SC-5, SC-6 (the numbered Success Criteria below serve as this phase's requirement IDs — this project has no REQUIREMENTS.md) **Depends on:** Phase 23 -**Plans:** 4/7 plans executed +**Plans:** 6/7 plans executed Plans: **Wave 1** @@ -697,8 +697,8 @@ Plans: **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)* +- [x] 24-05-PLAN.md — `/api/route53/*` read routes, sync trigger, and CRUD write routes with `requireAdmin()` gating *(wave 3)* +- [x] 24-06-PLAN.md — Scheduler entries (`route53-incremental`, `route53-full`) + `/admin/sync` tile *(wave 3)* **Wave 4** *(blocked on Wave 3 completion)*