A store that went through OpenCode's official 1.18 → 2.x in-place upgrade is misclassified as a v1 store, and the v2 fail-closed assert then refuses generation-specific access on every read:
[magic-context] v2 refuseIfUnsafe warn: OpenCode store generation mismatch at
~/.local/share/opencode/opencode.db: expected v2, found v1; refusing
generation-specific database access
The official migration keeps the retired message/part tables beside the new session_v2/session_message ones (tens of thousands of legacy rows on a long-lived install), so detectOpenCodeStoreGeneration — keyed on v1-table presence — reads every migrated store as v1.
Impact (observed on opencode 2.0.5/2.0.8 hosts)
Every prompt interrupts within ~20 ms of submission: the plugin's session hook fails during setup, the host swallows the error (zero server-side log lines at the moment of death), and no model call is ever made. Sessions show user → idle(interrupted) with no assistant turn. A clean-install store on the same host version works fine, which makes this look host-version-specific and sent us chasing opencode regressions for a long while before the mismatch warn surfaced in debug logs.
Fix
session_v2 is an unambiguous v2 signal — OpenCode 1.18.x never creates it while every 2.x store does — so prefer it over the v1-message heuristic:
if (tables.has("session_v2")) return "v2" // new, strongest signal
if (tables.has("message") && tables.has("part")) return "v1"
...
Pure 1.18.x stores (no session_v2) keep reading as v1; the pinned live-1.18 fixture test is unchanged and still passes.
Tests
New: a migrated store (message+part+session+project+session_v2+session_message) detects as v2, asserts v2 fine, and asserts v1 throws.
Existing: 492 tests across packages/plugin/src/shared + src/v2 pass, 0 fail.
Related note
The 0.42.6 v2 lane also calls context.model.list() directly (pre-catalog shape), which throws on opencode 2.0.3 hosts whose plugin context predates the model domain — same swallowed-error instant-interrupt symptom. Main already uses context.catalog.model.list, so that one looks resolved on main; mentioning it here since the two combined made 0.42.6 fatal on 2.0.3.
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.
Summary by cubic
Fixes store generation detection so stores migrated through OpenCode's official 1.18 → 2.x upgrade are treated as v2 instead of v1, and keeps the legacy tool-owner backfill working on those stores.
Bug Fixes
session_v2 is now the strongest v2 signal; pure 1.18.x stores without it still detect as v1.
The backfill now checks for the v1 message tables directly instead of asserting a v1 store, so migrated stores are backfilled and pure v2 stores fail fast with a clearer message.
Adds a migrated-store test covering v2 detection, v2 assert pass, and v1 assert throw.
Restores bun.lock to the upstream resolution so bun install --frozen-lockfile passes.
Confidence Score: 4/5
The store-detection and backfill fixes appear sound, but the PR is not yet safe to merge because the lockfile still depends on an unconfigured third-party registry.
The PR corrects OpenCode store-generation detection and its related legacy owner-backfill behavior.
Treats session_v2 as the strongest v2 schema signal, including when migrated stores retain v1 tables.
Allows the owner backfill to process any store that still has the legacy message and part tables.
Adds regression coverage for generation detection and assertions on a migrated schema.
The earlier third-party registry change in bun.lock remains outstanding.
Diagram
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Inspect OpenCode schema] --> B{session_v2 exists?}
B -->|Yes| C[Classify as v2]
B -->|No| D{message and part exist?}
D -->|Yes| E[Classify as v1]
D -->|No| F{session_message exists?}
F -->|Yes| C
F -->|No| G[Empty or unknown]
C --> H{Legacy message tables remain?}
E --> H
H -->|Yes| I[Run best-effort tool-owner backfill]
H -->|No| J[Skip backfill and use lazy adoption]