[dmccoystephenson]

Summary

• The arcade release that the Test workflow deploys to is bumped from v0.5.0 to v0.6.3 (the latest arcade release), as the comment on the ref: asks for each arcade release.
• git log v0.5.0..v0.6.3 in arcade shows a landing page, /version.json, /robots.txt, /og.png, a canonical Link header and a cleaner missing-registry error. The upload endpoint, its status codes and ?activate=false, plus the hash-token/serve commands used by CI, are unchanged in src/arcade/server.py and src/arcade/__main__.py, so no change to deploy.sh or action.yml is expected.

Closes #6

Test plan

• Test / deploy-to-a-real-arcade is green on this head, with every existing step running against arcade v0.6.3: first deploy + "The game is live", re-run failure, skip-existing, wrong/empty token, empty slug, bad inputs, other non-2xx, activate: false, and the static-site deploy.
• test.yml and action.yml parse as YAML locally.

Compatibility

Backward-compatible for callers pinned to @v1: only CI changes and the action is untouched. Because the PR touches .github/workflows/*, it is held for human review rather than auto-merged.

This PR description was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).

---

drafted by Claude on behalf of Daniel Stephenson

🤖 Generated with Claude Code

[dmccoystephenson]

Self-review rubric (run after CI went green on the PR head):

• Scope: PASS — git diff --stat origin/main shows one line changed in .github/workflows/test.yml (ref: v0.5.0 → ref: v0.6.3); nothing else is touched.
• Tests-new: PASS (n/a) — no new input, output, fail branch or status arm is added; all 15 existing scenario steps were re-run against the new server.
• Tests-fix: n/a — this is a CI pin bump, not a bug fix.
• Sibling structure / sibling renames: n/a — no new files and no renames.
• Docs: PASS — the README "Tests" paragraph says "a pinned release" without naming one, and the ref: comment ("Bump it with each arcade release") still holds; no other source of truth mentions the arcade version.
• Issue resolution: PASS — CI: pinned arcade v0.5.0 lags the latest release v0.6.3 #6 asks for exactly this pin change.
• CI: PASS — run 39013130016 is green; the log shows the arcade checkout fetching refs/tags/v0.6.3, and every deploy/assertion step ran with conclusion success (none skipped).
• Input parity / Output parity: PASS (unchanged) — action.yml, deploy.sh and the README are not modified.
• Token hygiene / Failure messages / Pre-network validation / Compatibility: PASS (unchanged) — deploy.sh and action.yml are untouched, so @v1 callers are unaffected.

Out-of-diff observations:

• .github/workflows/test.yml:24 — the upload API in arcade v0.6.3 (src/arcade/server.py) is unchanged from v0.5.0. The new /version.json on the API host could later be used to assert which arcade CI is running, but that is left out of this pin-only change.
• CI runs only on ubuntu-latest over http://, so the https:// production default url is still not exercised. That gap existed before this PR.

Merge gate: .github/workflows/* is on the do-not-auto-merge list, so the PR is held for human review and merge.

This review was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).

---

drafted by Claude on behalf of Daniel Stephenson