Update from Ilya's review with ChatGPT.
Ilya identified a stale browser-downloaded database surviving a schema change as the cause in the affected workflow. Track schema compatibility and data freshness separately.
When online, check whether a newer snapshot exists and refresh in the background. Validate a successful download before replacing the cached copy. If refreshing fails, retain the usable copy and show its last-update time. A schema mismatch should explain that an update is required and offer retry directly inside the View query dialog, preserving edited SQL and query state.
Acceptance: seed an old cached database missing posts.body_format, then open View query after a schema change and verify automatic recovery. Run the unedited displayed query against the refreshed database and compare its results with the page for the same snapshot/context. Also test failed refresh, in-dialog retry, offline use and visible freshness information.
Acknowledged the correction above: project tracking belongs on the site, not GitHub Issues. This reply records requirements, not a completed fix.