feat: S8 local .ics calendar export (constitution-safe)#71
Merged
Conversation
buildIcs (pure, tested): meetings → a VCALENDAR the user imports into any calendar themselves — the local alternative to outbound Google Calendar sync (nothing leaves the box). GET /api/meetings.ics downloads it; a 'ייצוא ליומן (.ics)' link in the §6 Meetings column. Undated meetings skipped (need DTSTART). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
S8 · Local
.icscalendar exportThe final roadmap slice (#50, epic #58) — the constitution-safe reframe of the prototype's "connect Google Calendar" affordance.
Why not Google Calendar
The constitution's core principle is "all inference local, nothing leaves the box except the read-only WhatsApp link." Two-way Google Calendar sync is an outbound third-party cloud write — it would need a constitution amendment (the S8 memo on #58 laid out the options). So instead of outbound sync, S7's local
meetingsare exported as a standard.icsfile the user imports into any calendar themselves — ~80% of the value, nothing leaves the device automatically, no amendment needed.What changed
buildIcs(meetings, now)(pure, tested) — aVCALENDARwith aVEVENTper dated meeting (UID/DTSTAMP/DTSTART/SUMMARY/DESCRIPTION, RFC-5545 escaping, CRLF). Undated meetings are skipped (a VEVENT needs a DTSTART) — they still show in the in-app agenda.GET /api/meetings.ics— downloads the calendar (text/calendar,attachment; filename="catchapp.ics").Verified
The endpoint returns a real importable calendar — confirmed live:
200 text/calendar, a validBEGIN:VCALENDAR … BEGIN:VEVENT … DTSTART:20260620T090000Z … END:VCALENDAR.Note
Meeting
starts_atis currently null for most extracted meetings (S7 doesn't yet parse Hebrew dates from free text), so the.icsis sparse until a date-extraction follow-up lands — the mechanism is correct and constitution-safe; richer dates are additive.Tests / gate
buildIcsunit-tested (VCALENDAR shape, undated-skip, RFC escaping). Full suite green.Closes #58.
🤖 Generated with Claude Code