platform/deploy/2026.08.24.02.report.md

2026.08.24.02 — deploy report

5 of 5 target hosts succeeded. Two hosts skipped by plan, neither a failure.

Rolled out deploy/2026.08.24.02 → e0d80fd3. Tag and package.json agreed. Every target moved c813eef6 → e0d80fd3 — one commit, no host ahead, no host behind.

Speech-to-text left the platform. Nothing was installed in its place: the transcribe plugin is in the catalogue and available, and per the plan no host was given it. That is the owner's decision, per host.

Per host

Host	Before	After	db:push	plugins	officer restart	processes
alpha	c813eef6	e0d80fd3	no changes	13/13	74 → 75	20/20 online
fofos	c813eef6	e0d80fd3	no changes	1/1	27 → 28	8/8 online
production-pertento-bridge	c813eef6	e0d80fd3	no changes	1/1	6 → 7	15/15 online
deadpool-rezio-bridge	c813eef6	e0d80fd3	no changes	2/2	12 → 13	9/9 online
macbookpro	c813eef6	e0d80fd3	no changes	none installed	14 → 15	6/6 online

Every host ran the plan's four steps in order, all four exited 0, and none was stopped early. Checkout paths were taken from each officer process's pm_cwd, not assumed — alpha resolved to ~/officerdev/platform, not its stale second checkout. deadpool-rezio-bridge was reached as br. macbookpro was awake; its bun commands ran with /opt/homebrew/bin appended to PATH and pm2 as a separate command.

Schema — verified, not assumed

The plan says no schema changed and bun db:push must report no changes. It reported none on all five hosts, and the evidence is that it emitted no DDL: no ALTER, no CREATE, no statement of any kind between reading the config and finishing. [✓] Changes applied alone was not treated as evidence — drizzle-kit push prints that line whether or not it did anything, and it can exit 0 on a half-applied change.

stdin was /dev/null on every host, so no prompt could be answered and none was. No direct SQL was needed, none was authorised, and none was run. --force was not used anywhere.

The seed steps that follow push were no-ops everywhere, which is the same answer from a second angle: 0 seeded, 4 already present for roles on all five, and every transcript already recorded.

Skipped

• officer-dev — the host this rollout ran on. Not pulled, nothing restarted. It already carries e0d80fd3 and has the transcribe plugin installed. Restarting officer here ends the rollout mid-flight, so the whole host is left alone deliberately. The owner restarts it, as the last step, once happy with the rest.
• edge-pertento-bridge — deliberately skipped per docs/servers.md, down since 2026-08-23 by the owner's call. Not contacted at all, so it cost nothing this time.

Notes — nothing here needs action

• plugins:update bounced far more than officer. Sequential per plugin, each printing sidecar: started: 13 sidecars on alpha, 2 on deadpool, 1 each on fofos and production-pertento-bridge. A report listing only officer under "restarted" would understate what moved. All came back online.
• fofos has one untracked file, scripts/chk.ts. A note, not a skip — a fast-forward could never touch it, and nobody's work was discarded to ship this.
• production-pertento-bridge prints an nvm warning on every interactive shell: .npmrc carries a globalconfig/prefix setting incompatible with nvm. Cosmetic, pre-existing, unrelated to this release, and it did not affect any step. Not fixed — that is not a rollout's job.

What was not verified

The plan's visible check — that Settings no longer offers Speech to Text — is a browser check, and this rollout has no browser. The code carrying that screen is gone from every host's tree, which is verified; that the rendered UI reflects it is not, and a stale JS bundle would look identical to a failed deploy. Hard refresh before concluding anything from it.