v0.49.2

v0.49.2

This patch release fixes Oh My Pi turns refused by a check that 0.49.1 added: in sessions with history, on the Responses API, and with several other provider APIs, every turn could be refused with "provider request does not match this pass's managed dispatch (prepared turn structure)". Oh My Pi's doctor --issue report now includes recent errors and the log. There is no database migration.

Upgrading

• No migration. context.db stays at schema 95 and store.db at schema 63. Restart Oh My Pi after updating.
• Only Pi, Oh My Pi and the CLI change. OpenCode 1 and 2 behave exactly as in 0.49.1.

Fixed

Oh My Pi

• Sessions whose input starts with a system entry are no longer refused on every turn. The check that compares the outgoing request with the prepared turn skipped leading system and developer entries on the request side but rejected them on the prepared side. Both sides now skip them the same way; a system entry later in the conversation is still refused (#686, #683, thanks @Qiiks). d3b0cbdf1c.
• Sessions with runs of consecutive assistant messages are no longer refused on the Responses API, for example commentary text followed by an answer from cached Responses history. The check merged those messages into one row on the request side but kept them separate on the prepared side; both sides now group them the same way and compare every text item (#686, thanks @Qiiks). bde7c878ff.
• Turns with older history are no longer refused on the chat-completions API (including Cline models). The check now recognises what Oh My Pi's converter does to that history: it drops empty and reasoning-only assistant replies, moves tool-result images into their own message, and turns a tool result whose call is missing into a note (#683). 04ed01228d.
• Requests are no longer refused on the Google, Vertex, Gemini CLI, Bedrock and Azure Responses APIs, or on Ollama with tool history. The check now reads each of these APIs' native request shape (#683). 593c73a50b, c45f1e0d8b.
• A refusal from this check now says where the request differed: the first differing message position, message counts, roles and which comparison failed. It never includes message text, tool names or ids. 2675e58aeb.

Requests that Magic Context did not prepare are still refused, as in 0.49.1.

CLI

• Oh My Pi doctor --issue reports include environment details, the last 20 errors and the last 400 log lines, sanitized and capped to GitHub's issue size like the Pi and OpenCode reports. Magic Context turn refusals now count as errors in these reports on every host, so a capped report keeps them. 6bc0264962.