fix(release): give publish-release a repo context for gh

The job has no checkout by design — it only talks to the API — but 'gh
release view/edit' resolves the repository from a git remote, unlike 'gh
api <path>'. Without one every call failed with 'not a git repository',
and the existence check (which suppresses gh's stderr) reported it as
'no release v0.0.18 exists'. The draft was sitting there with all four
correct assets.

This job was added in plan 024 and v0.0.18 was its first real run;
ci-gate and dispatch-apt-charliek also skip checkout but call 'gh api'
with explicit repo paths, so they were never affected.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: charliek

.github/workflows/release.yml

@@ -844,6 +844,12 @@ jobs:
       - name: Assert the artifact set, then publish
         env:
           GH_TOKEN: ${{ github.token }}
+          # This job deliberately has no checkout — it only talks to the API.
+          # But `gh release …` (unlike `gh api <path>`) resolves the repo from
+          # a git remote, so without this every call fails with "not a git
+          # repository" and the existence check below reports it as "no
+          # release exists". v0.0.18 died here on this job's first real run.
+          GH_REPO: ${{ github.repository }}
         run: |
           set -euo pipefail
           tag="${GITHUB_REF_NAME}"