[BUG] `dbt show -s some_data_test` does not display the result

[dbeatty10]

Describe the bug
I'll circle back later to fill this out.

Example from docs for dbt show:

$ dbt show -s "unique_my_model_with_duplicates_id"
13:22:53 Running with dbt=1.5.0
13:22:53 Found 4 models, 2 tests, 0 snapshots, 0 analyses, 309 macros, 0 operations, 0 seed files, 0 sources, 0 exposures, 0 metrics, 0 groups
13:22:53
13:22:53 Concurrency: 5 threads (target='dev')
13:22:53
13:22:53 Previewing node 'unique_my_model_with_duplicates_id':
| unique_field | n_records |
| ------------ | --------- |
|            1 |         2 |

What version of dbt Fusion is this bug in? (find out by running dbt --version)

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

• YES
• NO

To Reproduce

1. Open this workspace
2. Follow the instructions in the README

Expected behavior

$ dbt show --select not_null_my_model_id

[0m02:08:02  Running with dbt=1.10.9
[0m02:08:02  Registered adapter: snowflake=1.10.0
[0m02:08:02  Found 1 model, 3 data tests, 477 macros
[0m02:08:02  
[0m02:08:02  Concurrency: 4 threads (target='snowflake')
[0m02:08:02  
Previewing node 'not_null_my_model_id':
| ID |
| -- |

Actual behavior

$ dbt show --select not_null_my_model_id

error: dbt1007: Either --select or --inline must be specified

dbt-fusion 2.0.0-preview.7
   Loading profiles.yml
  Finished 'show'  with 1 error in 236ms

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

• Mac/Windows/Linux?
• X86 or ARM?

[fa-assistant]

🧹 Stale Issue Detected

This issue has had no meaningful activity for 174 days.

If this is still relevant, please:

• Comment with an update, or
• Add the cleanup/keep label to exempt it from future cleanup scans.

If no action is taken within 30 days, this issue will be scheduled for auto-close with a 7-day grace period.

---

This notice was posted by the Fusion Issue Cleanup workflow.

[fa-assistant]

🧹 Possible Duplicate Detected

This issue appears to be a potential duplicate of dbt-fusion#669.

If this is indeed a duplicate, consider closing one. If not, no action is needed — this notice is informational only.

---

This notice was posted by the Fusion Issue Cleanup workflow.

[fa-assistant]

🧹 Possible Duplicate Detected

This issue appears to be a potential duplicate of dbt-fusion#669.

If this is indeed a duplicate, consider closing one. If not, no action is needed — this notice is informational only.

---

This notice was posted by the Fusion Issue Cleanup workflow.

[fa-assistant]

🧹 Possible Duplicate Detected

This issue appears to be a potential duplicate of dbt-fusion#669.

If this is indeed a duplicate, consider closing one. If not, no action is needed — this notice is informational only.

---

This notice was posted by the Fusion Issue Cleanup workflow.

[fa-assistant]

🧹 Possible Duplicate Detected

This issue appears to be a potential duplicate of dbt-fusion#669.

If this is indeed a duplicate, consider closing one. If not, no action is needed — this notice is informational only.

---

This notice was posted by the Fusion Issue Cleanup workflow.

[fa-assistant]

🧹 Possible Duplicate Detected

This issue appears to be a potential duplicate of dbt-fusion#669.

If this is indeed a duplicate, consider closing one. If not, no action is needed — this notice is informational only.

---

This notice was posted by the Fusion Issue Cleanup workflow.

[fa-assistant]

🧹 Possible Duplicate Detected

This issue appears to be a potential duplicate of dbt-fusion#669.

If this is indeed a duplicate, consider closing one. If not, no action is needed — this notice is informational only.

---

This notice was posted by the Fusion Issue Cleanup workflow.

[fa-assistant]

🧹 Possible Duplicate Detected

This issue appears to be a potential duplicate of dbt-fusion#669.

If this is indeed a duplicate, consider closing one. If not, no action is needed — this notice is informational only.

---

This notice was posted by the Fusion Issue Cleanup workflow.