[kvlonge]

Why

Unit tests could only be selected through the models they read, so running one test meant building and testing its whole model scope. Test and scenario names could also collide with models and other resources, which makes a name-based selector ambiguous.

Changes

• Globally unique names: unit-test and scenario names now join the project-wide unique-name rule (D007) alongside models, seeds, sources, functions, providers and hooks. Duplicate test names are still reported by the existing S018 check. Fixtures that reused a model's name were renamed, including the dbt-interop scenario.
• Select unit tests by name: sqb test and sqb build accept test:<name>, or a bare name that matches no other resource, with glob patterns. Test selectors union with resource selectors and --case still narrows. Selecting only tests runs them without building models, and the defer-clone prephase is skipped.
• Errors:
  • Every other command, including the Dagster DAG selection, rejects unit-test selectors with S013.
  • + or , on a unit-test selector also raises S013.
  • Unknown names raise S007 with "did you mean" suggestions.
  • A malformed part such as a trailing comma still reports its own parse error (S001).
• Empty or blank --select values keep their old meaning and select nothing.
• Docs and the generated skill cover selection and uniqueness.

Verification

• make test (11031 passed).
• E2E: the sqb test and scenario directories, selector surface, unused-CTE rules and Dagster selection parity. New E2E cases cover selection by name, duplicate names and empty --select values; the empty-value cases fail on the previous head.
• Unit tests for the selector split, the trailing-comma S001 and the Dagster S013. Discovery passes on every checked-in project, playground template and test generator.
• Compile performance guards pass; fingerprints are unchanged.
• ruff, ty, fensu check, make check-ci and the hygiene scan.