Files
platform/deploy/2026.08.24.01.md
T
pastilhasandClaude Opus 5 c813eef6cc release 2026.08.24.01
One frontend file — the transcribe button hidden in the file viewer. No schema,
no dependencies, nothing to verify by query.

Also the first real firing of the rebuilt Platform Deployer commander, which is
why this is the release it gets: if the loop misbehaves the blast radius is a
button that was already invisible.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043
2026-08-24 02:58:36 +00:00

1.9 KiB

2026.08.24.01

One frontend file: the transcribe button is hidden in the file viewer's audio player.

No schema change. Nothing under src/databases/**/schema.ts moved. bun db:push is still a step because it is cheap and it proves the database agrees with the code, but it must report no changes.

No dependency change. bun.lock is untouched. Do not run bun install.

What is in it

  • The transcribe button is hidden. It calls POST /file-browser/transcribe, which refuses on every server here because no STT endpoint is configured anywhere — a control that can only fail, sitting beside OCR and extract-audio, which work. Hidden rather than deleted: speech-to-text is moving to a plugin and the wiring stays correct for when it lands.

Every host

  1. git fetch origin --tags then git merge --ff-only deploy/2026.08.24.01
  2. bun db:push — expect no changes. If it wants to alter something, stop and report it: this release touched no schema, so a diff means that host and this tree disagree about something else.
  3. bun run plugins:update
  4. pm2 restart officer

officer only at step 4. Step 3 restarts each plugin's own sidecar, which belongs in the report.

macbookpro: append /opt/homebrew/bin to PATH for the bun commands, run pm2 separately.

What to check, this release

Open a .m4a in the file browser. The audio player's header should show a download and a close icon and no transcribe icon. An image should still offer OCR and a video should still offer extract audio — if either of those disappeared, too much was hidden.

A stale bundle is the likely failure. Hard refresh before deciding it did not work.

No direct SQL is needed and none is authorised.

Hosts

  • edge-pertento-bridge — skipped, per docs/servers.md.
  • officer-dev — skip it. Restarting officer on the host running the rollout ends the rollout. Name it as skipped and say whether it is current.