rename officer-claude to officer-anthropic-proxy

the pm2 entry named officer-claude never ran an agent. it starts
sidecar/claude/index.ts, which registers as capabilities: ['proxy'] and only
holds the anthropic proxy secret and forwards api traffic. the process that
actually spawns claude is sidecar/claude/user-instance.ts, which had no pm2
entry at all and was spawned on demand by the main server.

that misnomer is how both CLAUDE.md files ended up claiming that restarting
officer does not disturb a running agent session. it does: the agent was a
grandchild of officer and died with it. correct the name so the next reader
starts from a true model, and fix the claim in both files.

no behaviour change — officer-agent arrives in the next commit.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/working-on-officer.md

@@ -57,8 +57,13 @@ Commit messages: simple lowercase, no prefixes, explaining *why*.
 
 ## Running and checking your work
 
-The server runs under pm2 as `officer`, plus sidecars (`officer-claude`, `officer-opencode`,
-`officer-email`, `officer-pty`, `officer-vnc`). `pm2 list` shows them; `pm2 logs officer` follows.
+The server runs under pm2 as `officer`, plus sidecars (`officer-anthropic-proxy`, `officer-agent`,
+`officer-opencode`, `officer-email`, `officer-pty`, `officer-vnc`, `officer-music`, `officer-vault`,
+`officer-slskd`). `pm2 list` shows them; `pm2 logs officer` follows.
+
+Two of those names are worth knowing apart: **`officer-anthropic-proxy` holds the Anthropic credential
+and proxies API traffic; `officer-agent` is the process that actually runs `claude`.** They used to be
+one confusingly-named entry (`officer-claude`) that was only the proxy.
 
 **Don't restart the owner's server to test.** Boot your own on a spare port instead — the running
 instance holds `PORT` from `.env` (9010):