Release process and deployment gates

A deployment is not considered certified until repo sync checks, environment contracts, smoke tests, upload coverage, parity checks, and release manifest verification all pass for the same candidate SHA.

Rollback targets are captured before deploy, post-deploy provenance is verified from runtime endpoints, and web search must remain disabled unless the managed backend is reachable and the explicit proof step passes.

These gates keep local development, staging, and production aligned so release status is based on runtime truth instead of documentation drift.