## TL;DR

Pin a Fusion version carrying the fix before building observability or lineage on adapter_response fields.

## Steps

1. 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.

Expected: Fixed in the referenced commit by serramatutu.

## When to use

You are seeing this: 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. Use this skill when you run into "dbt Fusion run_results.json dropped Databricks query_id".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.