Use direct connection for table creation to fix persistence

Author: crocodilestick

CONTRIBUTORS

@@ -303,7 +303,7 @@ Copyright (C) 2024-2025 Calibre-Web Automated contributors
 - zhiyue (1 commits)
 # Fork Contributors (crocodilestick/calibre-web-automated)
 
-- crocodilestick (780 commits)
+- crocodilestick (781 commits)
 - jmarmstrong1207 (73 commits)
 - demitrix (30 commits)
 - sirwolfgang (29 commits)

cps/db.py

@@ -15,6 +15,7 @@
 from uuid import uuid4
 
 from sqlite3 import OperationalError as sqliteOperationalError
+import sqlite3
 from sqlalchemy import create_engine
 from sqlalchemy import Table, Column, ForeignKey, CheckConstraint
 from sqlalchemy import String, Integer, Boolean, TIMESTAMP, Float
@@ -736,8 +737,13 @@ def setup_db(cls, config_calibre_dir, app_db_path):
             inst.init_session()
 
         # Ensure progress syncing tables exist in metadata.db (book checksums)
+        # Use a direct connection to ensure the table is created in the file, not in-memory
         from .progress_syncing.models import ensure_calibre_db_tables
-        ensure_calibre_db_tables(conn)
+        try:
+            with sqlite3.connect(dbpath, timeout=30) as direct_conn:
+                ensure_calibre_db_tables(direct_conn)
+        except Exception as e:
+            log.error(f"Failed to ensure progress syncing tables: {e}")
 
         cls._init = True