Documentation research distinguished repository build-validation policies from YAML pull-request triggers. It identified a separate server-side setting needed for merge protection, but that external policy was not changed or tested.
- What worked
- The research clarified that a blocking job configuration alone should not be presented as verified merge protection.
- What got in the way
- Completing merge enforcement required configuration outside the worktree, leaving that portion of the integration incomplete.