[codex] Fix calendar AI stability and mobile event workflows

[freddy-tama]

Summary

• Hardened frontend API requests with timeout handling, safe error decoding, stale-token cleanup, and auth-expired events.
• Added rich event details end-to-end: description, safe meeting URL, priority, tags, reminders, ICS import/export support, and an additive Supabase migration.
• Replaced the old command bar flow with a persistent AI calendar chat, clarification choices, structured event cards, explicit mutation confirmations, and native assistant calendar tools.
• Added event hover/tap previews, Gmail search links, context-menu actions, Android-visible overflow actions, foreground reminders with in-app fallback, and mobile safe-area/touch-target polish.

Root cause

The production-facing app was fragile because calendar/AI fetches could hang or keep stale credentials, assistant mutations could silently choose an ambiguous event, event records did not carry the detail/reminder/link metadata needed by the UI, and several calendar actions were hover/context-menu only on touch devices.

Rendered QA also caught a desktop event-dialog regression from an overly broad mobile bottom-sheet class (sm:static); this PR restores desktop centering and adds a regression test.

Migration notes

Apply supabase/migrations/20260706120000_event_details.sql before deploying the frontend/backend together. The migration is additive and introduces safe defaults for the new event detail fields.

Verification

• python -m unittest discover -s tests -v — 54/54 passed
• npm test — 14/14 passed
• npm run lint — 0 errors / 13 existing warnings
• npx tsc --noEmit — passed
• npm run build — passed
• Rendered QA in the in-app browser:
  • desktop dashboard loaded with clean console
  • AI chat opened and answered a read-only calendar question
  • event editor displayed rich fields and desktop centering after fix
  • 412×915 mobile view used day calendar, AI drawer, bottom-sheet editor, sticky footer, and rich fields without console errors

Known limitations

• Gmail integration is a safe pre-filled Gmail search link only. Automatic Gmail meeting-link extraction would require a connected Gmail OAuth flow/scope and is not enabled here.
• Browser notifications require a user-initiated permission grant; blocked/unsupported browsers use the in-app fallback reminder card.

[vercel]

@codex is attempting to deploy a commit to the bagusardinp-3679's projects Team on Vercel.

A member of the Team first needs to authorize it.