docs(release): update release process to reflect workflow_dispatch deploy trigger

- Replace outdated 'release: published' trigger description with the
  actual mechanism (release.yml calls gh workflow run after creating
  the GitHub Release)
- Add explanation of why workflow_dispatch is used instead of
  release: published (GITHUB_TOKEN cascade limitation)
- Note that deploy workflows can be triggered manually from the Actions
  tab for hotfix deployments

https://claude.ai/code/session_01JDVdCKNUcJfnKCaZZipMWW

Author: claude

docs/processes/release.md

@@ -41,9 +41,8 @@ Merging the release PR triggers `release.yml`, which:
 
 1. Reads the version from `pubspec.yaml` (source of truth)
 2. Creates and pushes the git tag (e.g. `v2026.5.5`)
-3. Creates a GitHub Release from that tag with the `CHANGELOG.md` body
-
-Creating the GitHub Release triggers the deployment workflows (via `on: release: published`):
+3. Creates a GitHub Release with the changelog for that version
+4. Explicitly triggers the deployment workflows via `workflow_dispatch`
 
 | Workflow | Action |
 |----------|--------|
@@ -52,6 +51,8 @@ Creating the GitHub Release triggers the deployment workflows (via `on: release:
 
 Monitor progress in the [Actions tab](https://github.com/richardthe3rd/cambridge-beer-festival-app/actions).
 
+> **Why `workflow_dispatch` and not `release: published`?** GitHub does not fire workflow triggers in response to events created by `GITHUB_TOKEN`. Using `gh workflow run` sidesteps this limitation without requiring a PAT.
+
 ## What goes into a release
 
 git-cliff reads conventional commit messages since the last tag. The following types are included:
@@ -80,6 +81,8 @@ git push origin hotfix/fix-description
 
 After merging to `main`, the release PR will pick up the fix in the next run and compute the next patch version automatically.
 
+To deploy a hotfix without waiting for the release PR flow, you can trigger the deployment workflows manually from the [Actions tab](https://github.com/richardthe3rd/cambridge-beer-festival-app/actions) — select `Release Web to Cloudflare Pages` or `Release Android` and provide the version tag.
+
 ## Promote Android release (manual)
 
 Once the Internal track build is available: