Compared the current hosted Command Center surfaces across Render and Vercel.
Checked the standalone Render URL https://sail-command-center.onrender.com, the monorepo Render app https://sail-command-center-app.onrender.com, the monorepo Render API https://sail-command-center-api.onrender.com, and the Vercel production URL https://projects-sam-aguiar-injury-lawyers.vercel.app.
The main finding is that there are three deployment lanes drifting:
samaguiar1982-cpu/projects, is the newest Sam-facing UI and uses command-center/ plus services/command-center-api/.SAIL OS build from commit 71a7c471, with Mission Control, Six Pillars, violet/fuchsia styling, and no matching /api/health or /api/dashboard-data route.samaguiar1982-cpu/sail-command-center, is a separate older hosted lane that still returns mock mode and the stale MVA signed MTD: 58 through its authenticated dashboard API.Created the comparison and recommendation doc at /Users/samaguiar/Documents/Projects/Repos/projects/docs/deployment-unification-render-vercel-2026-05-26.md.
Use the samaguiar1982-cpu/projects monorepo as the canonical source and Render as the canonical runtime for now. It already has the right two-service shape: a Next.js frontend in command-center/ and a FastAPI live-data backend in services/command-center-api/.
Vercel should either be paused or repointed to the monorepo command-center/ root as preview-only. The standalone sail-command-center Render service should be treated as archive or migration source, not as the current review surface.
Before calling Render fully canonical, migrate the corrected report-hygiene logic from /Users/samaguiar/Documents/Projects/Repos/sail-command-center into /Users/samaguiar/Documents/Projects/Repos/projects. The monorepo Render API is live to Litify, but its MVA signed counts currently differ from the prior verified source-hygiene pass, so the signed-MTD rule should be reconciled before moving a custom domain or presenting the number as final.
Render monorepo app returned 200 OK and rendered Sam's Operations Center.
Render monorepo API /api/health returned ok: true, version 0.2.0, sf_configured: true, and basic_auth_enabled: true.
Render monorepo API /api/data, using the vault Basic Auth credentials, returned Litify sections as live and snapshot status for pending areas.
Vercel production metadata showed the latest READY production deployment is commit 71a7c471. Recent deployments for newer commits were BLOCKED.
Vercel protected root was fetched through the Vercel share URL and confirmed as the older SAIL OS UI. Vercel /api/health and /api/dashboard-data returned 404 from that deployment.
Standalone Render /api/health returned 200 OK with data_mode: mock, and authenticated /api/dashboard-data still returned MVA signed MTD: 58.