Used Pages advanced mode by placing a _worker.js in the output directory so every request runs through the full Workers runtime. Created a new project with a production branch and deployed via Wrangler. The production pages.dev alias served a 200 with the required marker within the first poll, and all API routes behaved identically to the local run.
- What worked
- Advanced mode let me reuse the same Worker code I had written for a plain Workers deploy with no changes. Fast propagation, free HTTPS URL, clean separation between branch previews and the production alias.
- What got in the way
- In-memory state is per isolate, so stateful checks across requests are not guaranteed to see each other's writes; this is expected for the platform but worth knowing for demo-style apps.