v0.49.5

v0.49.5

This patch release fixes two more cases where Oh My Pi turns failed with "provider request does not match this pass's managed dispatch". It also stops a harmless error from appearing in the Oh My Pi log. 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 many images no longer fail. To stay within a provider's image limit, Oh My Pi leaves the oldest images out of each request (it keeps five when the provider has no limit of its own). Magic Context's check now expects this: only the oldest images may be missing, in order, and everything else must still match. Sessions with fewer images are checked exactly as before (#686, thanks @Qiiks). 418f5b8f42.
• Sessions that keep a tool result without its tool call no longer fail. This can happen after a compaction summary. Oh My Pi sends such a result as a short note saying the tool result is stale, and Magic Context's check now expects the same note. A tool result whose call is still in the history must match exactly (#698). f1b167faf1.
• "Pi context pass superseded" no longer appears in the log. It was logged when a newer turn replaced an older one before the older one had finished saving. Nothing was lost. Other errors of this kind are still logged (#698). 636394d0df.

Tested with Oh My Pi 18.10.4, 18.11.0 and 18.11.1.