Gate the canonical release workflow on full same-commit readiness

[ayden94]

Context

The canonical publish workflow is the sole release authority for the pending i18n patch.

Selected audit purposes:

• bug-finding
• refactoring
• feature-addition
• contract-api
• architecture-boundary
• tests-edge
• docs-book-sync
• release-impact
• nestjs-migration-gap
• comprehensive

Evidence

• .github/workflows/ci.yml:4
• .github/workflows/release.yml:38
• .github/workflows/release.yml:48
• docs/contracts/release-governance.md:39
• docs/contracts/release-governance.md:130

Contract Impact

A main commit can be published without the semantic verification required by release governance.

Affected surfaces:

• release-workflow
• stable-publish
• i18n-remote-loader

Preserve-Contract Resolution Direction

Run verify:release-readiness or an equivalent reusable same-SHA gate before changesets/action and govern the ordering.

Affected Packages

• @fluojs/i18n

Why Now

A pending i18n behavior patch relies on tests that the publish job does not run or depend on for the exact commit.

---

Search run: search-2026-08-24T094852+0900-i18n
Draft: D8