luckberg/familysync
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(phase-15): update tracking after wave 2

Browse Source
This commit is contained in:
Lucas Berger
2026-06-12 10:54:26 -04:00
parent c0c217019c
commit 0278e2080a
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.planning/ROADMAP.md
+3 -3
View File
@@ -288,7 +288,7 @@ Plans:
**Wave 2** *(blocked on Wave 1 completion)*
- [ ] 15-02-PLAN.md — ci.yml: `changes` (dorny/paths-filter@v4) + conditional api/harness + always-running `gate` aggregate (SC-1/SC-2, SC-3 YAML)
- [x] 15-02-PLAN.md — ci.yml: `changes` (dorny/paths-filter@v4) + conditional api/harness + always-running `gate` aggregate (SC-1/SC-2, SC-3 YAML)
**Wave 3** *(blocked on Wave 2 completion)*
@@ -314,7 +314,7 @@ Plans:
| 12. Initial Setup Wizard | v1.1 | 0/? | Not started | - |
| 13. Real Lint Gate (ESLint) | v1.1 | 3/3 | Complete | 2026-06-12 |
| 14. Desktop E2E Coverage | v1.1 | 1/1 | Complete | 2026-06-12 |
| 15. Doc-Only CI Skip + MD Lint | v1.1 | 1/3 | In Progress| |
| 15. Doc-Only CI Skip + MD Lint | v1.1 | 2/3 | In Progress| |
## Backlog
@@ -322,7 +322,7 @@ Plans:
**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/3 plans executed
**Plans:** 2/3 plans executed
Plans: