Audit for detaching the bundled tools into their own containers, talking to
coderai only through the HTTP API (aisbf proxying 1:1, assumed).

One coupling existed: video_editor.py imported codai.api.tts_backends to fill its
emotion and style pickers, which only works while it shares a process tree with
the server. Added GET /v1/audio/speech/capabilities and the editor now asks over
HTTP, falling back to the local import on an older server and to empty lists when
neither answers — the pickers simply don't appear rather than the tool breaking.

Everything else was already clean: no tool sends a local path into the API
expecting the server to read it (media goes base64/multipart), none reads coderai's
own state (models.json, /AI, ~/.coderai), and generated media is always fetched
over HTTP rather than from a shared filesystem.

docs/tools-as-services.md records the audit, what each container would need
(ffmpeg, own volumes, base-url/api-key, long proxy timeouts, large bodies) and
which tools are not API clients at all — review_outputs.py reviews the tools' own
output dirs, and the *_service.py workers are coderai's own subprocesses.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0182DhR1eFNPQyGmDrpHbedY