# 2026.08.22.01

349 community themes, Spotlight made usable, prompt history that stops eating drafts, and the email
plugin's multi-account backend.

**No schema change and no dependency change.** Verified against `deploy/2026.08.21.04..HEAD`: nothing
touches a `databases/*/schema.ts`, `package.json` dependencies or `bun.lock`. So **no `bun db:push` and no
`bun install`** — a host that runs either has run something this release did not ask for. Note that the
previous release DID need a push; that was `anthropic_accounts` and it is already applied everywhere.

## What is in it

- **The theme collection.** 147 ports from omarchythemes.com, then 44 more rescued by supporting
  `colors.toml` and `0x`-prefixed hex, then a fix to accent/secondary foreground derivation across 202 of
  them. This is the bulk of the diff: 229 files, ~22.5k lines, almost all data.
- **Spotlight.** Opens on **alt-space** and nothing else, from anywhere including a focused text field.
  The eight-item cap is gone — core items filled it, so every plugin tile was unreachable on a populated
  server. Rows draw the dock's own tiles, and the settings list went from nine hand-written entries to
  twenty read off the screens that declare them.
- **Prompt history.** Up/Down only recall from an empty composer, and any other keystroke ends a recall —
  so a half-written thought is never swapped for one from last week.
- **The email plugin's multi-account backend**, which arrives via `plugins:update` rather than through this
  repository. `?account=<id>` names a mailbox, `?account=all` spans them. **Absent is unchanged**, so
  nothing that calls those routes today behaves differently — including the mobile app and the agent's
  `email_db` tool. Only hosts with the email plugin installed are affected at all.

## Every host

1. `git pull --ff-only` — larger than usual, ~22.5k lines of theme data
2. `bun run plugins:update`
3. `pm2 restart officer`

`officer` only. Step 2 restarts each plugin's own sidecar, which is that script's behaviour and worth
recording in the report rather than omitting.

**`macbookpro`:** append `/opt/homebrew/bin` to PATH for the `bun` commands and run `pm2` separately. See
`docs/servers.md` — replacing the PATH is what broke `pm2` on an earlier deploy.

## `officer-dev` — skip it, and do NOT report it as behind

The commander runs there and skips its own host, as always. But this time the host is **already on this
code**: `officer` was restarted there many times during the night as the work landed, so it is running the
tree this tag names rather than lagging. Report it as skipped and current, not skipped and stale.

## Then check

`pm2 jlist`: `officer` is `online` and `restart_time` moved. Nothing `errored`, including the sidecars step
2 bounced.

A theme picker still lists themes and one loads — the diff is data, so a bad parse would show as a missing
or unreadable theme rather than as a failed boot.

`scripts/deploy-claim.sh state 2026.08.22.01` says `done`.