v0.9.1

CI: bound every release job to 60 minutes

A macos-13 (Intel) run was observed queued for a full 24h with no runner
ever assigned (steps: [] in the job API — GitHub had no capacity, not a
build failure) before being auto-cancelled, and a separate run needed a
manual cancel at 38 minutes for the same reason. fail-fast: false already
means one stuck platform doesn't block the others from building and
publishing, so this only bounds the wasted time and makes a repeat fail
loudly instead of silently eating a day.