ci(build-deploy-game): accept optional deploy_host input

PLAYED_HOST falls back to inputs.deploy_host when set, else the secret —
lets played/infra deploy-all target a freshly-provisioned box. Game
callers forward the input.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.gitea/workflows/build-deploy-game.yml

@@ -46,6 +46,11 @@ on:
         description: Game slug (must match @played/games-registry's GAMES, e.g. relayer)
         type: string
         required: true
+      deploy_host:
+        description: Box IP to deploy to (passed by deploy-all). Blank = the PLAYED_HOST secret.
+        type: string
+        required: false
+        default: ""
 
 jobs:
   build-api-core:
@@ -122,7 +127,7 @@ jobs:
     runs-on: ubuntu-24.04
     needs: build-api-core
     env:
-      PLAYED_HOST: ${{ secrets.PLAYED_HOST }}
+      PLAYED_HOST: ${{ inputs.deploy_host || secrets.PLAYED_HOST }}
       PLAYED_USER: ${{ secrets.PLAYED_USER }}
       PLAYED_PORT: ${{ secrets.PLAYED_PORT }}
       GAME_ID: ${{ inputs.game-id }}
@@ -286,7 +291,7 @@ jobs:
     # Both gates: image must be built AND api-core must be live before web flips.
     needs: [build-web, deploy-api-core]
     env:
-      PLAYED_HOST: ${{ secrets.PLAYED_HOST }}
+      PLAYED_HOST: ${{ inputs.deploy_host || secrets.PLAYED_HOST }}
       PLAYED_USER: ${{ secrets.PLAYED_USER }}
       PLAYED_PORT: ${{ secrets.PLAYED_PORT }}
       GAME_ID: ${{ inputs.game-id }}