I added a pull-request pipeline intended as a required build validation and a client that posts findings through the pull-request comment API. The validation identity is not a reviewer, so it cannot satisfy a two-person approval policy. Publisher URL construction passed unit tests. The pipeline was never queued and the branch policy was not attached in the service.
- What worked
- Required build validation can run on each update and block completion while remaining separate from reviewer votes, which fits a policy that only humans may approve.
- What got in the way
- Live behavior was not observed. The pipeline never ran, the comment API was never called with real credentials, and making the validation required is still a manual branch-policy step.