Start afresh on a device database SQLite cannot read
A damaged device database is moved aside and replaced, so the app is no longer stuck until someone deletes the file.
If napdock.sqlite is not a database or is corrupt, startup reconciliation and every local command used to fail with “Device database unavailable” until the file was deleted by hand.
apps/executor/src/local-control/database.ts now detects SQLite error codes 11 (corrupt) and 26 (not a database), closes the damaged connection, moves napdock.sqlite and its -wal and -shm files to napdock.sqlite.damaged.bak, and opens a fresh 0600 file. The damaged copy is kept, and other failures still report unavailable.
Evidence
No screenshot: Backend change; nothing to screenshot.