After confirming attendance (or revisiting an already-attending RSVP),
guests can add the event to Google, Outlook, Apple, or any iCalendar
client with one click.
- internal/calendar package builds an RFC 5545 VCALENDAR plus the three
provider deep-links from a narrow Event projection. Times are emitted
as Z-suffixed UTC; the UID is deterministic (event-uuid@guestguard)
so re-downloads update the same calendar entry instead of duplicating
- GET /access/{token}/calendar.ics returns the .ics with a slugified
filename in Content-Disposition; same rate-limit class as /access
- GET /access/{token} response now embeds google/outlook/yahoo/ics URLs
so the frontend doesn't re-encode per provider
- AddToCalendar.vue renders the four buttons; shown only when the
guest is attending (declined/maybe don't need a calendar entry)
- Unit tests cover ics field presence, RFC 5545 escaping (comma,
semicolon), CRLF line endings, explicit-end handling, omitted
optionals, provider URL shape, filename slugification
- Integration: ics download returns valid VCALENDAR with the event
UID + name; unknown token returns 404; /access embeds the links
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Guests can revisit their invitation link and change their response
or plus-ones up to 5 times. Each prior state is snapshotted into
`rsvp_revisions` and surfaced to the host via a per-guest history
modal on the event detail page.
- Migration 0007 adds rsvp_revisions + rsvps.edit_count (with down)
- RSVPRepo.Update wraps snapshot+update+counter in one transaction,
FOR UPDATE-locking the row so concurrent edits can't bypass the cap
- PATCH /rsvp/{token} re-runs the fraud check on every edit attempt
(different device on an edit is itself a signal)
- POST /rsvp no longer marks the token used — the link stays valid
so the guest can come back to edit
- GET /access/{token} now embeds the existing RSVP so the frontend
renders an edit form instead of a blank submit form on revisit
- New host endpoint GET /events/{id}/guests/{guest_id}/rsvp/history
- Frontend: rsvp/[token].vue toggles between summary + edit form,
surfaces edits-remaining; dashboard adds a "History" action on
responded guests opening a revision-trail modal
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Adds docs/TIER2_PLAN.md with the detailed 8-block sequencing for
post-launch work, and updates CLAUDE.md to reference both plan docs.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- docs/TIER2_PLAN.md: detailed sequencing for the 8 blocks of
Tier 2 work (editable RSVPs, calendar integration, multi-host,
branding, analytics, smarter fraud, reminders + broadcasts,
day-of check-in) with schema changes, endpoints, tests, and
effort estimates per block.
- CLAUDE.md: roadmap section now points at both TIER1_PLAN.md
and TIER2_PLAN.md.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Bring in the full GuestGuard build (Phase 1-3 + UX polish) and the
production roadmap (4-tier plan + Tier 1 sequencing doc).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- CLAUDE.md: 4-tier feature roadmap appended after the build-order
section (launch blockers → moat features). Future sessions
reference this to know which tier a new feature belongs to.
- docs/TIER1_PLAN.md: detailed sequencing for the 8 blocks of
Tier 1 work (auth, authz, rate limiting, notifications, CSV
import, billing, backups, privacy) with schema changes,
endpoints, tests, and effort estimates per block.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Kwaku Danso