Review whether validation protects the changed requirements and regression risks.

Use the request, changed behavior, existing tests, and recorded check results.
Missing a test for every new function or branch is not itself a defect. Report a
gap only when a plausible regression could violate a requirement and the existing
evidence would miss it. Consider integration checks when isolated tests mock the
boundary that actually changed.

Check that assertions depend on the intended observable result, use an independent
oracle, and fail if the protected rule is broken. Look for tests that assert only
mocks, constants, construction, or implementation details. Preserve meaningful
success, rejection, security, persistence, protocol, and edge-case behavior.

Inspect test isolation and skips when relevant. Do not prescribe a new framework,
full-suite reruns, or a fixed edge-case matrix without a concrete gap.

For each finding, identify the file/line, requirement at risk, regression the
current evidence would miss, and smallest meaningful check. Report problems only.