From 860abdfcc8ff51495a7c8645af75c25587aa811b Mon Sep 17 00:00:00 2001
From: BoldBlackBot <296328274+BoldBlackBot@users.noreply.github.com>
Date: Sat, 15 Aug 2026 20:20:19 -0400
Subject: [PATCH] release v1.1.0 (sentinel re-fire)

Re-fires the release sentinel: the previous release PR (#38) was
merge-committed, so the head commit message did not start with
'release v' and tag-on-merge.yml skipped. Version 1.1.0 and the
changelog are already on main; npm 1.1.0 is already published
(manual first publish), so the workflow's publish step will detect
and skip. Expected result: v1.1.0 tag + GitHub release.

Co-Authored-By: Enrique Canals <84596+EnriqueCanals@users.noreply.github.com>
---
 rfcs/2026-08-15_rename-to-dispatch.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/rfcs/2026-08-15_rename-to-dispatch.md b/rfcs/2026-08-15_rename-to-dispatch.md
index 31aa1e2..bab377e 100644
--- a/rfcs/2026-08-15_rename-to-dispatch.md
+++ b/rfcs/2026-08-15_rename-to-dispatch.md
@@ -58,3 +58,12 @@ The golden test is updated first (TDD): it now generates with `name=dispatch` ex
 - [x] (post-merge) GitHub repo renamed to `boldblackai/create-dispatch` (2026-08-15)
 - [x] (post-merge) manual first publish of `@boldblackai/create-dispatch@1.1.0` (2026-08-15); `@boldblackai/create-bclaw` deprecated with a pointer to the new name
 - [x] (post-merge) homepage DNS cutover to `dispatch.boldblack.ai` (live 2026-08-15)
+
+## Implementation Notes
+
+- The first release attempt (PR #38) was merged with a regular merge whose
+  commit message did not carry the `release v` prefix (the PR title was
+  truncated in the merge commit), so the `tag-on-merge.yml` sentinel never
+  fired and no `v1.1.0` tag was created. This release PR re-fires it;
+  release PRs must be **squash-merged** so the head commit message starts
+  with `release v`.