diff --git a/CLAUDE.md b/CLAUDE.md
index 0912ac8..cb9ba62 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -45,7 +45,7 @@ A **shot** holds the metadata (name, location, INT/EXT, light phases + artificia
 - **The Android signing key** lives in the deployment repository's GitHub secrets and the owner's offline backup, never in git or a checkout; a new key cannot update installed apps. Builds use no Expo account (`expo prebuild` + Gradle). Locally only keyless builds: the dev client (`make dev-build`) and OpenClapper Local (`make apk-local`, debug-signed).
 - **One product version** (root `package.json`, SemVer 0.x; workspace packages stay `0.0.0`). Releases: `scripts/release.sh X.Y.Z`, only when the owner asks ([releasing](docs/releasing.md)).
 - **CI is a gate**: never pass `--admin` to `gh pr merge`; a red check is fixed, not bypassed.
-- **Deploys to production are done by the owner**, from the deployment repository `OpenClapper-dev/deploy` (its "Production · …" and "Staging · …" workflows: Release, Deploy server, Build phone app, Reset from production; its GitHub environments `production` and `staging` hold each instance's settings, see `docs/self-hosting.md`). This repository is for development and is a black box to that one: scripts and reusable workflows read every setting from the environment, never from a settings file or a path outside the checkout, and the Makefile's targets are local-only (no deploy targets, nothing a deployment calls). The tracked `wrangler.jsonc` files are local-dev only: never put an account, database or Access id back into them. You prepare, check and commit. You may apply additive remote migrations when asked. Commit only when asked or when working through an agreed plan; work on a branch.
+- **Deploys to production are done by the owner**, from the deployment repository `OpenClapper-dev/deploy` (its "Production · …" and "Staging · …" workflows: Release (production), Update (staging: server and app from one commit), Deploy server, Build phone app, Recreate from production (staging); its GitHub environments `production` and `staging` hold each instance's settings, see `docs/self-hosting.md`). This repository is for development and is a black box to that one: scripts and reusable workflows read every setting from the environment, never from a settings file or a path outside the checkout, and the Makefile's targets are local-only (no deploy targets, nothing a deployment calls). The tracked `wrangler.jsonc` files are local-dev only: never put an account, database or Access id back into them. You prepare, check and commit. You may apply additive remote migrations when asked. Commit only when asked or when working through an agreed plan; work on a branch.
 
 ## Working from a GitHub issue