Build once, deploy to DoIT and Vault R2 test builds

[mrdavidgagnon]

Moves this repo's CI to the pattern already running on Aqualab (fielddaylab/wake#47, fielddaylab/wake#48): one Unity build, deployed independently to DoIT (as today) and to Vault's R2 test-build storage.

build   (VaultLearningGames/vault-publisher unity-build.yml@v1)
  ├─► doit     VPN + rsync → https://fielddaylab.wisc.edu/play/bloom/ci/<branch>/   (unchanged; delete this job when DoIT is retired)
  └─► preview  → https://builds.vaultlearninggames.org/fieldday/bloom/<branch>/
remove-preview (on branch delete)

What changes: only the workflow file. The build itself moves to the shared reusable workflow (same game-ci builder, Unity version read from ProjectSettings/ProjectVersion.txt); the DoIT upload becomes its own job using the same secrets and folder as before; a new job publishes the same build to the Vault CDN as game bloom of studio fieldday. Nothing in the game changes.

Bloom specifics: DEPLOY_DIR stays a repository variable (vars.DEPLOY_DIR), as in the old workflow. production gets its own PR with the same change, because develop is 60 commits ahead of it.

What merging triggers: a push to develop, so one Unity build (uses a Unity seat; the first build on a branch has no Library cache, so it is slower than usual), then

• DoIT: redeploys https://fielddaylab.wisc.edu/play/bloom/ci/develop/ (same code, new build)
• Vault: publishes https://builds.vaultlearninggames.org/fieldday/bloom/develop/

From then on every branch push does both, and deleting a branch removes its Vault build.

How to verify:

• This PR's own test build (branch vault-r2-publish, check below): https://builds.vaultlearninggames.org/fieldday/bloom/vault-r2-publish/ and https://fielddaylab.wisc.edu/play/bloom/ci/vault-r2-publish/
• After merging: the run on develop in Actions shows build, doit and preview / publish green, and https://builds.vaultlearninggames.org/fieldday/bloom/develop/ loads the game.

Merge with a merge commit or squash, one repo at a time (Unity seats). The first run creates a vault-staging deployment environment in this repo, which is where the published URL shows up.

🤖 Generated with Claude Code