v0.49.4

v0.49.4

This patch release fixes Oh My Pi turns that 0.49.3 still refused with "provider request does not match this pass's managed dispatch", and makes every failed history summary record why it failed. There is no database migration.

Upgrading

• No migration. context.db stays at schema 95 and store.db at schema 63. Restart OpenCode 1, OpenCode 2, Pi or Oh My Pi after updating.

Fixed

Oh My Pi

• Sessions with extension messages or a compaction summary are no longer refused on the chat-completions API. The check now builds those rows the way Oh My Pi does: custom extension messages and compaction summaries become user rows, and only rows left with no text or images are dropped (#686, thanks @Qiiks). 4e0619d73b.
• Sessions with earlier replies from other models are no longer refused on the Responses and Codex APIs. The check now models those replies the way Oh My Pi sends them. When a reply can't be modelled, it no longer compares against a shape that could never match; it still refuses any request that doesn't carry Magic Context's prepared history (#686, thanks @Qiiks). 4e0619d73b.

History

• Every failed history summary now records a reason. On Pi and Oh My Pi a failed run used to store an empty reason. Magic Context's own reasons are kept word for word; provider and other external errors keep their status, error type and code, with no provider text; a Pi subprocess failure keeps its exit code and the first line of a known launch error, such as an extension that failed to load (#694). 72d298a84d.