Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,16 @@ Status: in development.
- [x] CI, release pipeline, SBOM, provenance
- [x] Verification against a live Azure Databricks workspace
- [x] CLI output tests across terminal widths, unicode, nulls and escape-sequence injection
- [ ] Live coverage for `chat`, chunked results and `QUERY_RESULT_EXPIRED` recovery
- [ ] Live coverage for three paths that resist automation — each blocked for a different reason,
recorded here rather than left as one vague gap:
- `chat` — the REPL refuses to start without an interactive terminal, by design, so it cannot be
driven from CI or an agent session. Its underlying follow-up call *is* covered live; the loop
around it is not. Needs a human at a terminal.
- Chunked results — Genie writes its own SQL and generally bounds it, so producing a result large
enough to span chunks is not reliably reachable through the Conversation API. Covered by
contract tests against a stubbed multi-chunk response.
- `QUERY_RESULT_EXPIRED` recovery — the cache expires on Databricks' schedule, hours later. No
way to force it; covered by contract tests only.
- [x] Command reference and authentication guide

## v0.2 — automation
Expand Down
10 changes: 10 additions & 0 deletions docs/compatibility.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,3 +81,13 @@ contract tests only.
Add a row when you run something, naming what you ran it against. Remove a row if the evidence
stops being true. An entry with no evidence behind it is worse than a missing entry, because it
gets believed.

## Live run — 2026-08-01, second pass

Re-run of the full live suite (8 tests) against the same Azure Databricks workspace after the
Agent-resolution change that fetches an id directly instead of paging the listing. All 8 passed,
which is the point of re-running it: that change alters how every `ask`, `chat` and `pack run`
finds its Agent, and a contract test cannot tell you whether a real workspace agrees.

Still not exercised live, with the reason each resists it, are the three paths listed under v0.1 in
[ROADMAP.md](../ROADMAP.md).
Loading