"No BigQuery datasets configured" toast on every page load, despite `datasets:` being set in connection.yaml

Summary

With a working BigQuery direct connection, evidence dev shows a persistent error toast on every page load:

No BigQuery datasets configured Add at least one dataset to your warehouse settings to enable schema introspection.

The datasets: allowlist is set in connection.yaml, and every query on the page runs correctly against BigQuery. The toast is created with duration: Infinity, so it never dismisses on its own and returns on each refresh.

Environment

• Evidence CLI v0.9.3 (latest)
• macOS 15.6 / arm64
• BigQuery direct connector via local connection.yaml, not logged in to Studio

Steps to reproduce

type: bigquery
project: my-project
keyfile: ./sa-key.json
location: EU
dataset: my_dataset
datasets:
  - my_dataset

evidence dev

Open any page. Data loads correctly; the toast appears bottom-right and stays.

What I ruled out

• Not a key-name problem. Adding schemas: [my_dataset] alongside datasets: and restarting produces the identical toast.
• Not a credentials problem. evidence query "select ..." returns rows, and all page components render live BigQuery data.
• Not a general introspection failure. evidence describe <table> returns the full column list, so the INFORMATION_SCHEMA.COLUMNS path works.

Cause

The toast is raised by a guard on an empty dataset list:

if (this.#P.length === 0) {
  ev.error("No BigQuery datasets configured", {
    description: "Add at least one dataset to your warehouse settings to enable schema introspection.",
    duration: 1/0
  })

That list is used just below to build the per-dataset INFORMATION_SCHEMA.COLUMNS query, so it is meant to be the configured allowlist — but it arrives empty when the connection comes from a local connection.yaml rather than Studio warehouse settings. The message text ("your warehouse settings") also suggests this path assumes a logged-in Studio connector.

Expected

With datasets: present in connection.yaml, the dev server should populate the list from it and not warn. If a local direct connection genuinely cannot support the schema browser, the toast should at least be dismissible / non-repeating rather than duration: Infinity.

Impact

Cosmetic but constant — it covers part of the viewport on every page load during development, and it is misleading because it points at configuration that is already correct.