[chpy04]

Refactor calendar events domain to use slim models

Related to https://nerdocs.atlassian.net/wiki/spaces/NER/pages/2231697435/Root+Cause+Analysis+EC2+OOMs

Models:

• BaseEvent: primitives, userCreated, teamType, scheduledTimes
• CalendarEvent: calendar grid and Your Events / Review Bookings tables. Member counts replace member lists
• EventDetail: event popup, edit modal, availability page. isCurrentUserOnEvent is computed in the DB
• UpcomingEvent: calendar sidebar and lead home "Upcoming Design Reviews"
• EventConflict, GuestEventInstance, UserEventAttendance

Endpoints

• Added: GET /events/my-conflicts, GET /events/reviews, GET /events/upcoming, GET /events/attendance
• Removed: GET /events, GET /event-members/:id, GET /event/:id/conflict
• POST /events/filter: filters by time range
• POST /events-paginated: takes a direction and runs one query; the cursor is (startTime, scheduleSlotId)
• ICS feed: only slots from the last 6 months onward
• Event mutations return 204; create returns { eventId }

Frontend

• The event popup and edit modal load EventDetail when opened instead of in initial page load
• Conflict banners load in the background instead of blocking the calendar page
• Your Events and Review Bookings load only when their tab is open

Bug fixes

• Add org check on GET /events and POST /events/filter
• uploadDocument permission check was always false
• scheduleEvent modified slots and availabilities before checking permission
• editEvent team type validation never failed (findMany)
• Guest events pagination repeated or skipped items

[wavehassman]

BANG