docs(bugbot) - lint conventional commits

.cursor/BUGBOT.md

@@ -127,6 +127,33 @@ describe('useCostCalculator', () => {
 });
 ```
 
+## PR Title Convention (Required)
+
+Always check the pull request title. Releases and semver bumps are driven by conventional commits, so PR titles must use that format.
+
+**Required format:** `type(scope): description`
+
+**Allowed types:** `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`, `ci`, `build`, `revert`
+
+**Rules:**
+
+```text
+If the PR title does NOT match /^(feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert)(\([^)]+\))?!?\s*[:-]\s+.+/i, then:
+- Add a blocking Bug titled "PR title must follow conventional commits"
+- Body must include:
+  - The current (invalid) PR title
+  - That titles must use `type(scope): description`
+  - That this drives semver (`feat` → minor, `fix` → patch, `BREAKING CHANGE` → major)
+  - A rewritten good title based on the PR changes
+  - Examples:
+    - BAD: `canInvite is now depending of onboarding-reserve-status pending request`
+    - GOOD: `fix(onboarding-reserves) - fix race condition on the invite button, now depending on onboarding-reserve-status`
+    - GOOD: `feat(gp): add PayrollAdminOnboarding flow mutations and schemas`
+- Assign the Bug to the PR author
+```
+
+Do not skip this check even if the code looks correct. Flag the title on every review until it complies.
+
 ## Specific Areas of Focus
 
 When reviewing code, pay special attention to:
@@ -491,6 +518,7 @@ listItems: [
 
 Before approving a PR, verify:
 
+- [ ] **PR title follows conventional commits** - e.g. `fix(scope) - description` or `feat(scope): description`
 - [ ] **No breaking changes** - Or properly documented with `BREAKING CHANGE:`
 - [ ] **New tests added** - All new features/fixes have tests
 - [ ] **JSDoc added** - Public APIs have documentation