verify the deployed URL

Verification runs against the deployed URL, never just localhost. Auth walls, deployment protection, CDN headers, and cookie behavior all differ from local serving — a feature can pass locally and be structurally broken in production conditions. Localhost once masked a week of video that no real phone could play.

A week of video playback “worked” on localhost once — and no real phone could ever play it, because the production host's cookie behavior broke the stream. The deployed URL is the only surface that tells the truth.

After every deploy: load the production URL, exercise the changed path, and only then use the word 'live.' The completion claim carries the URL — a place to go look — or it explicitly says 'committed, not yet pushed.'

The whole method is downloadable and adaptable — rules/verify-the-deployed-url.md inside the zip.