Astro Content Integrity Verification Post-Build

Astro's Markdown transformation pipeline shifted between major versions: 2.x relies on @astrojs/markdown with Shiki highlighting, while 3.x+ may alter frontmatter handling and default plugin configuration, changing output HTML structure. This means a verification script must target the specific Astro version in use.

A practical approach: run astro build --verbose to capture the processed file list, then compute SHA-256 hashes of normalized source Markdown (strip frontmatter, normalize whitespace) against normalized rendered HTML (remove generated IDs, data-astro-* attributes, and framework-specific classes). Store baseline hashes per version to detect drift after dependency upgrades or config changes.

Third-party remark/rehype plugins often break across major versions, so pin plugin versions in package.json and include them in the verification baseline.