docs: record the raised turn timeout and why

channels/http/README.md

@@ -46,7 +46,7 @@ rather than concurrently.
 | `DATA_BRAIN` | `letta` (default) answers from the self-hosted agent; `zo` is the pre-migration persona path. |
 | `DATA_LETTA_AGENT_ID` | The agent to answer as. Defaults to Data's agent. |
 | `DATA_LETTA_BIN` | The Letta CLI. Defaults to `letta`, resolved against `PATH`. |
-| `DATA_LETTA_TIMEOUT_MS` | Turn timeout before the child process is killed. Defaults to `180000`. |
+| `DATA_LETTA_TIMEOUT_MS` | Turn timeout before the child process is killed. Defaults to `180000`; the live service sets `420000`, because a question that sends the agent through a long tool loop can take minutes while a simple one answers in seconds. |
 | `DATA_PERSONA_ID` | Persona id for the `DATA_BRAIN=zo` path only. |
 | `PORT` | Set by the Zo service. Defaults to `8788` from a shell. |
 | `DATA_HTTP_TOKEN` | Optional shared secret. When set, callers must send it as `x-data-token`. |

services/http-api.md

@@ -48,6 +48,11 @@ to keep alive.
   `agent/instructions.md` into the agent's memory), a second question on the same
   `session` continued the conversation, and a question about this service answered from
   `channels/http/index.ts` with a citation.
+- 2026-09-25 — turn timeout raised to `420000` ms on the live service (`DATA_LETTA_TIMEOUT_MS`).
+  Measured the same day: `POST /ask` on a question that sends the agent through a tool loop took
+  4m26s and tripped the `180000` ms default (`letta -> exit null: timed out after 180000ms`), while
+  a two-sentence question about this service answered in 7.2s citing `channels/http/index.ts`.
+  The timeout bounds a turn, not the agent's willingness to investigate.
 - 2026-09-25 — Data's own Google key was wired in. With only `DATA_GEMINI_API_KEY` in
   `/root/.zo_secrets` and no canonical `GEMINI_API_KEY` in the environment, the service
   logged `provider: exported DATA_OPENROUTER_API_KEY as OPENROUTER_API_KEY,