Bolt checkout broke after a deploy: run the path on every push
Checkout is a chain of redirects. One renamed button after a Bolt deploy is enough to stop revenue. Monitor the path, not the homepage.
Bolt apps often glue a cart to a Stripe Checkout URL. The deploy that changes the button from Checkout to Pay now looks like a copy tweak. It is a broken flow if your monitor is looking for the old words, and it is a broken product if customers can't find the new ones either.
The flow to describe
Add an item to the cart and reach Stripe checkout. The useful assertion is not a pixel match. It is that the browser URL actually lands on checkout, Stripe's host or your /checkout route, after the click.
Run it when the deploy hook fires
Daily is a backstop. The failure mode you care about is the deploy you just shipped. A webhook URL on the project lets Bolt, Vercel, or Netlify POST when the build is live. Free plans keep the URL and refuse the run. Starter and Pro run every enabled flow.
If the step fails twice, send one email. Include the screenshot of the cart page that did not advance, and a fix prompt that says to restore a path a customer can find rather than hard-coding the test selector into the product.