Admin management

Admin surfaces for the Calendar live under the Founder Account dashboard (admin role). Three workflows: submission triage (verify or reject submitted events), event editing (update verified events), and coverage planning (flip coverageEligible + coverageStatus).

Submission triage queue

• List view: every CalendarEvent with verificationStatus='pending' or 'needs_info'. Sorted oldest first to enforce FIFO.
• Per row: title, organizer, country, category, startDate, submitterEmail, sourceUrl. Inline buttons: Verify / Request Info / Reject.
• Verify action: opens the full editor with the 3-gate checklist surfaced. Editor must check all three before "Publish" enables.
• Request Info action: sends a templated email to the submitter listing the missing/unclear fields. Status flips to 'needs_info'.
• Reject action: requires a free-text reason. Status flips to 'rejected'. Submitter is emailed the reason.

Event editor

• Form mirrors the CalendarEvent interface — 30+ fields grouped into the 11 clusters. Bilingual fields show side-by-side EN | AR inputs.
• Cross-module reference pickers: type-ahead search across Founders / Startups / Editorial / Opportunities / Files. Selected IDs render as chips with title preview.
• Save action bumps updatedAt + (if status flips to verified) sets lastVerifiedAt = now.
• Edit history: every save creates a versioned record. The previous version is restorable for 90 days.

Coverage planning surface

For events with editorialPriority='featured' or 'spotlight', admin can flip coverageEligible=true and set coverageStatus='planned'. This adds the event to the Events Coverage editorial pipeline. When the coverage article publishes (in the separate Events Coverage admin surface), coverageStatus auto-flips to 'covered' and the article becomes the canonical post-event reference linked from the event details page.