Say What Closing Keywords Do on Promotion and Where the Title Limit Ends - #4183

Summary

Title limit and bind words. The 72-character limit measures the authored title or subject, and the (#N) suffix GitHub appends at a squash merge sits outside it. The lowercase title-case bind-word list is marked exhaustive and gains with, as, via, into, over, and per. GOVERNANCE.md "Pull Request Title and Commit Message Conventions", comment-and-doc-style, and .github/copilot-instructions.md now agree.

Two headings capitalized a listed word, so they are lowercased, along with the README table-of-contents entry for one of them. Anchors are lowercase already, so no link moves. STANDUP.md "Hand Over What Only the Maintainer Can Supply" is left as it is. "Over" there is a phrasal-verb particle, not a bind word.

Closing keywords under the squash setting. The hub's squash_merge_commit_message reads PR_BODY (read live). So a feature pull request's body becomes its squash commit on develop. A closing keyword there closes its issue once the promotion brings that commit to main, whatever the promotion body says. branching-and-release-model and backlog-burndown both said such a keyword closes nothing, which is corrected here. The rules now state:

• what a keyword does in a feature body, and that a direct-push commit message behaves the same way;
• that the settled convention stands: a feature body or direct-push commit carries only the inert Closes on promotion: line, and the promotion body owns the closing keywords;
• that a keyword fires inside a sentence that negates it, with the safe rewording;
• a mechanical closing-set check after each promotion body write, again when the promotion is reported ready, and before it merges. It compares closingIssuesReferences with the intended set and greps the promoted range's commit messages for closing keywords.

GOVERNANCE.md "Branching Model" gains a short summary. drive-pr step 5 points to the check, and merge-and-release step 2 runs it before the merge. The generated skill trees are regenerated by scripts/build_dist.py.

Local Review Findings Left Standing

• introduced, fixed in the second push: merge-and-release step 2's closing-set check read a local git log, which for a downstream target is the hub checkout's range. It now reads the target's range through gh api --paginate .../compare/main...<sha>, run on its own so a failed read stops the merge rather than reading as a clean range.
• introduced, fixed in the second push: the same check read as applying only to the no-ready-report case. It is now its own unconditional sentence.
• pre-existing/declined: a reviewer may read STANDUP.md "Hand Over" as breaking the exhaustive list, since "over" is on it. It is a phrasal-verb particle rather than a bind word, so it stays capitalized by the coordinator's ruling. A particle exception would be a new rule neither issue asks for.

Closes on promotion: #1154, #1471

🤖 Generated with Claude Code