docs(05-06): complete reminderScheduler plan

.planning/ROADMAP.md

@@ -203,7 +203,7 @@ Plans:
 **Wave 4** *(blocked on Wave 3)*
 
 - [x] 05-05-PLAN.md — NOTIF-02 list-change slice: listChangeDispatcher + hook coalescer into mutations, reorder-silent (D-01/D-02/D-03)
-- [ ] 05-06-PLAN.md — TDD: NOTIF-01 reminderScheduler — shared-timed 15-min scan (query-enforced D-05), all-day excl, dedup, empty-set safe (D-05/D-06/D-07)
+- [x] 05-06-PLAN.md — TDD: NOTIF-01 reminderScheduler — shared-timed 15-min scan (query-enforced D-05), all-day excl, dedup, empty-set safe (D-05/D-06/D-07)
 
 **Wave 5** *(blocked on Wave 4)*
 
@@ -246,7 +246,7 @@ Note: Phase 4 depends only on Phase 1 and can begin as soon as Phase 1 is comple
 | 2. Calendar Display | 5/5 | Complete    | 2026-06-05 |
 | 3. Event Write-Back + PWA Install | 12/12 | Complete    | 2026-06-07 |
 | 4. Shared Lists + Live Sync | 6/6 | Complete   | 2026-06-09 |
-| 5. Web Push Notifications | 5/8 | In Progress|  |
+| 5. Web Push Notifications | 6/8 | In Progress|  |
 | 6. UX Polish | 0/? | Not started | - |
 
 ## Backlog
@@ -255,7 +255,7 @@ Note: Phase 4 depends only on Phase 1 and can begin as soon as Phase 1 is comple
 
 **Goal:** [Captured for future planning] Abstract the calendar backend behind a provider interface so Fastmail/CalDAV is one implementation among potentially many. Shipping with a single provider is fine, but the broker, sync, and event-expansion layers should be structured so additional providers (e.g. other CalDAV hosts, Google Calendar, generic ICS feeds) can be added without rework. Captures the "provider" seam as an explicit architectural concern.
 **Requirements:** TBD
-**Plans:** 5/8 plans executed
+**Plans:** 6/8 plans executed
 
 Plans: