docs(03-03): complete write API surface plan — enqueue-only endpoints GREEN

2026-06-05 17:59:53 -04:00
parent 0a8222329e
commit 7398946aa8
16 changed files with 2168 additions and 10 deletions
@@ -102,7 +102,7 @@ Plans:
 **Wave 2** *(blocked on Wave 1)*

 - [x] 03-02-PLAN.md — TDD: VEVENT builder (vevent.ts, D-13 DATE/DATETIME + RRULE) + tsdav write wrappers (write.ts, D-12 broker boundary)
- [ ] 03-03-PLAN.md — Write API: POST/PATCH/DELETE events + GET sync-status, enqueue-only, D-03 ownership, D-04 edit-as-move pair (CAL-04/05/06/07)
+- [x] 03-03-PLAN.md — Write API: POST/PATCH/DELETE events + GET sync-status, enqueue-only, D-03 ownership, D-04 edit-as-move pair (CAL-04/05/06/07)

 **Wave 3** *(blocked on Wave 2)*

@@ -161,7 +161,7 @@ Note: Phase 4 depends only on Phase 1 and can begin as soon as Phase 1 is comple
 |-------|----------------|--------|-----------|
 | 1. Foundation + Broker Spike | 4/4 | Complete   | 2026-06-04 |
 | 2. Calendar Display | 5/5 | Complete    | 2026-06-05 |
-| 3. Event Write-Back + PWA Install | 2/8 | In Progress|  |
+| 3. Event Write-Back + PWA Install | 3/8 | In Progress|  |
 | 4. Shared Lists + Live Sync | 0/? | Not started | - |
 | 5. Web Push Notifications | 0/? | Not started | - |

@@ -171,7 +171,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:** 1/8 plans executed
+**Plans:** 3/8 plans executed

 Plans: