fix(ci): pass repository to release lifecycle commands

[BrianInAz]

Summary

• pass the explicit repository to every issue lifecycle command that can run without a checkout
• cover view, comment, and close repository context in the release contract test

Reproduction

Adding built to monitor-created issue #3 launched run 30727885122. The job failed before validating the marker because gh issue view reported fatal: not a git repository; the job has no checkout from which gh can infer a repository.

Solution

Use --repo "$GITHUB_REPOSITORY" for issue reads, comments, and closes in the skip, built, accepted, approval, and local handoff jobs. This keeps these jobs checkout-free and least-privilege while making repository selection deterministic.

Validation

• scripts/test-private-ca-release-contract.sh
• shellcheck scripts/test-private-ca-release-contract.sh scripts/normalize-private-ca-desktop-tag.sh
• Ruby YAML syntax parse
• git diff --check

After merge, removing/re-adding the existing built label on issue #3 will retry only the already-accepted v0.5.2 lifecycle record; it will not build or install v0.5.3.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[BrianInAz]

CI disposition: the PR-scoped private-CA release contract and dead-token guard passed. The macOS lane reproduced the already documented base workflow failure before product compilation (mesh-llm checkout for 43103c5 not found after cargo fetch). This two-file fix only supplies explicit repository context to checkout-free gh issue commands and adds a contract assertion; it does not touch desktop or Cargo code.