[BUG] `state:modified` false negative when unit test definition changes

[dataders]

Description

When running dbt build --select state:modified with deferral, changes to a unit test are not detected as modified. The associated SQL model runs (if its columns changed), but the unit test node itself is not selected.

Steps to Reproduce

1. Do a full build and save the manifest as the deferred state
2. Change a unit test definition and a SQL model column
3. Run dbt build --select state:modified with deferral to the saved manifest
4. Observe: the SQL model runs, but the unit test does not run

Expected Behavior

The unit test node should be selected as state:modified and run.

Actual Behavior

The unit test node is not selected — it is treated as unmodified even though its definition changed.

[mikaylacrawford]

Thanks for filing Anders! Here's the specific commit on my test project for reproducing: https://github.com/dbt-labs/orc-jaffle-shop/pull/15/changes/c1ff8959829b7756f171baa5dc23f38d2dd1d080

[milevin]

No repro: https://github.com/dbt-labs/fs/pull/8762

If you still see this issue, please add a repro project as a zip file + fusion command to run