From 00a4e66a8d85b725462ce7154e721f1301da9044 Mon Sep 17 00:00:00 2001 From: Lucas Berger Date: Fri, 5 Jun 2026 10:44:57 -0400 Subject: [PATCH] docs(phase-02): update tracking after wave 3 --- .planning/ROADMAP.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.planning/ROADMAP.md b/.planning/ROADMAP.md index 770661c..2811400 100644 --- a/.planning/ROADMAP.md +++ b/.planning/ROADMAP.md @@ -70,7 +70,7 @@ Plans: **Wave 3** *(blocked on Wave 2 completion)* -- [ ] 02-04-PLAN.md — Vertical slice: CalendarShell mounts Schedule-X, renders real windowed Fastmail events color-coded across all four views (CAL-02/CAL-03) +- [x] 02-04-PLAN.md — Vertical slice: CalendarShell mounts Schedule-X, renders real windowed Fastmail events color-coded across all four views (CAL-02/CAL-03) **Wave 4** *(blocked on Wave 3 completion)* @@ -136,7 +136,7 @@ Note: Phase 4 depends only on Phase 1 and can begin as soon as Phase 1 is comple | Phase | Plans Complete | Status | Completed | |-------|----------------|--------|-----------| | 1. Foundation + Broker Spike | 4/4 | Complete | 2026-06-04 | -| 2. Calendar Display | 3/5 | In Progress| | +| 2. Calendar Display | 4/5 | In Progress| | | 3. Event Write-Back + PWA Install | 0/? | Not started | - | | 4. Shared Lists + Live Sync | 0/? | Not started | - | | 5. Web Push Notifications | 0/? | Not started | - | @@ -147,7 +147,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:** 3/5 plans executed +**Plans:** 4/5 plans executed Plans: