[P0][doc-drift] SQLite Browser: backend exists, frontend UI is missing

[EVWorth]

Context

docs/audits/README.md batch 4 lists SQLite as a pending audit target. ARCHITECTURE references SQLite for connection profile storage (rusqlite, shipped), but a SQLite BROWSER feature is implied by the existence of the mas-sqlite crate and 8 sqlite_* Tauri commands yet no UI delivers it.

Problem

src-tauri/crates/mas-sqlite/ (413 LOC) plus src-tauri/src/commands/sqlite.rs (sqlite_open, sqlite_close, sqlite_list, sqlite_execute, sqlite_get_tables, sqlite_get_columns, sqlite_get_indexes, sqlite_get_table_ddl) compile and register in invoke_handler but no frontend caller ever invokes them. Verification: grep -rn sqliteOpen src/components src/stores src/App.tsx returns 0 hits.

Files

• src-tauri/crates/mas-sqlite/src/{connection,query,schema,error,lib}.rs
• src-tauri/src/commands/sqlite.rs
• src/lib/tauri-api.ts:145-163
• docs/audits/sqlite.md

Expected

Either SQLite Browser ships as a user-facing feature, or the crate is removed and ARCHITECTURE doc is amended to reflect.

Proposed fix

L: build the SQLite browser UI. Add SqliteConnection to useConnectionStore, SqlitePanel mirroring src/components/schema/, SqliteOpenDialog for file picker, register in MenuBar and ConnectionTabs.

Acceptance

grep -rn sqliteOpen src/components src/stores returns >=3 hits. User can File > Open > SQLite Database, browse tables, run SELECT, see results in same grid as MySQL sessions.

Needs human verify

yes (UX placement decisions)