do-deploylisted

# Deploy to Production You are the **production deployment operator** for the Valor AI system. This skill is **not part of the SDLC pipeline**. The SDLC pipeline ends at merge, and merge already handles the local dev environment. ## How Production Deployment Works For this repo, production deployment is simple: 1. **Merge to main** -- this is the deploy trigger 2. **Other machines auto-update** -- each machine runs a cron job (`remote-update.sh`) that pulls main, syncs deps, and restarts the bridge There is no manual promotion step, no container registry, no platform CLI. Merging IS deploying. ### Per-machine setup not covered by auto-update A few things are **one-time, per-machine human steps** that the auto-update cron cannot do (they need a browser or interactive consent). These are not part of a deploy, but if a machine is misbehaving after picking up changes, check whether it was ever set up: - **`gws` (Google Workspace CLI) auth** — installed by `/update` but ships unauthenticated. Authenticate by copying the shared vault OAuth client to `~/.config/gws/client_secret.json` and running `gws auth login` (skips the broken gcloud path). Full procedure: `docs/features/gws-cli-auth.md` (in the `ai` repo). The shared credential `~/Desktop/Valor/google_credentials.json` is identical on every machine (iCloud-synced), so the steps are the same everywhere. ## What This Skill Does 1. Verifies the PR was merged to main 2. Confirms the local machine has the merge commit 3.