release v1.1.0 (sentinel re-fire)

[BoldBlackBot]

Summary

• Re-fires the release sentinel for v1.1.0: PR release v1.1.0 #38 was merge-committed, so the head commit message did not start with release v and tag-on-merge.yml skipped — no tag or GitHub release was created.
• Content: one implementation note in the rename RFC documenting the miss and the squash-merge requirement for release PRs.
• Version 1.1.0 + changelog are already on main (from feat: rename bclaw to dispatch (package, repo identity, template, v1.1.0) #37/release v1.1.0 #38); npm 1.1.0 is already published (manual first publish).

⚠️ Merge style: SQUASH

The sentinel checks startsWith(head_commit.message, 'release v'). A merge commit breaks that; a squash produces release v1.1.0 (sentinel re-fire) (#<n>) and fires it.

What the workflow will do on merge

1. Tag v1.1.0 (doesn't exist yet — it will be created)
2. Extract the changelog entry → GitHub release v1.1.0
3. npm publish step: detects 1.1.0 already on npm → "Version 1.1.0 already published, skipping" → green run, OIDC chain exercised

Verification

• RFC checklist fully ticked; note appended under Implementation Notes.
• No code changes — build/tests unaffected (CI still runs and must pass).

Test plan

• After squash-merge: gh run list shows Tag and Release not skipped; tag v1.1.0 + release appear; the site's version pill (live-fetches latest release) flips to v1.1.0.