codeSplitters: one real hosted deploy of a Railway or Hetzner box target #345

Follow-up from #248. Hosted deploys can now store Railway and Hetzner keys and pass them into the deploy container as RAILWAY_API_TOKEN / HCLOUD_TOKEN. The tests cover the env, the sealing and the log scrubbing, but no real box has been deployed from the site. That needs your accounts and costs a little (a Railway service, or a Hetzner cpx12 plus volume), so it waits for you.

Steps

• After MANUAL RUN: codeSplitters: one real hosted deploy from the site, with a scoped token #309's Cloudflare run works: make a throwaway repo with targets.box: { provider: "railway" } (or hetzner), no native crates.
• Store a Railway team token (or a Hetzner project token) in its Deploy panel and press Deploy. Expect a *.up.railway.app (or http://<ip>:3000) URL and the check to pass, and the token never in the log.
• Deploy again: the same service or server, not a second one (Alchemy state, including the SSH key Alchemy makes for Hetzner, is carried between runs).
• Note the run time: rustybuns build box runs inside the 13-minute budget on the basic container.
• Destroy the box, delete the token and the stored key.

Known limit: a box whose native/ crates need the Docker cross-build can't build in the deploy container (no Docker); that one deploys from the desktop.

🤖 Generated with Claude Code