Phase 7: AI-assisted query authoring (autocomplete, explain, fix, optimize, NL translation)

Adds a self-hosted (Ollama, qwen2.5-coder) model provider abstraction with a pluggable opt-in cloud adapter, schema grounding, and a shared cost/safety guard every AI-suggested query is assessed against -- compiling to and executing through the same unchanged Phase 2 IR/ compiler and Phase 4 tenant scoping as a hand-written query, no parallel execution path. Track A (built into the query bar): inline ghost-text autocomplete, "Explain this query", "Fix this query" with a diff view, and a rule-based "Optimize" suggestion. Track B: natural-language-to-query translation, always a separate review step from execution, with `sentryctl query --nl` requiring explicit confirmation to run. Every accepted/dismissed translate-fix-optimize interaction is logged into the same append-only audit_log table Phase 4 built. Two real product bugs were found and fixed via live browser verification (a Svelte effect re-running on every keystroke that silently cancelled the ghost-text debounce; a ghost-text widget positioned at document offset 0 instead of the cursor), and a real costguard logic bug (unbounded-aggregation vs. raw-row) was caught by its own test suite. New integration tests wire a real Ollama client through the real HTTP handler against a mock server matching Ollama's wire contract (hack/mock-ollama), keeping model-quality verification out of CI as a disclosed, periodic human-run check instead. See /docs/phase-7-ai-design.md and /docs/phase-7-runbook.md.
2026-08-16 18:06:27 -07:00
parent 661568085e
commit 7d316f92db
37 changed files with 5230 additions and 20 deletions
@@ -0,0 +1,14 @@
+-- Phase 7 task 12: AI-assisted interactions (translate/fix/optimize
+-- accept-or-dismiss decisions) are audited through the *same*
+-- append-only, hash-chained audit_log table Phase 4 built -- not a new
+-- table -- since audit_log's detail JSONB column and event_type
+-- discriminator were already designed to carry event shapes other than
+-- "query" (role_change/grant_change/etc. already don't populate
+-- row_count/duration_ms, relying on detail instead; ai_interaction is
+-- the same shape of extension). Postgres has no ALTER CHECK, so drop
+-- and recreate, same pattern as 0035_add_heatmap_viz_type.sql.
+ALTER TABLE audit_log DROP CONSTRAINT audit_log_event_type_check;
+
+ALTER TABLE audit_log
+    ADD CONSTRAINT audit_log_event_type_check
+    CHECK (event_type IN ('query', 'role_change', 'grant_change', 'sso_config_change', 'secret_reveal', 'ai_interaction'));