Scheduled detection half of the Vercel to Statuspage incident loop. It reads recent failed production Vercel deployments, writes one data.shared proposal for the first unhandled deployment, and notifies the owner to review whether customer communication is needed. It never creates or updates Statuspage incidents, rolls back deployments, promotes deployments, pauses projects, mutates domains or environment variables, or calls arbitrary APIs. Vercel native notifications and rollback controls own their native surfaces; this recipe only creates a Recued-visible cross-system proposal that an owner can approve or dismiss with create-approved-statuspage-incident-from-vercel.

Owner-invoked action half of the Vercel to Statuspage incident loop. It reads one awaiting_owner_approval proposal written by vercel-statuspage-incident-proposal, then either creates exactly one Statuspage incident from deterministic proposal copy or dismisses the proposal as no customer impact. Running this recipe is the owner's approval or decline. It takes no outward-facing action when there is no pending proposal or required Statuspage incident copy is missing.