The packaged app does open SQLite during the smoke (migrations run, [DB] Added …
column, cache_size lines) but its primary open path prints no "[DB] Driver: …"
line — only the recovery path and the sql.js fallback do — so the #7592 assertion
demanded a line that never exists and every Linux release leg failed on it. The
guard now: rejects the sql.js fallback line (which the fallback always prints),
accepts a native driver line, and otherwise accepts demonstrable database activity;
after readiness the smoke requests /api/monitoring/health and waits for that
activity, outside the readiness retry loop so a missing database is a verdict, not
a retry. The previous commit on this branch had the wait inside the loop and made
ci.yml's Electron Package Smoke fail; electron-smoke-script suite 10/10.
The packaged app opens SQLite lazily and the smoke's readiness URL (/login) never
touches it, so the logs carried no "[DB] Driver: ..." line and
assertNativeDriverSelected failed on the v3.8.50 re-attach (run 33251755872) with
every leg green up to that point — the assertion could not distinguish a native
driver from no database at all. After readiness the smoke now requests
/api/monitoring/health (DB-backed) and waits up to 15 s for the driver line; the
cold-restart assertion is unchanged. Unit tests cover the wait and the timeout.
Landed with the design call resolved per the owner's pick — **option 1**: the synced store is now endpoint-agnostic (persistDiscoveredModels and managedModelImport no longer drop non-chat models at write time), and chat selectability moved to read time (auto-pool expansion in autoStrategy applies filterChatSelectableModels; the models-route projection already had its chatOnly filter). Your discovery test now passes end-to-end (3/3): /api/show capabilities persist per connection and image/embedding requests route through the advertising host.
Reconciliation notes: conflicted areas merged onto the current tip (adobe discovery import, requestedModel preflight signature, resolvedProvider fast-path coexists with the synced-route override — explicit resolution wins); carried base-red drains (#10055 memoization, #11071 test variants) dropped as already-landed; the managed-model-import exclusion test was propagated to the new contract (image/video models persist; the read filter still hides them from chat pickers — pinned by a new assertion). Full battery: 205/206 focused (the one red is a confirmed periodic-timer timing flake on the loaded devbox — 20/20 isolated), autoCombo vitest 30/30, combo suites 46/46, gates + typecheck clean.
Thank you @yourspraveen — the capability probe + routing design was right; it just needed the store contract opened up. Fixes#11087.
