Admin Panel (Mission Control)

Mission Control is the Lorapok Labs operations dashboard at https://cursor-dev.lorapok.tech.

Authentication

Google sign-in, email magic link, or email/password (Firebase Auth)
Only allowlisted admin emails can access /dashboard/* (invite-only; checked before sign-in)
Master admin is configured via ADMIN_MASTER_EMAIL
Login page shows a read-only Sign-in & infrastructure panel (LoginInfraPanel) with live /api/health indicators

Only the master admin can trigger:

Deploy — publish an existing git tag to marketplaces (opt-in; the normal marketplace path)
Rollback — restore a prior tag as a new patch release (+ marketplaces when opted in)
Infra — redeploy Mission Control / marketing site without marketplace publish

Push to main may prepare tags and redeploy Mission Control; it never publishes marketplaces (DEPLOY-04).

Non-master admins can view deployment history and runtime logs but cannot submit dispatch forms.

Module	Purpose
Overview	Health, marketplace sync, KPIs, download breakdown, service analytics hub (ANALYTICS-01)
Reports	Printable status report + service analytics hub cards
Deployments	Trigger publish or rollback workflows with live runtime log preview
Notices	Enable/disable development notices on the marketing site
Mailbox	Outbound mail log, branded HTML templates, compose & test
Logs	Unified API/mail/system explorer (LOGS-01): severity, source, time range, search, CSV export; ACL audit tab
Team	Admin allowlist management
Docs	In-app architecture reference

When dispatching a release or deploy, choose the target marketplace:

Market	Destination
`Both`	Open VSX + VS Code Marketplace
`Open VSX`	Canonical `lorapok-labs` listing
`VS Code Marketplace`	`LorapokLabs` publisher
`Firefox AMO`	Browser extension via `web-ext sign`

cd website/admin
cp .env.example .env
npm run dev

Dev server: http://localhost:5173 — API routes are served by vite-dev-api.mjs.

Mission Control is installable as a PWA. After manifest updates, reinstall or clear site data to refresh the shell cache.