v0.42.3

v0.42.3

Migration / breaking

• No shared database schema change; the fence stays at 84.
• No Rust module change; ck-mc from v0.42.1 remains current.

Pi package re-published

npm acknowledged the v0.42.2 publish of @cortexkit/pi-magic-context but left the version staged and never made it installable, so Pi installs kept resolving 0.42.1 and missed the v0.42.2 high-fill fix. v0.42.3 re-publishes all three packages at one version; the release pipeline now verifies each package is visible on the registry before a release is declared shipped.

Synchronous OpenCode database reads could block the host for seconds (#440)

On the stock OpenCode schema, SQLite planned Magic Context's bounded message-ID part reads on the session index — a scan of the whole session's parts per page (4–5 seconds each on a 102k-part session, repeated during index reconciliation) — and compaction-marker discovery scanned every session part and then messages once per marker. Every bounded part lookup now disqualifies the session-only index so the message-ID index drives the plan, and marker discovery scans summaries once before fetching boundary parts in pages of at most 800. Query plans are pinned by tests on the stock schema with absent and adversarial statistics on both SQLite runtimes, and old-vs-new marker reconciliation is proven identical. Thanks to @null-axiom for the exact SQL fingerprints, the standalone reproduction and the validated fix.

OpenCode v2 groundwork does not change v1 installs

This release carries the first slice of OpenCode v2 host support (a v2 entry under dist/v2/, a hermetic v2 test runner). It is inert on OpenCode 1.x: the package publishes no ./server export (the 1.x loader would resolve it ahead of main) and no v2 SDK in its runtime dependencies (its peer range on @opentui/* conflicts with the 1.x TUI packages and would fail npm install). Both are pinned by tests; the release smoke now installs the packed package as a consumer with the stock npm resolver before booting OpenCode.