tui: upgrade database migration system to drizzle migrator

Replaces custom migration system with drizzle-orm's built-in migrator, bundling migrations at build-time instead of runtime generation. This reduces bundle complexity and provides better integration with drizzle's migration tracking.

AGENTS.md

@@ -1,80 +1,93 @@
-- To regenerate the JavaScript SDK, run `./packages/sdk/js/script/build.ts`.
-- ALWAYS USE PARALLEL TOOLS WHEN APPLICABLE.
-- The default branch in this repo is `dev`.
+# Agent Instructions
+
+## Quick Reference
+
+- Default branch: `dev`
+- Regenerate JS SDK: `./packages/sdk/js/script/build.ts`
+- Always use parallel tools when applicable
 
 ## Style Guide
 
+### General Principles
+
 - Keep things in one function unless composable or reusable
-- Avoid unnecessary destructuring. Instead of `const { a, b } = obj`, use `obj.a` and `obj.b` to preserve context
 - Avoid `try`/`catch` where possible
 - Avoid using the `any` type
-- Prefer single word variable names where possible
-- Use Bun APIs when possible, like `Bun.file()`
+- Use Bun APIs when possible (e.g., `Bun.file()` instead of `fs.existsSync()`)
+- For sync file reads, use `readFileSync` from `fs` (Bun.file is async-only)
+- Avoid generated file artifacts - prefer build-time `define` globals for bundled data
 
-### Avoid let statements
+### Naming
 
-We don't like `let` statements, especially combined with if/else statements.
-Prefer `const`.
-
-Good:
+Prefer single word variable names. Only use multiple words if necessary.
 
 ```ts
-const foo = condition ? 1 : 2
+// Good
+const foo = 1
+const bar = 2
+
+// Bad
+const fooBar = 1
+const barBaz = 2
 ```
 
-Bad:
+Reduce total variable count by inlining when a value is only used once.
 
 ```ts
-let foo
+// Good
+const journal = await Bun.file(path.join(dir, "journal.json")).json()
 
+// Bad
+const journalPath = path.join(dir, "journal.json")
+const journal = await Bun.file(journalPath).json()
+```
+
+### Destructuring
+
+Avoid unnecessary destructuring. Use dot notation to preserve context.
+
+```ts
+// Good
+obj.a
+obj.b
+
+// Bad
+const { a, b } = obj
+```
+
+### Variables
+
+Prefer `const` over `let`. Use ternaries or early returns instead of reassignment.
+
+```ts
+// Good
+const foo = condition ? 1 : 2
+
+// Bad
+let foo
 if (condition) foo = 1
 else foo = 2
 ```
 
-### Avoid else statements
+### Control Flow
 
-Prefer early returns or using an `iife` to avoid else statements.
-
-Good:
+Avoid `else` statements. Prefer early returns.
 
 ```ts
+// Good
 function foo() {
   if (condition) return 1
   return 2
 }
-```
 
-Bad:
-
-```ts
+// Bad
 function foo() {
   if (condition) return 1
   else return 2
 }
 ```
 
-### Prefer single word naming
-
-Try your best to find a single word name for your variables, functions, etc.
-Only use multiple words if you cannot.
-
-Good:
-
-```ts
-const foo = 1
-const bar = 2
-const baz = 3
-```
-
-Bad:
-
-```ts
-const fooBar = 1
-const barBaz = 2
-const bazFoo = 3
-```
-
 ## Testing
 
-You MUST avoid using `mocks` as much as possible.
-Tests MUST test actual implementation, do not duplicate logic into a test.
+- Avoid mocks as much as possible
+- Test actual implementation, do not duplicate logic into tests