[BUG] Named exposure selector returns "nothing to do" in Fusion

[faithebear]

Describe the bug
A clear and concise description of what the bug is.
Account: 26712 | Project ID: 437779 | Branch: fusion_fixes_branch
Issue:
dbt run --select +exposure:orders_data returns "nothing to do", while these work correctly: - dbt run --select +exposure:*

• dbt run --select +exposure:customers_data

What version of dbt Fusion is this bug in? (find out by running dbt --version)
Fusion Version: 2.0.0-preview.120

Is this a discrepancy between the dbt Fusion Engine and dbt Core? Check one.

• YES
• [ x] NO

To Reproduce
Please submit one of the following

• A minimal YML snippet which reproduces the behavior
• A minimal dbt project which reproduces the behavior
• A description so detailed that the issue can be easily reproduced

What we confirmed:
dbt ls --select +exposure:orders_data completes parsing and scheduling successfully but schedules zero nodes — the exposure exists in the graph but the named selector silently returns empty

Removing metric() references from orders_data does not fix the issue
The exposure YAML is valid and both exposures are defined in the same file
customers_data (the second exposure in the file) selects fine; orders_data (the first) does not
Likely cause: A bug in Fusion's named exposure: selector during the scheduling phase — it resolves the node during parsing but fails to match it by name when scheduling.

Expected behavior
A clear and concise description of what you expected to happen.
dbt run --select +exposure:orders_data should run the models associated with my exposure.

Screenshots
If applicable, add screenshots to help explain your problem.

Operating System and CPU Type (please complete the following information):

• Mac

[faithebear]

Went to make a video to repro + the issue has disappeared.