platform/deploy/2026.08.29.03.report.md

2026.08.29.03 — deploy report

7 of 7 target hosts succeeded. officer-dev skipped, as required.

Tag deploy/2026.08.29.03 → 03fbb118, matching package.json. Plan: deploy/2026.08.29.03.md. Every host ended at 03fbb118.

Rolled out one host at a time, first release under a new watcher.

Per host

Host	HEAD before	HEAD after	plugins:update	officer restart_time	health	file-browser/ls
alpha	78bf63c2	03fbb118	15/15	4 → 5	401	200, 76 entries
fofos	21665ed0	03fbb118	5/5	45 → 46	401	200, 38 entries
macbookpro	78bf63c2	03fbb118	none installed	4 → 5	401 (:9010)	200, 62 entries
macbruno	78bf63c2	03fbb118	1/1	7 → 8	401	200, 41 entries
production-pertento-bridge	78bf63c2	03fbb118	1/1	5 → 6	401 (:9010)	200, 53 entries
edge-pertento-bridge	78bf63c2	03fbb118	2/2	6 → 7	401	200, 29 entries
deadpool-rezio-bridge	78bf63c2	03fbb118	2/2	23 → 24	401	200, 49 entries

Every host: tracked tree clean, git merge --ff-only deploy/2026.08.29.03 fast-forwarded, officer came back online with a moved restart_time, and no process on any host was left off-line. Ports were read from each checkout's own .env rather than assumed. 401 on /api/health is healthy per the plan.

What was NOT done

• officer-dev — skipped entirely. Not pulled, nothing restarted. The rollout ran there, inside officer-claude-code; restarting would have ended it mid-deploy. It is already at 03fbb118, so no code is missing — only its officer process still runs the previous build. The owner restarts it deliberately.
• No bun db:push, no bun install, no SQL. The plan states there is no schema and no dependency change, and says improvising either is itself the error. Nothing was queried because nothing was changed. This release has no schema verification, by design.
• Orphaned todos rows in role_permissions left alone, as the plan instructs. Absence denies.

Worth knowing

• A commit landed on master mid-rollout. origin/master reached 44f16fed while hosts 4–7 were fetching. No host took it: every merge targeted the tag, not the branch, so the fleet is uniformly at 03fbb118. 44f16fed is undeployed and rides the next release. This is the 2026-08-23 failure not happening.
• plugins:update moved more than officer. It restarts sidecars itself — around twelve on alpha — and added and started one each on production-pertento-bridge (gitea), edge-pertento-bridge (offscale) and deadpool-rezio-bridge (email).
• fofos has an untracked scripts/chk.ts. Left in place. Untracked files are a note, not a skip.
• edge-pertento-bridge needed no special handling. docs/servers.md warns it may be far behind after its outage; it was already at deploy/2026.08.29.02. That warning is now stale.
• /todos now 404s on all seven hosts. Intended — the board is the kanban plugin, installed nowhere by default.