_{P1 Badge} Persist provider session updates in SQLite

When a streamed/non-streamed response returns the provider conversation IDs, this only mutates the object returned by storeManager.getSessionById. With the new SQLite store, getSessionById parses JSON and returns a detached copy, so providerSessionId, parentMessageId, historyHash, and lastActiveAt are never written back via storeManager.updateSession. On the next turn the route reads the old row and sends no provider parent/session IDs, so Qwen multi-turn context is still lost after the first request.

Useful? React with 👍 / 👎.

_{P1 Badge} Create the storage directory before opening SQLite

On a fresh install where ~/.chat2api does not already exist, new Database(this.dbPath) attempts to create store.db inside a missing parent directory and fails with SQLITE_CANTOPEN, aborting storage initialization before the later request-log manager has a chance to mkdir anything. This only works for users who already have the legacy storage directory, so new users cannot start the app.

Useful? React with 👍 / 👎.

_{P1 Badge} Do not re-encrypt migrated credentials

During migration, account credential values read from the old data.json are already the per-field safeStorage ciphertext written by the previous addAccount path, but this loop encrypts those ciphertext strings again. After upgrade, getAccounts(true) decrypts only the outer layer and providers receive the old base64 ciphertext instead of the real token, so existing accounts fail authentication until users re-enter every credential.

Useful? React with 👍 / 👎.