chore: bump to v0.1.37

[alexkroman]

What & why

Version bump to 0.1.37 (CFBundleShortVersionString 0.1.36 → 0.1.37,
CFBundleVersion 36 → 37, xcodeproj regenerated). Generated by the
release-bump workflow — run 31567112534.

Merging this starts the release. That is the change #126 just landed: the
push to main carries a changed CFBundleShortVersionString, release.yml's
resolve job confirms the version actually changed and isn't already tagged,
and the build job signs, notarizes, staples, and builds the DMG. Publishing
then parks on the release-publish approval gate until someone downloads that
DMG, installs it, and approves. Nothing is rebuilt after approval, so what gets
tested is byte-for-byte what ships.

0.1.36 was bumped on main but never released, and predates the automatic
trigger, so it is skipped rather than shipped. No v0.1.36 tag exists, so
nothing is orphaned by that.

This is also the first release started without a workflow dispatch: the bump ran
from a pushed marker branch (release/v0.1.37 at main's tip, carrying no
commits of its own), which the workflow verified was an ancestor of main
before bumping on top of main and force-pushing the result here.

How it was tested

• scripts/check.sh passes (or CI will, if I'm not on a Mac) — Linux
  sandbox, so CI on macos-26 is the authority; the release build runs the
  full suite again before signing
• I read AGENTS.md and this doesn't reintroduce anything
  deliberately removed
• Docs updated if behavior changed — n/a, generated bump only

https://claude.ai/code/session_01F952B3qz1QeXYv5sPGwPh3

---

Generated by Claude Code

[github-actions]

Dev build

Download Blurt.app — built from dde210c, Debug-Local,
ad-hoc signed. Expires in 14 days.

Installing it

cd ~/Downloads
unzip -o blurt-dev-build-pr-127.zip   # GitHub wraps every artifact in a zip
unzip -o Blurt-dev-dde210c.zip
find Blurt.app -exec xattr -c {} +   # clear quarantine: xattr lost -r in macOS 12.3
rm -rf /Applications/Blurt.app && cp -R Blurt.app /Applications/
open -a Blurt

It is ad-hoc signed and not notarized: Gatekeeper refuses to open it until
the quarantine flag is cleared, and macOS treats it as a different app from a
released Blurt, so you have to re-grant Microphone, Accessibility, and Input
Monitoring. Reinstall the release DMG
when you are done reviewing.

Expect that re-grant once per dev build, including a second build of this
same PR. TCC pins an Accessibility grant to the signature that took it, and an
ad-hoc signature is just a hash of the binary, so every build is a new app as far
as tccd is concerned. Blurt clears the orphaned grant at launch, which is what
keeps the Accessibility step from getting stuck on a Blurt row that is switched on
and still denied. If you are coming from a build old enough to predate that,
clear the grant yourself once:

tccutil reset Accessibility dev.alex.blurt