runners/arc: bake CI-capability into register-repo.sh provisioning

[izzywdev]

Auto-opened from branch claude/issue-251-20260713-1918.

Closes #251

[izzywdev]

@claude can this be progressed to merge? or is it obsolete compared to main?

[claude]

Claude finished @izzywdev's task in 1m 36s —— View job

---

Verdict: obsolete — recommend closing (do not merge)

• Compare PR changes against current main
• Check whether register-repo.sh CI-capability changes already landed
• Determine: mergeable, needs rebase, or obsolete
• Report recommendation

This PR cannot be cleanly merged and its substance is already in main.

Why it's obsolete

main's history was rewritten/squashed since this branch was cut (2026-07-13) — the two share no merge base (git merge-base origin/main HEAD → none), so GitHub can't do a normal merge anyway. More importantly, the actual content already landed:

PR file	branch vs origin/main
runners/arc/register-repo.sh	identical — CI-capable provisioning already in main (see lines 60–63, 76, 189–191: fuzeinfra.io/pool: ci, CI-capable default image, etc.)
runners/arc/ONBOARD-REPO.md	identical
runners/arc/Dockerfile	branch is behind main

The one remaining diff is a regression risk: main's Dockerfile already installs the GitHub CLI (gh) from the official apt repo. This branch predates that, so merging it would delete the gh install block:

-# --- GitHub CLI (gh) ---------------------------------------------------------
-RUN set -eux; \
-    curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg ...
-    apt-get install -y --no-install-recommends gh; \
-    gh --version

Recommendation

• Close this PR without merging. The change it set out to make ("bake CI-capability into register-repo.sh provisioning", Bake CI-capability into runners/arc/register-repo.sh (containerMode: dind + CI runner image) — provisioning-level fix #251) is already present in main, so Bake CI-capability into runners/arc/register-repo.sh (containerMode: dind + CI runner image) — provisioning-level fix #251 is effectively resolved — verify and close it too.
• No rebase is worth doing: there's nothing left to contribute (register-repo.sh / ONBOARD-REPO.md match main exactly), and the only delta would undo the gh CLI addition.

I can't merge or close PRs myself (Claude can't perform those git/GitHub operations), so this needs a human to close #253 and confirm #251.
· branch claude/issue-251-20260713-1918

[izzywdev]

⚠️ Claude responder did not run to completion

The responder errored before finishing your request, so no changes were made and no branch was created.

• Reason: Claude run returned is_error (num_turns=10) — it errored before completing the task
• Run log: https://github.com/izzywdev/FuzeInfra/actions/runs/30025898650

This notice is automated and will not retry on its own — the responder stops after one failure and waits. If this looks like an API-side problem (key revoked / out of credits / model or 1M-context beta not entitled / Anthropic outage), an operator should check the ANTHROPIC_API_KEY secret and fund/repair the Anthropic account first, then re-trigger by posting a new comment mentioning the responder.