Checked October 29, 2026. The operator has verified an existing OpenClawLab installation running Bob v0.7.2 with the updated Activity Manager, mobile Settings, status stages, original-thought drafting, and Moltbook publishing. The operator successfully installed bobctl update and received up to date (v0.7.2-updater-bootstrap).
| Workflow | Status | What it does |
|---|---|---|
bobctl update --check |
Verified by owner | Confirms the installed GitHub release registry and checks for an available manifest |
bobctl update |
Operator-verified on real releases | Installed several reviewed manifest-driven dashboard changes, including the queue-management Pending-filter fix |
| Existing-host upgrades through historical scripts | Used successfully for v0.7.1/v0.7.2 | Exact-match checks, SQLite backup, staged code swaps, rollback/health checks |
scripts/bootstrap_bob_updater.py |
Verified on owner's existing host | One-time registration of known-good v0.7.2 code and installation of the updater command |
| Fresh Windows/WSL/OpenClawLab installation from a clone | Not implemented or verified | There is no supported unattended/new-host setup installer |
Existing release scripts and the updater depend on preexisting state: OpenClawLab WSL2 distro, ordinary openclaw user, Docker/OpenClaw/Ollama and local model, systemd user services/timers, a private credentials file, an existing application database and startup recovery configuration. Their guards deliberately refuse arbitrary unknown hosts rather than secretly creating users, generating tokens, exposing API credentials or starting autonomous publication.
The v0.7.1 end-to-end systemd install document describes a disposable rehearsal, not a production clean-install procedure. Its old blocker descriptions are historical: v0.7.1 production upgrades were subsequently deployed, but the new-host installer gap remains.
A production-ready clean installation should have one guided command and explicit steps for:
- Windows/WSL2, Linux user, systemd and local port prerequisites; clear failure messages without modifying an existing host.
- Local Ollama and OpenClaw/Docker preflight; model selection and private dependency installation, with user consent before downloads or external services.
- Owner-private Moltbook credentials and dashboard username/password setup, without exposing them in shell history, logs or Git.
- Database creation and the initial protected application files, user systemd services/timers, and Windows reboot/startup recovery, with activation off by default until reviewed.
- Authenticated dashboard health, read-only worker readiness and a one-step rollback/uninstall that preserves private data and never automatically posts.
- One fresh-environment acceptance on a disposable OpenClawLab VM/WSL distro, not just synthetic tests.
A clean installer must never run the old v0.7.1/v0.7.2 pinned update scripts on an unrecognized installation.
The canonical source branch is now main (PR #5 was merged and the resulting tree was verified). The operator reports the updater's migration from feature/v0.7.1-navigation to canonical main completed successfully. The guarded one-time main updater migration creates a separate trusted ~/bob-main checkout, re-pins the updater to main, and updates its private release registry without stopping services or touching SQLite.
The owner reports a successful migration to main and working nonempty manifest releases through v0.7.2-queues2. The historical feature branch remains available for recovery. The next compact Scout/Activity release is prepared but not yet installed. This remains an existing-host upgrade channel, not a new-host installer.