update-team-server

Update the operator-configured Team server through its canonical deployment owner.

388k|81.5k|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/steipete/clawdis --skill update-team-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-team-server
Source: https://github.com/steipete/clawdis/tree/main/.agents/skills/update-team-server
Command: npx skills add https://github.com/steipete/clawdis --skill update-team-server

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about update-team-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a shared Team server without breaking active sessions?

Route the update through the configured canonical deployment owner and its hourly timer. Require the pre-cutover session-preservation witness and per-database integrity checks before stopping writers, then verify the deployment receipt and serving SHA after restart.

What is the canonical deployment owner for Team server updates?

The canonical owner is the operator-configured updater service documented in the private deployment runbook. It alone controls deployment, Gateway lifecycle, rollback, and recovery; direct restarts or in-place source builds are not substitutes.

Does the Team server update require a separate scheduler?

No. The existing hourly timer must remain the sole cadence. Creating another scheduler or pausing the timer for proof windows is explicitly disallowed by this workflow.

Why does the update-team-server skill refuse to clear failed deployment status?

Clearing failed status would manufacture idleness and hide unresolved journals. The skill preserves failed outcomes and routes recovery through the canonical forward-recovery owner until every store is verified ready.

When should I not use the update-team-server skill?

Do not use it when the canonical owner is missing access or a safe capability, when source or PR repairs are pending in the same worktree, or when the operator has not authorized routine deployments and supported upstream migrations.