Gate D - Release Integrity

[flyingrobots]

Contract

Echo 1.0 must ship from a pinned, reproducible, cross-repository compatibility set with package, documentation, upgrade, rollback, audit, and release evidence complete.

Owner

Canonical repository: echo.

Executable check

A release-gate workflow or command must verify the pinned compatibility set and return pass/fail.

Expected final shape:

cargo xtask test-slice echo-1.0-release-proof

Required evidence

• echo-convergence.lock or equivalent pinned compatibility manifest.
• Clean-room reproducible build report.
• Package verification output.
• Documentation verification output.
• Upgrade and rollback test output.
• Gate A/B/C evidence bundle references.
• Release candidate artifact digests.

Negative cases

• Release candidate generated from an unpinned dependency set is rejected.
• Missing gate evidence blocks release.
• Documentation or package verification failure blocks release.
• Upgrade/rollback failure blocks release.

Compatibility set

Must pin exact participating repository commits, protocol/profile versions, artifact schema versions, package versions, and evidence workflow runs.

Pass rule

Pass only when all four release gates are closed by evidence-bearing PRs and the release candidate is generated from the pinned compatibility set.

[coderabbitai]

🔗 Related PRs

#265 - chore: update CHANGELOG and finalize Lock the Hashes milestone [merged]
#529 - Add Hello Echo demo and docs lifecycle policy [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!