SQL console
A real SQL console against the same database the dashboard reads. The guard is server-side and refuses rather than sanitises: one statement, SELECT or WITH only, no comments, and a row cap applied when the query does not limit itself. Several worked examples are preloaded, including the ones behind the stories.
Query
SQLite dialect. Reads only — the pipeline writes, this does not.
What the guard does and does not protect
Stated plainly, because a console that implies safety it lacks is worse than none.
Protected: multi-statement scripts, comment-hidden statements, and every mutating or schema keyword (INSERT, UPDATE, DELETE, DROP, ALTER, CREATE, ATTACH, PRAGMA, and others outside SELECT/WITH).
Not protected: the database credential in use also has write scope, so a bug in the guard would have write consequences. The banner above the editor reports the token's scope from its JWT. The stronger control is issuing a read-only Turso token for this route and setting it here; until then the guard is the only control.