The new pages are accessible when running the loader project on localhost.
In loader case, you need to somehow trigger a re-deploy after you publish a new version of your Plasmic project. This is explained in our Deployment and Automation docs: Deployments and automation | Learn Plasmic
When you use the Headless API, your Plasmic content is usually fetched at build-time and cached for lightning-fast initial pages loads. Therefore, to deploy updates from Plasmic, you need to trigger a re-deploy on your deployment platform.
We’ll be using webhooks to trigger a re-deploy when an editor publishes your project. Most deployment platforms already provide webhooks for triggering re-deploys. If your deployment platform doesn’t, you can still build custom automation to enable this behavior.
I see that in your Publish dialog, there are no webhooks configured. That possibly explains why the live app is unaware of the latest published version of the Plasmic project.