The 20260507164347_add_workspace_time migration shipped as
ALTER TABLE \`workspace\` ADD \`time_used\` integer NOT NULL;
bun:sqlite (and standard SQLite) refuse to add a NOT NULL column
without a DEFAULT to a non-empty table. Anyone upgrading from
v1.14.41 (Hono) to v1.14.42 with populated workspace rows hit
"Cannot add a NOT NULL column with default value NULL" at startup
and the app crashed before reaching the TUI.
Dev users hadn't noticed because they pulled the migration when
their workspace table was empty (or under a fresh fixture); the
ALTER then succeeded and was journaled. State C (empty table at
migration time = success), state A/B (populated table at migration
time = crash) — only state A/B users hit the bug, and only on
upgrade from v1.14.41.
Replace with a table-recreate pattern that is idempotent across
both states. The SELECT pulls only columns from the v1.14.41
schema, so it works whether time_used exists or not. The new
table defines time_used with DEFAULT 0; existing rows reset to 0,
which is acceptable because time_used is a usage counter the app
re-derives anyway and is brand new in v1.14.42.
Verified locally on bun:sqlite for both states.
