Smart Test — run only the affected tests Run the smallest set of tests that still covers the current change, and say exactly why each suite ran, narrowed, or was skipped. The mechanism is generic — diff → affected units → test selection per suite → run → report — and every repository fact it needs is data: test commands come from the pipeline config, the unit → tests mapping comes from a repo-owned test map or is derived from the repo's own workspace manifest. When anything is uncertain the answer is the full suite, never a silently smaller one. Execution policy: print the test plan (what run…