docs: add v0.6 "full event read" milestone before v1.0

Plan to surface every readable CalendarContract field (reminders, status, availability, attendee role + self-status, timezone, URL, access level) in the detail view before write support. Recurrence-override badges and CATEGORIES/ATTACH stay out (the former folds into v2, the latter is a provider limitation). Noted only — implementation comes later. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
docs: cut jump-to-date (M2) from V1 scope
2026-06-10 23:35:02 +02:00 · 2026-06-10 23:27:21 +02:00
5 changed files with 44 additions and 13 deletions
--- a/.planning/REQUIREMENTS.md
+++ b/.planning/REQUIREMENTS.md
@@ -17,7 +17,7 @@ See full design spec: `docs/superpowers/specs/2026-06-08-calendar-app-design.md`
 - [ ] Day view (S3)
 - [ ] Event Detail Sheet (S4)
 - [ ] Multi-Calendar Filter (M3)
- [ ] Today button + Jump-to-Date (M2)
+- [x] Today button (M2) — shipped v0.5; Jump-to-Date **cut from scope**
 - [ ] View-Switcher (M1)
 - [ ] Settings screen (M4)
 - [ ] Empty / no-permission / no-calendars states
--- a/.planning/ROADMAP.md
+++ b/.planning/ROADMAP.md
@@ -9,16 +9,41 @@
 | v0.3 | Month + Week + Day views, view switcher | complete |
 | v0.4 | Event Detail (S4) + humanized recurrence | complete |
 | v0.5 | Calendar filter (M3) + Settings (M4) | complete |
-| v1.0 | Polish + jump-to-date (M2), F-Droid release | pending |
+| v0.6 | Full event read — surface every readable field | pending |
+| v1.0 | Polish pass, F-Droid release | pending |

 Delivery ran ahead of the original table: Day view (S3) shipped in v0.3 and
 Event Detail (S4) in v0.4, so the Filter/Settings milestone became v0.5.
-Jump-to-date (M2) was deferred out of v0.5 and folds into the v1.0 polish pass.
+
+Jump-to-date (the date-picker half of M2) was **cut from scope** and will not
+ship. The "Today" half of M2 already shipped in v0.5 (drawer entry).
+
+## v0.6 — Full event read
+
+Round out the read-only model so a detail view shows everything the system
+actually stores, before write support starts. Scope = `CalendarContract`
+columns we don't yet read/display:
+
+- **Reminders** (`VALARM`) — read `CalendarContract.Reminders`, list lead times
+- **Status** — Confirmed / Tentative / Cancelled (cancelled shown struck-through)
+- **Availability** (`TRANSP`) — Free / Busy chip
+- **Attendee extras** — role (required / optional / organizer) + the user's own
+  `SELF_ATTENDEE_STATUS`
+- **Timezone** (`EVENT_TIMEZONE`) — shown only when it differs from the device zone
+- **URL** — tappable link card
+- **Access level / class** (private / confidential) — small chip (optional, trivial)
+
+Deliberately out of v0.6:
+- Recurrence exception / modified-occurrence badges — `Instances` already
+  resolves correct per-occurrence times for display; this only matters for
+  editing, so it folds into v2
+- `CATEGORIES`, `ATTACH` — not reliably exposed by `CalendarContract`
+  (provider limitation, not our choice)

 ## v1.0 — First Public Release

 All V1 features shipped, polished, on F-Droid. Read-only calendar.
-Remaining before v1.0: jump-to-date (M2) and a UI polish/QA pass.
+Remaining before v1.0: a UI polish/QA pass.

 ## v2.0 — Write Support

--- a/.planning/STATE.md
+++ b/.planning/STATE.md
@@ -5,8 +5,9 @@
 ## Status

 **Milestone:** v0.5 — Calendar filter (M3) + Settings (M4) (complete)
-**Phase:** All V1 screens and cross-cutting wiring done except jump-to-date
-(M2), which is deferred to the v1.0 polish pass
+**Phase:** All V1 screens done. Jump-to-date (date-picker half of M2) cut from
+scope. Next up is v0.6 — full event read (surface every readable
+`CalendarContract` field) — then a polish/QA pass before v1.0

 ## Progress

@@ -21,10 +22,13 @@
 - [x] Event-detail screen (S4) — full-screen, humanized recurrence
 - [x] Filter sheet (M3) — per-calendar visibility, grouped by account, persisted, applied centrally in the repository
 - [x] Settings (M4) — appearance (theme, dynamic colour, week start), language (per-app locales), about
- [ ] Jump-to-date (M2) — drawer entry still stubbed (deferred to v1.0)
+- [~] Jump-to-date (M2) — **cut from scope**; "Today" half shipped in v0.5, date-picker dropped

 ## Next

-1. Jump-to-date (M2) — date picker from the drawer, reachable on every view
+1. v0.6 — full event read: reminders, status, availability, attendee role +
+   self-status, timezone (when it differs), URL, access level. Read the
+   `CalendarContract` columns we don't yet pull and show them in the detail
+   view. (Planned, not started — implement another day.)
 2. UI polish / QA pass across all views before v1.0
 3. F-Droid release of v1.0
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -16,7 +16,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
  separate from the system VISIBLE flag) and applied centrally in the
  repository, so month/week/day re-filter live the moment a switch flips.
  The drawer was trimmed to just Today, the calendar filter, and Settings
-  (the stubbed jump-to-date entry was removed; M2 returns in v1.0)
+  (the stubbed jump-to-date entry was removed; jump-to-date was later cut
+  from scope entirely)
 - Settings (M4): a full-screen destination with
  - **Appearance** — theme (System / Light / Dark), Material You dynamic colour
    (auto-disabled below Android 12), week start (Automatic / Monday / Sunday)
--- a/docs/superpowers/specs/2026-06-08-calendar-app-design.md
+++ b/docs/superpowers/specs/2026-06-08-calendar-app-design.md
@@ -27,7 +27,7 @@ von Google Calendar gibt - speziell mit dem 2025er Expressive-Design.
 - 3 Hauptansichten: Monat, Woche, Tag
 - Event-Detail-Sheet (read-only Detailansicht)
 - Multi-Kalender-Toggle (Sichtbarkeit pro Kalender)
- Heute-Button + Jump-to-Date
+- Heute-Button (Jump-to-Date gestrichen, siehe Out-of-Scope)
 - Settings-Screen (Theme, Dynamic Color, Wochenstart, Sprache)
 - Permission-Flow für `READ_CALENDAR`
 - Empty-States und Error-Recovery
@@ -35,6 +35,7 @@ von Google Calendar gibt - speziell mit dem 2025er Expressive-Design.
 - Tests + CI ab Tag 1

 ### Out-of-Scope (V2+)
+- Jump-to-Date / Datum-Picker (aus V1-Scope gestrichen)
 - Event-Create/Edit/Delete (V2)
 - Home-Screen-Widget
 - Volltextsuche
@@ -202,9 +203,9 @@ fragt Repository nur für sichtbaren Range an - kein "alle Events der Welt".
 - Immer erreichbar von allen Hauptansichten
 - State persistent (zuletzt aktive Ansicht)

-**M2 - Heute / Springe-zu-Datum**
- Schnell zurück zu "heute"
- Springe zu beliebigem Datum via Datum-Picker
+**M2 - Heute**
+- Schnell zurück zu "heute" (Drawer-Eintrag, ausgeliefert in v0.5)
+- ~~Springe zu beliebigem Datum via Datum-Picker~~ — **gestrichen**, siehe Out-of-Scope
 - Erreichbar von allen Hauptansichten

 **M3 - Kalender-Filter (Bottom-Sheet)**