Review behavior and scope
Compare the result with the user’s requirement and note any part that remains unsupported or out of scope. Trace affected call sites, routes, translations, configuration, and documentation where relevant.
Look for unintended side effects such as changed defaults, weakened validation, missing error handling, or duplicated content. Consider how existing consumers behave when fields are absent or values differ.
Verify the handoff evidence
Run checks that cover the changed area when appropriate and read their output. A passing type check does not prove the user-facing behavior, while a manual review alone may miss a syntax or build issue.
Summarize what changed, what was checked, and any limitation that affects use. If a concern remains, identify it precisely instead of implying the entire project was audited.