fix(ci): allow the scope release-please uses in its own PR title

release-please opens 'chore(main): release X.Y.Z'. The PR title check has
an allowlist of scopes and 'main' was not on it, so that title failed. With
conventional-commit now a required status check in the branch ruleset, the
release PR would have been permanently unmergeable — a trap that only
appears once enforcement is on.

Adds 'main' with a comment saying why it is there, since it is a branch
name rather than a component and looks out of place next to sync/auth/logs.
Adds 'types' too, which was missed when that command landed.

Removes docs/main-ruleset.json; the rule is configured and the checklist
lists the settings inline.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: mschmicking

.github/workflows/pr-title.yml

@@ -31,16 +31,24 @@ jobs:
             ci
             chore
             revert
-          # Optional, but keep the vocabulary small so it stays meaningful.
+          # Optional, but keep the vocabulary small so it stays meaningful. A scope is
+          # not required, but any scope used must appear here.
+          #
+          # 'main' is not a component — it is the branch name release-please puts in its
+          # own PR title ("chore(main): release 1.0.0"). Without it that title fails this
+          # check, and once the check is required by the branch ruleset the release PR
+          # becomes unmergeable.
           scopes: |
             sync
             auth
             watch
             logs
             json
+            types
             cli
             deps
             docs
+            main
           requireScope: false
           # Only the trailing full stop is rejected. A lower-case rule was tried and
           # removed: Dependabot capitalises some of its titles ("Bump x from 1 to 2")

docs/GOING-PUBLIC.md

@@ -16,7 +16,7 @@ These change how merges behave, and the release automation depends on them.
 > "Your rulesets won't be enforced on this private repository until you move to a GitHub
 > Team organization account". Reading it back over the API also 403s on the free plan.
 > So configure it whenever you like — it starts working the moment the repo is public.
-> `docs/main-ruleset.json` is a ready-to-import copy.
+> The settings are listed in step 5.
 
 - [ ] **Settings → General → Pull Requests**
   - [ ] Enable **Allow squash merging**
@@ -125,8 +125,6 @@ Things that only start working once the repository is public:
 - [ ] **Branch protection** — now available, since the repository is public.
       **Settings → Rules → Rulesets → New branch ruleset**:
 
-  Import `docs/main-ruleset.json`, or set it by hand:
-
   - Name: `main` (only a label; it appears in the "blocked by" message on a rejected push)
   - Enforcement status: **Active**
   - Target branches: **Include default branch**