Skip to main content
Contacts (apps/contacts) hosts tutoring workspaces that a customer uses daily. Vercel remains its production runtime. This page records the state so that nobody mistakes the candidate for a cutover-ready app.

State

Cutover packet (not ready)

Do not attach a route for Contacts from the candidate. The candidate Worker answers 503 unless CONTACTS_START_CANDIDATE=staging on the exact staging origin, and forwards to Next, so it would add a hop in front of Vercel with no cost saving. A real cutover needs the native conversion, the sealed artifact, signed-in staging acceptance of tutoring, feedback, billing and /users/reports, and a production profile (Worker name, host, bindings and secret names, as in Finance).

Rollback

Nothing has been switched, so the production rollback is unchanged: the immutable Vercel deployment already serving contacts stays in place. Any future cutover captures the current Vercel deployment id, source SHA and DNS record before the flip and rolls back by removing only the Contacts Worker route.

Smoke (current Vercel production)

Signed-in checks of /users/reports use a disposable workspace, never customer data.