v0.19.0 — Ask Optio in the API pod, machine agent limits

Added

• Ask Optio runs in the API pod by default. A turn is a child process of the API through a new process runtime that speaks the same run protocol as the pod runtimes, instead of a pooled agent pod per conversation. The API image now carries Claude Code and Codex, and the chart mounts an agent home at /home/agent. OPTIO_ASSISTANT_PLACEMENT=agent-pod (Helm optio.assistant.placement) keeps the separate pod; a turn with a repo, another harness, or past OPTIO_ASSISTANT_IN_POD_MAX (default 3) running turns goes to an agent pod anyway.
• Machines have an agent limit (default 3): agent sessions that automations, Jobs, Tasks and tickets start past it queue ("Queued") and start as agents finish, oldest first, the way a repo's concurrency limit queues pod tasks. A session you open by hand always starts but counts; shells and plain commands never count. Set it on the Machines page on the web, or on a machine's page in the iOS and Android apps (PATCH /api/local/hosts/:id).

Fixed

• iOS: swiping through a Codex session's terminal scrolls again. Wheel reports carried the bottom-right cell as the pointer, which Codex ignores (it only scrolls over its transcript); Claude Code scrolled regardless.

Upgrading

• Helm: helm upgrade adds the agent-home emptyDir and the OPTIO_ASSISTANT_PLACEMENT / OPTIO_ASSISTANT_IN_POD_MAX env to the API deployment; releases upgraded with --reuse-values get the defaults.
• A migration adds local_hosts.max_concurrent_agents (default 3).