platform/deploy/2026.08.22.01.report.md

2026.08.22.01 — deploy report

6 of 6 hosts succeeded. officer-dev skipped (the commander's own host) and already on this code. No host failed, no process came back errored.

Tag deploy/2026.08.22.01 → 78db9c8c. package.json reads 2026.08.22.01 at that commit — they agree. Every host went 98177c3b → 78db9c8c, a clean fast-forward.

Per the plan: no bun install and no bun db:push ran anywhere.

Per host

alpha — succeeded

• Checkout /home/pastilhas/officerdev/platform, from PM2's pm_cwd (the stale second checkout at ~/dockers/officer.dev/platform was not touched).
• Tree clean, tracked and untracked both. HEAD 98177c3b → 78db9c8c.
• bun run plugins:update: 12/12 updated in 48s, no plugin reported a failure. It bounced twelve plugin sidecars of its own accord — atelier, bitcoin-wallet, email, gitea, invoices, jellyfin, music, offscale, photos, soulseek, transmission, vault.
• pm2 restart officer: restart_time 64 → 65, online.
• All 19 processes online afterwards.

One gap, stated because it is the kind of thing a report should not quietly round up: the exit code of plugins:update was lost on this host — the shell wrapper swallowed it. Success is asserted from the 12/12 updated line and the absence of any per-plugin failure, not from an exit status. Every other host captured an explicit 0.

fofos — succeeded

• Checkout /home/pastilhas/officerdev/platform. HEAD 98177c3b → 78db9c8c.
• One untracked file present: scripts/chk.ts. Noted, not a reason to skip — a fast-forward cannot touch it, and it was left alone. No tracked change.
• plugins:update exit 0: 1/1 updated in 7s (gitea), its sidecar restarted.
• pm2 restart officer: 18 → 19, online. All 8 processes online.
• The capabilities sync that failed here for three deploys ran clean: capabilities: pulled. The ownership fix of 2026-08-21 is holding.

macbookpro — succeeded

• Awake and reachable. Checkout /Users/pastilhas/projects/officer-suite/platform.
• HEAD 98177c3b → 78db9c8c, tree clean.
• bun run with PATH=$PATH:/opt/homebrew/bin appended, pm2 run as a separate command through the interactive shell, exactly as the plan and docs/servers.md require.
• plugins:update exit 0: no plugins installed — nothing to update. No sidecar bounced.
• pm2 restart officer: 5 → 6, online. All 6 processes online.

edge-pertento-bridge — succeeded

• Checkout /home/pastilhas/officerdev/platform. HEAD 98177c3b → 78db9c8c, tree clean.
• plugins:update exit 0: 2/2 updated in 9s (gitea, offscale), both sidecars restarted.
• pm2 restart officer: 7 → 8, online. All 8 processes online.

production-pertento-bridge — succeeded

• Checkout /home/pastilhas/officerdev/platform. HEAD 98177c3b → 78db9c8c, tree clean.
• plugins:update exit 0: 1/1 updated in 4s (gitea), its sidecar restarted. nvm printed its .npmrc globalconfig/prefix warning first. Pre-existing, unrelated to this release, and the command still exited 0 — recorded so the next reader does not chase it.
• pm2 restart officer: 9 → 10, online.
• This host also runs a non-Officer PM2 set (Dashboard, Tracking, Uptime, five Crons * entries). All online, none touched.

deadpool-rezio-bridge — succeeded

• Login br, not pastilhas. Checkout /home/br/officerdev/platform.
• HEAD 98177c3b → 78db9c8c, tree clean.
• plugins:update exit 0: 2/2 updated in 8s (email, offscale), both sidecars restarted. Printed capabilities: adopted rather than pulled — this host's capabilities checkout is newer than the others'. Not an error.
• pm2 restart officer: 3 → 4, online. All 9 processes online.

officer-dev — SKIPPED, and current

The commander runs here, inside officer-claude-code. Nothing was pulled and nothing restarted.

It is not behind: deploy/2026.08.22.01 is an ancestor of the local HEAD. The checkout is in fact two commits past the tag — c9823533 and 0c2ff88c, neither on origin when this ran — written by another agent working in this same tree during the rollout. Its work was left alone; only this report was staged, by path.

Worth knowing rather than discovering: pushing this report carries those two commits to origin/master with it, because they are its ancestors. Nothing was deployed from them — every host in this rollout is at 78db9c8c, the tag — but the next release will include them.

officer here is online at restart_time 180, running the tree this tag names.

Verification

• Every restarted process came back. pm2 jlist re-read on each host after the restart: officer online with restart_time incremented, and no process anywhere in state errored or stopped.
• The theme data landed. The release is mostly data, so a bad file shows up as a missing or unreadable theme rather than a failed boot. All six hosts carry 227 theme CSS files under src/workspaces/theme/css/themes/, matching the release tree exactly.
• scripts/deploy-claim.sh state 2026.08.22.01 → done.

What was not done

• officer-dev was skipped entirely — its own host, by design. The owner restarts it deliberately when happy with the rest. It needs no pull.
• No theme was loaded through a UI. The plan asks that a theme picker still lists themes and one loads. A commander cannot click. The file-count check above is the substitute, and it is weaker: it proves the files arrived, not that each parses.
• alpha's plugins:update exit code was not captured (see above). Judged from output, not status.