governance(AGENTS.md PD15): align the bold lead with the amended reserved-act list

The lead read "... or triggers a release workflow", which forbade the
fleet-write relay's refresh stroke that the amended list admits. It now
reads "... or triggers a release". The list stays the definition: every
other release.yml lane and every other publish-capable workflow is still
reserved by name. Ruling record 6160857949 (letter A: one rule text that
matches one mechanism); the seat's answer to the report's open question
chose this option. AGENTS.md stays at 1116 lines.

Claude-Session: https://claude.ai/code/session_01B7mrh59UAGffd7s9asUfoY
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

AGENTS.md

@@ -299,7 +299,7 @@ localStorage / auth gotchas.
     approval, or a Tier S merge without a PASS record is a seat violation, filed and rolled back. No seat judges this.
 
 15. **⛔ A version release is performed by the maintainer, by hand — no AI seat publishes, tags, cuts a Release, or
-    triggers a release workflow, and none merges the Version Packages PR.** A rule that binds every seat lives here,
+    triggers a release, and none merges the Version Packages PR.** A rule that binds every seat lives here,
     not only in a lane-specific skill file. **Release-adjacent work stays open to every seat**: the release board,
     `.objectui-sha` pin bumps, version reconciliation, writing changesets, compiling release notes when asked, and
     *verifying* release state (`npm view`, `git ls-remote --tags`) are ordinary tasks. What is reserved is the