v0.32.2

v0.32.2

Resilience patch. Three production-incident fixes plus groundwork that ships dormant.

Fixed

• Double cache bust after history compaction. When the historian's compaction marker landed, the next request could re-upload a large part of the prompt because the marker's summary message appeared in the conversation one pass after the compaction itself. The pass that applies the marker now serves the identical representation immediately, so the compaction costs exactly one cache rebuild. On large sessions this saves ~100K cache-write tokens per compaction.
• Multi-process startup storms. A freshly started OpenCode process (for example a second TUI next to a running one) no longer fires background maintenance for every project immediately at boot, and a busy database during startup migration checks now retries with backoff instead of disabling Magic Context for that process.
• Transform failures no longer re-upload the full raw history. If the transform pipeline fails mid-session (for example under database lock pressure), Magic Context now replays the last known-good transformed prompt with the live tail appended, instead of falling back to the raw uncompacted message array. On large sessions this prevents accidental 900K-token uploads during transient failures.
• Cache diagnostics: prompts sent while the transform was unavailable are now attributed to Magic Context instead of "Provider-side".

Internal

• Groundwork for a future Rust-based transform engine (inactive; requires developer configuration that is not part of the public schema).
• New optional embedding provider plumbing (inactive unless explicitly configured).