v1.0.0 release readiness epic: final hardening and publication checklist

[cdcavell]

Context

This epic consolidates the release-readiness evaluations for bringing the current v0.4.2 baseline to a defensible v1.0.0 release.

The attached assessments agree that the repository is already technically mature, but the remaining v1.0.0 gap is broad: documentation consistency, CI/CD publication, container production readiness, template packaging, archival/citation metadata, ADRs, governance, supply-chain hardening, and consumer-experience polish.

Goal

Use this issue as the parent tracking issue for final v1.0.0 readiness work before generating the release.

Done When

• A v1.0.0 milestone exists or an equivalent project tracking view is configured.
• All blocker child issues are closed before tagging v1.0.0.
• High-priority child issues are either closed or explicitly deferred with rationale.
• Release publication flow has been dry-run validated before the v1.0.0 tag.
• README, DocFX, release notes, package metadata, and archival metadata agree with the shipped state.
• The final release produces a usable template package, container artifact, SBOM/provenance assets, and citation/archive path.

Suggested Labels

release-readiness, v1.0.0, priority/blocker

References

• NetCoreApplicationTemplate v1.0.0 Readiness Assessment
• Copilot supplemental readiness assessment
• Gemini supplemental readiness assessment
• Meta supplemental readiness assessment