Full Parity Milestone 8 Websites And Public Operations Evidence

Milestone 8 tracks public websites, registry publication, deployment reports,

redirects, search, metadata, rollback evidence, and public operations docs.

Current state: current-static-ops for static websites. App-specific public

operations remain blocked by Milestone 6 and Milestone 7 closure.

Gate

Generate the evidence ledger:

make full-parity-milestone8

Check the milestone evidence:

make full-parity-milestone8-check

The gate validates the static website evidence files, publish reports, rollback

reports, redirect/search/sitemap artifacts, post-commit redeploy hook, roadmap

status, and public docs.

Current Evidence

• deploy/static-sites/0x0-publish-report.html
• deploy/static-sites/libs-publish-report.html
• deploy/static-sites/jmp0x1b-publish-report.html
• deploy/static-sites/completion-report.html
• deploy/static-sites/redirect-check-report.html
• parity/milestone8-websites.tsv

Existing focused gates remain the deployment and UX gates:

• make public-docs-milestone-8-check
• make public-docs-milestone-9-check
• make static-site-0x0-redeploy-check
• make public-site-build-check
• make public-site-link-check

Closure Rule

Milestone 8 static-site evidence can be current while app-specific public

operations remain blocked. Final public operations closure waits for Index and

Kukulkan production artifacts to close their unresolved gap rows.

Documentation Impact Review

Website, registry, redirect, metadata, search, sitemap, rollback, deployment,

or public operations behavior changes must update this file,

docs/public-site-release-checklist.html, site/release.html,

docs/feature-support-matrix.html, and docs/release-notes.html in the same

change unless the ADR/RFC explains why a location is unaffected.