Summary

SQL result-grid Save still lags Table Browser after #772 / #774 / #792.

1. Schema load failure — getTableSchema is catch (_) { pks = []; } in PG/MySQL/SQLite SQL workspaces. Save stays off; status is still N row(s). — indistinguishable from a healthy grid. Table Browser now shows “schema unavailable”.
2. SQLite implicit rowid — SQL SELECT * does not project rowid and uses declared PKs only. Table Browser edits CREATE TABLE t (name TEXT) via rowid; SQL-grid cannot Save.
3. columnMeta omitted — generateMutationPlan gets columnDataTypes but not columnMeta, so generated / AUTO_INCREMENT INSERT columns are not omitted (Table Browser does).

Scope

• Reuse loadTableViewSchema (or equivalent) and surface schema errors in the SQL status line.
• Apply sqliteTableBrowserPrimaryKeys + project rowid when needed (or document that SQL-grid Save requires rowid in the SELECT).
• Pass columnMetaFromSchema into SQL-grid mutation plans.

Out of scope

• Execute discarding dirty edits (separate issue).