[Bug] saved queries are always selected as "modified", they should not be

[graciegoheen]

Is this a new bug in dbt-core?

• I believe this is a new bug in dbt-core
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Saved queries are always selected as "modified"

Expected Behavior

Saved queries should only be selected as "modified" when they have been modified

Relevant log output

No response

Environment

- OS:
- Python:
- dbt:

Which database adapter are you using with dbt?

No response

Additional Context

No response

[graciegoheen]

Potentially related to -> #9548

[tlento]

A community member is reporting the exact opposite behavior - saved queries do not show up in state:modified or state:new even when they should. Here's the repro step sequence they provided in the linked Slack thread:

Steps used for testing:

1. Upgrade existing projects to dbt v1.8
2. Run dbt parse for project containing semantic models
3. Rename target to old-target
4. Edit semantic model (edit existing saved query, add new saved query)
5. Make edits to SQL model as a control for the test
6. Run dbt parse again
7. Run dbt ls -s "state:modified state:new" --target old-target

Result: no semantic model changes detected, SQL model change detected as expected.