docs(TASK-044): review polish — visible-output wording, web-search wire pin note, truncation debug line, thinking-exclusion pin test

CHANGELOG.md

@@ -12,12 +12,15 @@ migrate them to the sibling `patch.responses` key / the model patch's `responses
 (env override: `COYOTE_PATCH_<client>_RESPONSES`).
 - Sessions saved after this change may contain the new `reasoning` thinking blocks (encrypted
 reasoning items from the Responses API); older coyote binaries cannot load those sessions.
+- OpenAI native web search (the bundled `web_search_coyote` tool) uses the chat-only
+`gpt-4o-*search-preview` mechanism, which the responses wire does not serve: until the tool is
+updated, pin `wire_api: chat` on the openai client when relying on it.
 
 ### Feat
 
 - support `wire_api: responses | chat` on the openai and openai-compatible clients, with wire-aware request patching on both patch layers
 - report token usage (including cached input tokens) on the openai responses path
-- streaming responses that end with `response.incomplete` now surface the truncation reason (e.g. `max_output_tokens`) when no output was delivered — matching the non-streaming behavior — and record token usage for truncated turns instead of ending silently
+- streaming responses that end with `response.incomplete` now surface the truncation reason (e.g. `max_output_tokens`) when no visible output (text or tool calls) was delivered — matching the non-streaming behavior — and record token usage for truncated turns instead of ending silently
 - the responses wire always sends `include: ["reasoning.encrypted_content"]` and `"strict": false` tool definitions; strict third-party `/v1/responses` servers may reject these as unknown params when opted in via `wire_api: responses` (workaround: a `responses`-keyed client patch, e.g. `include: null` for Groq)
 
 ## v0.10.3 (2026-09-15)