fix(db): use DOUBLE PRECISION for position and progress columns

Co-Authored-By: Claude Opus 5.5 <[email protected]>

packages/db/migrations/0001_init.sql

@@ -21,7 +21,7 @@ CREATE TABLE course_acl (
 CREATE TABLE progress (
   user_id TEXT NOT NULL, course_id TEXT NOT NULL, lesson_id TEXT NOT NULL,
   state TEXT NOT NULL CHECK (state IN ('not-started', 'in-progress', 'done')),
-  position_seconds REAL,
+  position_seconds DOUBLE PRECISION,
   updated_at TEXT NOT NULL,
   PRIMARY KEY (user_id, course_id, lesson_id)
 );
@@ -61,7 +61,7 @@ CREATE TABLE collection_courses (
   PRIMARY KEY (collection_id, course_id)
 );
 CREATE TABLE jobs (
-  id TEXT PRIMARY KEY, kind TEXT NOT NULL, status TEXT NOT NULL, progress REAL NOT NULL,
+  id TEXT PRIMARY KEY, kind TEXT NOT NULL, status TEXT NOT NULL, progress DOUBLE PRECISION NOT NULL,
   message TEXT, payload_json TEXT NOT NULL, result_json TEXT, error TEXT,
   created_at TEXT NOT NULL, updated_at TEXT NOT NULL
 );