3 items across 3 sections
Deliberately re-cause the deployment failure from edge-runtime-deployment-failure: add one runtime export to a next/og metadata image handler, capture the failure, then revert. Determine for yourself whether it surfaces locally or only on deploy.
How the AI Execution Lab Vercel deployment pipeline evolved from initial setup through two documented build failures to a stable production configuration — covering edge runtime failure, next-mdx-remote v6 blockJS, environment variable scoping, preview workflows, and current build performance.
export const runtime = 'edge' in app/opengraph-image.tsx blocked the entire Vercel deployment. Took 23 minutes to identify and revert.