OpenClaw Update Rollback Manager v1.0

Price: $4.99

Category: automation

What it does

OpenClaw Update Rollback Manager helps operators review release notes or incident notes before touching a production OpenClaw install. It turns messy upgrade risk signals into a clear PASS, REVIEW, or BLOCKED report with snapshot, dry-run, rollback, and post-upgrade health-check guidance.

The skill is local and read-only: it does not run upgrade commands, edit config, restart services, call the network, or mutate files.

Use cases

• OpenClaw operators planning upgrades who need a repeatable safety checklist before changing gateway, plugin, or channel components.
• Consultants managing client installs who want evidence-backed rollback notes and health checks before a maintenance window.
• Teams recovering from regressions who need to classify gateway, bridge, cron, dependency-loop, and point-release risks before the next attempt.

Requirements

• OpenClaw v2026.3.23 or later recommended.
• Python 3 with standard library only; no pip dependencies.
• No API keys, model calls, network access, git access, service access, or package-manager access required.
• Input: a local release-notes or incident-notes text/Markdown file.

Example usage

python3 scripts/update_rollback_manager.py --notes release-notes.md --json

Expected output excerpt:

{
  "ok": true,
  "status": "REVIEW",
  "risk_score": 40,
  "findings": [
    {"rule": "point_release_risk", "severity": "medium", "evidence": "breaking change"}
  ],
  "snapshot_plan": ["Record current OpenClaw version", "Backup workspace memory and skills"],
  "rollback_notes": ["Keep prior package/version reference"],
  "mutated_files": []
}

Release evidence

• Viper: APPROVED_FOR_RELEASE in memory/viper-test-results-2026-06-09.md.
• Warlock: SECURITY_CLEARED in memory/warlock-security-audit-2026-06-09.md.
• Safety profile: deterministic stdlib-only text analysis with mutated_files: [].