Launch Cal

@sites Build and deploy an internal workspace app called Launch Cal.

Use the company’s connected Slack, Google Drive, Notion, and Google Calendar context to organize upcoming product and feature launches. Use D1 for cached launch records and normalized source references. If live source ingestion is not available during the initial build, create realistic representative launch records that demonstrate the intended workflow.

The primary experience should be a polished monthly calendar view, not a generic dashboard. Group launch items by target date and show each item as a compact colored block. Use distinct accent colors for each product area. Each calendar block should surface the launch type, title, owner initials, status, and dependency-risk indicator.

Add:
- A top navigation bar with the Launch Cal brand, a global search field, and the current user avatar.
- Month navigation with previous, next, and Today controls.
- A filter toolbar for team, status, surface, dependency risk, and source freshness.
- A launch count and a dependency-risk legend.
- A footer noting that records refresh from Slack, Drive, Notion, and Google Calendar.

Keep the page header intentionally minimal:
- Show only the title “Upcoming launches.”
- Do not add an eyebrow label above the title.
- Do not add a subtitle below the title.
- Do not show a “D1 cache live” badge, sync timestamp, or overflow dot menu in the top navigation.

Each launch calendar item must open a detailed side-panel modal with:
- Status and dependency-risk badges
- Launch title and summary
- Owner, launch date, and launch type
- Interactive launch checklist with completion progress
- Normalized source links back to Slack, Drive, Notion, and Google Calendar
- Relevant docs
- Dependencies
- Go-to-market notes
- Blockers
- Last updated time
- Connected-source count

Design direction:
- Modern internal product-tool aesthetic
- Warm off-white background with subtle borders and restrained shadows
- Functional, information-dense calendar layout
- Colored UI blocks for launch items
- Clean typography and compact spacing
- Avoid unnecessary dashboard cards or decorative chrome
- Make the first viewport feel immediately useful and visually polished

Persist checklist updates in D1. Keep the normalized source-reference model suitable for future refresh jobs.

Build, validate, and deploy the finished app. Make it accessible to all active users in the workspace.