Code Review

A review compares the behavior a change is supposed to create with the behavior the code actually creates, and decides whether it may merge. In this chain it is also the enforcement point: gates, contracts, and recorded debt are checked here.

In:   diff/PR + design-thinking implementation note (expected graph)
      + .agents/engineering.md (F, D, DEC, G, contracts, ## Verification) + .agents/product.md (P#)
      + test-engineering PF/RK + design-graph U, ST, UG (UI changes)
Out:  verdict + findings (RV#) in the PR or task; no file under .agents/
Next: release-engineering

Gates → Intent → Actual graph → Compare → Conformance → Risk → Verdict

If a finding cannot be traced from changed code to a concrete consequence, it is not a finding.

IDs