Gate & report Shipped
Two capabilities end in a machine-readable readiness verdict. A plain quality review deliberately does not.
Not every review has a verdict
This is a distinction worth being precise about. review conformance and review finish declare a gate, and end by writing a merge-readiness file: ready or not, with the reasons. A plain review code declares no gate at all — it ends at the report, because "is this branch mergeable" is a different question from "what is wrong with this code," and answering the second does not entitle you to answer the first.
Which capabilities gate
| Declares a gate | Writes merge-readiness | Ends at a report | |
|---|---|---|---|
| myteams devteam review code | no | no | yes |
| myteams devteam review conformance | yes | yes | yes |
| myteams devteam review finish | yes | yes | yes |
One gate implementation, two capabilities
Both conformance and finish-review use the same gate module, with case-insensitive field matching, so the two cannot drift apart. That matters because the gate is the thing the build loop trusts to decide whether an increment moved forward.