Merge plan: tag v2 on the merge commit; consuming repos bump @v1 -> @v2 and drop continue-on-error in their own PRs (merging next), then hub.yaml status_check_contexts.
Flips the checker from warn-only to enforcing so the four wired repos can make the naming job a required status check (#557 WS6 hardening step).
- check.sh exits 1 on any violation; log prefix WARN -> FAIL
- dfritz break-glass exemption unchanged (early exit 0)
- tests assert exit codes + FAIL-line presence (20/20 green)
- README/action.yaml: v2 enforcing, v1 stays legacy warn-only; new warn-only wiring uses job-level continue-on-error
Merge plan: tag v2 on the merge commit; consuming repos bump @v1 -> @v2 and drop continue-on-error in their own PRs (merging next), then hub.yaml status_check_contexts.
The four wired repos flip the naming job to a required status check
(agenthub#557 WS6); a check that always exits 0 can never gate. v2 makes
the script exit nonzero with FAIL lines; warn-only stays available via
job-level continue-on-error or the legacy @v1 tag. dfritz break-glass
exemption unchanged.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Flips the checker from warn-only to enforcing so the four wired repos can make the naming job a required status check (#557 WS6 hardening step).
Merge plan: tag v2 on the merge commit; consuming repos bump @v1 -> @v2 and drop continue-on-error in their own PRs (merging next), then hub.yaml status_check_contexts.