This post exists for one job: prove the static deployment path emits a real article and a real tag page before nginx and Traefik get blamed for missing content.
The build should generate /blog/production-deployment-baseline/ and /blog/tags/it/. The draft template should stay dark. If either check fails, the problem belongs in the content pipeline, not in production folklore.
No CMS, no runtime routing, no JavaScript ceremony. Just Markdown, Astro static paths, and files nginx can serve over a bad connection.