What problem does it solve?
Keeping a shared Team server current without breaking session continuity, schema compatibility, or recovery guarantees is risky when deployments are improvised. This Skill enforces a single canonical deployment owner, hourly cadence, and strict pre-migration verification so routine updates and supported upstream migrations proceed safely.
Core Features & Use Cases
- Owner-driven deployment: Routes every update through the configured updater service and its hourly timer, never duplicating schedulers or substituting direct restarts.
- Schema-safe migration gates: Requires database inventory, WAL-aware backups, session-preservation witness, writer fencing, and per-database integrity checks before mutation.
- Receipt-based verification: Validates deployment receipt, serving SHA, process generation, RPC, health, channels, and policy/identity preservation before declaring success.
- Use Case: An operator needs to roll out a new OpenClaw release to a shared Team deployment overnight. Use this Skill to trigger the canonical updater, confirm the migration Doctor flow, and verify session continuity before users reconnect in the morning.
Quick Start
Use the update-team-server skill to deploy the latest upstream release through the configured owner and verify session continuity.