MANUAL RUN: codeSplitters: one real hosted deploy from the site, with a scoped token #309

The last two checks from #247. They need you: a signed-in admin session on the site, and a scoped Cloudflare token only you can create.

Hosted deploys are now live on https://codesplitters.notryanquinn.workers.dev. The DeployRunner container app, DEPLOY_SECRETS_KEY and the deploy_keys migration are deployed. The whole run (clone, bun install, rustybuns deploy, check, with the Alchemy state carried between runs) was replayed in the real deploy-sandbox image on a Mac against a throwaway Worker, but never from the site itself.

Steps

• In the Cloudflare dashboard, create an API token scoped to Workers Scripts: Edit on the notryanquinn account, and nothing else.
• Sign in to the site as quinn and make a small throwaway Rusty Buns repo. It needs a rustybuns.config.ts with an edge target, adopt off, bindings: {} (or any) and @rustybuns/cli plus the pinned alchemy set (rustybuns add deploy). Commit it so it has a git remote.
• In its Deploy panel, store the token and account ID, then press Deploy. Expect the four steps to go green and a *.workers.dev URL. Check the log shows <deploy key> and never the token.
• Press Deploy again. It should update the same Worker (same URL), not create a second one.
• Note how long the run took. On the Mac, under amd64 emulation, bun install took 100–330 s and the deploy 8–22 s. A run gets 13 minutes (RUN_BUDGET_MS, inside the alarm's 15).
• Remove the throwaway Worker afterwards, delete the token, and delete the repo's stored key.

From #247.

🤖 Generated with Claude Code