opencode crashes on startup when SQLite database is corrupted

[leecoder]

Bug

When the local SQLite database file becomes corrupted, opencode crashes on startup with:

SQLiteError: database disk image is malformed

or:

SQLiteError: file is not a database

This can happen due to power loss, disk issues, or incomplete writes to the WAL file.

Expected Behavior

opencode should detect corruption, backup the corrupted files, and recreate a fresh database so the user can continue working without manual intervention.

Steps to Reproduce

1. Corrupt the database file at ~/.local/share/opencode/opencode.db (e.g. write garbage to internal pages while keeping the SQLite header intact)
2. Run opencode
3. Observe crash

Environment

• OS: macOS
• opencode: latest dev branch

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• opencode crashes on start with SQLITE_CORRUPT #30157: opencode crashes on start with SQLITE_CORRUPT — same error, same crash-on-startup behavior
• SQLite database corruption (database disk image is malformed) when running concurrent sessions on NFS #14970: SQLite database corruption ("database disk image is malformed") — same error message, includes workaround and suggested fixes