test-ops

To determine the minimal Taskfile verification entry, classify repository changes into static, logic, contract, workflow, or performance categories using docs/test_strategy.md to select the appropriate validation path beyond basic unit tests.

Selecting a Taskfile check for frontend and backend changes involves classifying the modified entry points against your test strategy documentation to identify the most efficient verification path and exclude unnecessary heavy testing workflows.

You need a verification path beyond basic unit tests when repository changes involve logic, contract, workflow, or performance modifications that require targeted validation entries defined in your Taskfile.yml and test strategy documentation.

Code change classification maps to Taskfile entries by evaluating frontend and backend modifications against known entry points and test strategy categories, returning the chosen entry, selection rationale, and intentionally omitted items.

Yes, using test_strategy.md to classify changes allows you to skip unnecessary Taskfile verification steps by matching change types to minimal validation entries and intentionally excluding heavy paths when they are not required.