agilab-release-verification

Release readiness verification identifies and reports gaps between your current release state and declared contracts across PyPI, GitHub Releases, release proof, docs, coverage badges, and Hugging Face Space sync. It outputs a compact verdict with actionable steps to resolve blockers before publication.

A post-release alignment check validates proof freshness and Hugging Face Space sync to prevent stale or misleading release claims. It inspects public surfaces and release assets to ensure published artifacts match your declared contracts across all platforms.

Coverage badge failures occur when gaps exist between current release assets and declared contracts. Release verification checks badge statuses against actual public surfaces, identifying mismatches and providing actionable steps to realign your documentation with your release state.

Release verification applies to any release candidate and post-release checks. It validates top-level packages, provenance packages, and release artifacts by requiring access to workflow YAMLs, release_plan tooling, and public surfaces to generate a compact verdict.

Validating release contracts requires checking declared contracts against actual artifacts across PyPI, GitHub Releases, docs, and coverage badges. The verification process surfaces gaps between expected and actual states, providing gated checks and actionable guidance to enforce release discipline.

End-to-end release readiness verification requires access to workflow YAMLs, release_plan tooling, and public surfaces. It inspects release assets and validation of artifacts across your checkout to surface blockers and recommended actions before publishing.