SEO: enforce one publication boundary

[MaggieAppleton]

Summary

• define one literal publication boundary: only draft: true is private
• keep draft entries out of public routes, canonical version selection, landing pages, topics, generated indexes, feeds, and social images
• retain development-only draft previews and move /drafts behind a DEV-only optional route
• preserve ordinary names such as api-v1 and api-v2 as separate articles, including in version-history UI
• support flat and nested Now entries without route collisions
• add pure policy tests plus production-compiler regressions for the Now route

Stack

• Base branch: codex/seo-aeo-fast-html
• Exact base SHA: 651daf7
• Direct dependency: chore: add fast SEO HTML verifier #245
• Eventual target: main, reviewed oldest-first
• This PR is not authorized to merge or deploy

Verification

• node --test tests/*.test.mjs — 75/75 passed
• npm run generate-links — passed
• npx tsx src/scripts/generate-topics.ts — 36 topics generated
• npm run verify:html — 13/13 routes passed without requesting images
• npx astro check — 0 errors, 0 warnings, 28 pre-existing hints
• npm run build:local — passed at 9c528c0; 195 pages and 7,647 optimized images
• independent specification and code-quality reviews — clean
• production artifact audit — 23 drafts re-derived, 24 blocked HTML candidates and 23 blocked OG candidates checked, 199 rendered files scanned, zero draft artifacts or authoritative links found

Notes

• The first production-build attempt exposed two existing Astro compiler/hoisting edge cases in the Now route. Both received narrow fixes, regression coverage, and independent re-review before the successful full build.
• One pre-existing tweet embed could not be fetched during the build; Astro logged it without failing the build.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
maggieappleton-com-v3	Ignored		Sep 7, 2026 10:20am UTC