Files
platform/deploy/2026.08.24.02.md
pastilhasandClaude Opus 5 e0d80fd3ae release 2026.08.24.02
Speech-to-text leaves the platform for the transcribe plugin. No schema, no
dependencies — a removal plus a catalogue entry.

The plan says explicitly not to install the plugin during the rollout. Which
hosts get transcription is the owner's call, made per host, and an install now
grants access to every role. Removing and installing in one unattended pass
would decide that for five machines at once.

Nothing is lost anywhere: no host had an STT endpoint configured, so the routes
this removes have never answered on any of them.

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

55 lines
2.7 KiB
Markdown

# 2026.08.24.02
Speech-to-text leaves the platform. It is a plugin now — `transcribe`, in the catalogue.
**No schema change.** Nothing under `src/databases/**/schema.ts` moved. `bun db:push` stays a step because
it is cheap and 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
- **`api/stt/` and `server-settings/stt.ts` are gone**, along with `POST /chat/stt`,
`POST /file-browser/transcribe`, the FileViewer handler behind the button hidden last release, the
Settings → Speech to Text screen and the orphaned locale keys in all six locales.
- **The transcription logic moved byte for byte** into `plugins/transcribe` — the two-pass
detect-then-transcribe, the 25 language priming prompts, the timeouts. Verified identical, not rewritten.
- **`transcribe` is in the catalogue**, so it can be installed from `/plugins` on any host that wants it.
## Installing the plugin is NOT part of this release
This release only removes. A host that had speech-to-text configured loses it until somebody installs the
plugin and points it at a server — and no host here had it configured, so nothing is lost anywhere.
**Do not install it as part of the rollout.** Which hosts get transcription is the owner's decision, made
per host, and an install grants access to every role. Report that the catalogue entry is available; leave
it there.
## Every host
1. `git fetch origin --tags` then `git merge --ff-only deploy/2026.08.24.02`
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
**Settings should no longer offer Speech to Text.** That screen is gone, and its absence is the visible
change. If it is still there, the frontend bundle is stale — hard refresh before deciding it failed.
The audio player's header should still show download and close, and still no transcribe icon. Images
should still offer OCR and videos extract audio; those stay in the platform for now.
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. It
already has this code and the plugin installed; name it as skipped and say so.