docs: document Conventional Commit PR-title requirement for release-please

[chrischall]

Fleet-wide release-please alignment. Squash-merge + release-please means the PR title is the only thing release-please parses; CLAUDE.md had no PR-title guidance. Docs-only.

🤖 Generated with Claude Code

[claude]

Claude finished @chrischall's task in 46s —— View job

---

PR Review: docs: document Conventional Commit PR-title requirement for release-please

• Gather context
• Review documentation accuracy
• Verify against project configuration

Reviewing the added documentation section:

The PR adds a "Pull requests & releases" section documenting:

1. Squash-merge + PR title as release source ✓ Accurate
2. Conventional Commit requirement ✓ Accurate
3. Type → action mapping (feat=minor, fix=patch, !=major) ✓ Accurate per release-please-config.json
4. Changelog sections (perf/refactor/docs visible, ci/test/build/chore hidden) ✓ Matches lines 19-30 of release-please-config.json exactly
5. Auto-merge workflow ✓ Matches pr-auto-review.yml + auto-merge.yml behavior

Verification against actual project state:

• ✓ Squash-merge is the only allowed strategy (per the statement "squash-merges")
• ✓ Recent commits follow the format (e.g., chore(deps-dev): bump esbuild…)
• ✓ release-please-config.json confirms changelog-sections and hidden flag mappings
• ✓ pr-auto-review.yml runs on PR events and adds ready-to-merge label on pass
• ✓ auto-merge.yml uses gh pr merge --auto --squash (confirmed via reusable workflow stub)
• ✓ Documentation accurately reflects the "don't run gh pr merge yourself" constraint

Quality observations:

• Clear, well-structured explanation of the workflow
• Properly formatted with Conventional Commit examples
• Explains both what to do (branch + PR, conventional title) and what not to do (manual gh pr merge)
• Practical guidance on which commit types trigger releases vs changelog-only

No issues found. The documentation is accurate, complete, and well-integrated into CLAUDE.md.

Verdict: pass

---

[github-actions]

✅ Auto-review verdict: pass — Documentation accurately reflects the project's Conventional Commit PR-title requirement and auto-merge workflow. All claims verified against release-please-config.json, workflow files, and existing commit history.