Owner: Engineering\ Last reviewed: 2026-07-21

Every operational runbook should include:

1. purpose and scope
2. owner and escalation path
3. prerequisites and required access
4. exact procedure
5. verification and expected result
6. rollback or recovery procedure
7. last-tested date

1. Deploy API and required migrations before a mobile-web release that depends on them.
2. Treat the native wrapper version, web release version, and API compatibility version as separate values.
3. Verify the exact release-registry channel and wrapper-version tuple used by the store binary.
4. Never place service-role keys, access tokens, database URLs, or JWTs in a runbook.

Link detailed procedures to their source-controlled scripts and canonical documentation so commands do not drift silently.