v0.161.1: Release job: name the repo explicitly — no checkout means no git context
First live run of the release job failed with fatal: not a git repository. The job deliberately runs without a checkout (it needs no code), and gh release create infers the repository from the local git context — which doesn't exist there. The gh api calls in the same script were immune because they name the repo in their request paths. One flag: -R "$REPO".
v0.161.0 was backfilled by hand for #568's merge commit with the same title and notes the job would have produced, so the version sequence stays truthful.
This PR's merge is the live retry: on landing, the job must auto-cut v0.161.1 (fix/ → patch from v0.161.0). If that release appears without manual help, the automation is verified end-to-end.
Full Changelog: v0.161.0...v0.161.1