# Release-note fragments are now checked by CI, not just local hooks

Every release ships with release notes assembled from per-PR fragment files. If one fragment is malformed, the release pipeline jams — and not just for that one change: EVERY release for EVERY agent stops until someone finds and fixes the bad fragment. We had local protection (a check that runs on your machine before you push), but local checks can be bypassed — merging from the GitHub website or with admin rights skips them entirely, which is exactly how a bad fragment reached the main branch twice. Now the same fragment validation also runs on GitHub's servers as part of the required CI checks on every PR and on main itself: a bad fragment turns the checks red immediately, named and attributable, instead of silently waiting to jam the next release.
