chore: prepare v1.27.3 release and guard template publishing

AGENTS.md

@@ -67,9 +67,10 @@ docs/               # Bilingual documentation (English + Simplified Chinese)
 ## Versioning
 
 - Release tags identify actual downloadable packages; the compatibility matrix distinguishes released tags from source-only fixes
-- The current published release is **v1.27.2**; it has a push-notification bug in Bloom, Ember, and Heritage on Gitea 1.27.1+. The fix is on `main` and verified against Gitea 1.27.3. The quick-reference table in `COMPATIBILITY.md` lists the `main (unreleased)` row first; the tracker workflow updates that row by position
+- The current release is **v1.27.3**, verified against Gitea 1.27.3; it fixes the push-notification bug in Bloom, Ember, and Heritage that affects v1.27.2 on Gitea 1.27.1+. The quick-reference table in `COMPATIBILITY.md` lists the active release first; the tracker workflow updates that row by position
 - When a new Gitea version is checked: update the top `COMPATIBILITY.md` row and README badge; keep unreleased fixes distinct from the published release, and update verified/tested wording only after verification
 - Tag a new release (`vX.Y.Z`) only when the template content itself changes — the release workflow packages automatically on tag push
+- Before tagging, add `.github/release-notes/vX.Y.Z.md`; the release workflow validates the file, runs `go test ./...`, and publishes those reviewed notes with the archives
 - Keep the `TRACKER:` markers in `COMPATIBILITY.md` / `README.md` adjacent to their rows so the automated workflow keeps parsing them
 
 ## Commit Conventions