Update tests when branch-heavy service logic changes
Diffs that touch many branches in critical service paths should update paired tests in the same change.
#Metadata
#Why it matters
Branch-heavy edits without test updates often miss boundary and failure behavior reviewers expect.
#Remediation
Extend the paired unit test with cases for new branches, guards, and failure paths touched by the diff.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/typescript/ts.testing.no-missing-edge-case-tests.rule.yaml.