docs(03): record gap-closure completion (03-09..03-12) in STATE + ROADMAP
This commit is contained in:
@@ -78,10 +78,10 @@ Plans:
|
|||||||
|
|
||||||
**Gap-closure waves** *(from 03-REVIEW.md — write path was broken end-to-end; Gate 2 / 03-08 is blocked on these)*
|
**Gap-closure waves** *(from 03-REVIEW.md — write path was broken end-to-end; Gate 2 / 03-08 is blocked on these)*
|
||||||
|
|
||||||
- [ ] 03-09-PLAN.md — Route layer: align zod schema to client title/start/end contract (CR-01) + real OIDC iss/sub→users.id resolution on all 5 handlers (CR-06) [wave 1]
|
- [x] 03-09-PLAN.md — Route layer: align zod schema to client title/start/end contract (CR-01) + real OIDC iss/sub→users.id resolution on all 5 handlers (CR-06) [wave 1]
|
||||||
- [ ] 03-12-PLAN.md — PWA EventForm: edit-mode population + recurrence preselect (WR-03), zone-consistent dates (WR-05), real focus trap (WR-07); PWA-01/02 install assets verified [wave 1]
|
- [x] 03-12-PLAN.md — PWA EventForm: edit-mode population + recurrence preselect (WR-03), zone-consistent dates (WR-05), real focus trap (WR-07); PWA-01/02 install assets verified [wave 1]
|
||||||
- [ ] 03-10-PLAN.md — Worker dispatch: build real VEVENT via buildVeventString + all-day DTEND+1 (CR-02/WR-04), fail closed on bad creds (CR-03), backoff index + randomUUID (WR-01/WR-08) [wave 2, after 03-09]
|
- [x] 03-10-PLAN.md — Worker dispatch: build real VEVENT via buildVeventString + all-day DTEND+1 (CR-02/WR-04), fail closed on bad creds (CR-03), backoff index + randomUUID (WR-01/WR-08) [wave 2, after 03-09]
|
||||||
- [ ] 03-11-PLAN.md — Outbox durability: durable create-before-delete (CR-04), drain concurrency guard (CR-05), fresh-etag-before-PUT (WR-02) [wave 3, after 03-10]
|
- [x] 03-11-PLAN.md — Outbox durability: durable create-before-delete (CR-04), drain concurrency guard (CR-05), fresh-etag-before-PUT (WR-02) [wave 3, after 03-10]
|
||||||
|
|
||||||
**UI hint**: yes
|
**UI hint**: yes
|
||||||
|
|
||||||
@@ -168,7 +168,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 |
|
| 1. Foundation + Broker Spike | 4/4 | Complete | 2026-06-04 |
|
||||||
| 2. Calendar Display | 5/5 | Complete | 2026-06-05 |
|
| 2. Calendar Display | 5/5 | Complete | 2026-06-05 |
|
||||||
| 3. Event Write-Back + PWA Install | 7/8 | In Progress| |
|
| 3. Event Write-Back + PWA Install | 11/12 | In Progress| |
|
||||||
| 4. Shared Lists + Live Sync | 0/? | Not started | - |
|
| 4. Shared Lists + Live Sync | 0/? | Not started | - |
|
||||||
| 5. Web Push Notifications | 0/? | Not started | - |
|
| 5. Web Push Notifications | 0/? | Not started | - |
|
||||||
|
|
||||||
@@ -178,7 +178,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.
|
**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
|
**Requirements:** TBD
|
||||||
**Plans:** 7/8 plans executed
|
**Plans:** 11/12 plans executed
|
||||||
|
|
||||||
Plans:
|
Plans:
|
||||||
|
|
||||||
|
|||||||
+7
-7
@@ -3,13 +3,13 @@ gsd_state_version: 1.0
|
|||||||
milestone: v1.0
|
milestone: v1.0
|
||||||
milestone_name: milestone
|
milestone_name: milestone
|
||||||
status: executing
|
status: executing
|
||||||
stopped_at: Completed 03-05-PLAN.md
|
stopped_at: Completed 03-11-PLAN.md (gap-closure waves done; 03-08 Gate 2 human checkpoint remains)
|
||||||
last_updated: "2026-06-05T22:48:01.593Z"
|
last_updated: "2026-06-06T00:34:09.142Z"
|
||||||
last_activity: 2026-06-05
|
last_activity: 2026-06-06 -- Phase 03 execution started
|
||||||
progress:
|
progress:
|
||||||
total_phases: 6
|
total_phases: 6
|
||||||
completed_phases: 2
|
completed_phases: 2
|
||||||
total_plans: 17
|
total_plans: 21
|
||||||
completed_plans: 16
|
completed_plans: 16
|
||||||
percent: 33
|
percent: 33
|
||||||
---
|
---
|
||||||
@@ -26,9 +26,9 @@ See: .planning/PROJECT.md (updated 2026-06-03)
|
|||||||
## Current Position
|
## Current Position
|
||||||
|
|
||||||
Phase: 03 (event-write-back-pwa-install) — EXECUTING
|
Phase: 03 (event-write-back-pwa-install) — EXECUTING
|
||||||
Plan: 8 of 8
|
Plan: 11 of 12 (gap-closure 03-09/10/11/12 complete; 03-08 Gate 2 live/iOS human checkpoint remains)
|
||||||
Status: Ready to execute
|
Status: Gap-closure waves complete — write path now reachable end-to-end
|
||||||
Last activity: 2026-06-05
|
Last activity: 2026-06-06 -- Phase 03 gap-closure (03-09..03-12) executed and merged
|
||||||
|
|
||||||
Progress: [███████░░░] 65%
|
Progress: [███████░░░] 65%
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user