fix: replace migrations with final schema bootstrap

[krasnoperov]

Why

PatchRelay runs one production SQLite database that is already on the current schema. Startup compatibility migrations were still rebuilding issues through issues_new, DROP TABLE, and RENAME, which could destroy the live schema when interrupted.

What changed

• replace all upgrade, backfill, and retired-column logic with one declarative final schema bootstrap
• limit startup schema work to CREATE TABLE/INDEX IF NOT EXISTS
• include every column used by current stores in fresh databases
• remove legacy migration fixtures and add regression tests that forbid destructive DDL or data migration in the bootstrap
• keep read-only operator preflight behavior explicit

Existing older schemas are intentionally unsupported; this deployment targets the single current production database.

Validation

• pnpm run ci — 1024 tests, lint, typecheck, and build pass
• focused schema/store/preflight tests pass
• fresh schema and live production schema have identical table columns except the two operator-feed columns now correctly included in the final schema; those will be added once, offline, before the production restart
• live PRAGMA integrity_check is ok

[review-quill]

Verdict: 🛑 Request changes — The bootstrap must be transactional so an interrupted first startup remains safely retryable.

[review-quill]

🚨 If a fresh install stops mid-exec, the next startup sees the first created table and refuses to resume, leaving the database incomplete. Make the bootstrap atomic.

Suggested change

	connection.exec(schema);
	connection.transaction(() => connection.exec(schema))();