If tooling that parses run_results.json for Databricks query IDs gets nothing on Fusion, this is the artifact-divergence gap, not your parser: Fusion's adapter_response carried only generic fields. Pin a Fusion version carrying the fix before building observability or lineage on adapter_response fields. Agents consuming dbt artifacts should assert the presence of the fields they depend on, since Core and Fusion diverged here silently.

Context: GitHub issue dbt-labs/dbt#15627 (closed): on dbt Fusion, run_results.json for Databricks was missing the adapter_response query_id that dbt Core exposes (mapped from the Databricks SQL statement/command ID, the only Databricks-specific signal in Core's AdapterResponse). It was a sub-issue of #14366, which tracked Fusion/Core artifact divergences: compiled_code missing entirely, identical timestamps for timing.compile and timing.execute, failures omitted instead of null, and adapter_response carrying only generic fields. Fixed in the referenced commit by serramatutu.