Reset a native journal that is not a database
A workspace journal that is corrupt or not a SQLite file is moved aside and recreated instead of failing every turn.
Before, a workspace’s journal.sqlite that was not a database (SQLITE_NOTADB) or was corrupt (SQLITE_CORRUPT) made every submit and status read fail with “Native journal unavailable”, and the file was never touched.
openJournal in packages/agent-runner/src/journal.ts now moves the file and its -wal and -shm files to *.damaged.bak, recreates it with mode 0600, logs native_journal_reset, and connects again. Other failures, such as permissions or I/O errors, still report unavailable. The reset loses that workspace’s journaled turn receipts, in line with the pre-release rule of resetting rather than repairing.
Evidence
No screenshot: Backend change; nothing to screenshot.