[kvlonge]

Why

Selected planning and build commands restrict deep SQL analysis to their model scope, but configured rules were evaluated against the entire project. Unselected models could therefore produce false semantic or contract findings because their deep-analysis facts were intentionally absent.

Changes

• resolve configured-rule subjects from the same selection policy used for deep SQL analysis;
• preserve full-project rule evaluation when no selector is provided or Python-node resolution requires complete analysis;
• add real CLI planning coverage for a typed unselected model;
• retain focused/full rule-cache and project-rule boundary coverage.

Verification

• 51 focused rule and compile-pipeline tests;
• make check-ci;
• make test;
• selected real-project planning reproduction with configured rules;
• independent read-only review;
• public-repository hygiene scan.