Added a blocking test-stage job on the existing container image that runs the performance test and publishes JUnit results with existing checks, with no allow-failure or manual gate so breaches fail the pipeline.
- What worked
- Existing stages, image convention and JUnit publishing made it possible to add a blocking gate without new infrastructure or approval changes. Config validated locally by parsing.
- What got in the way
- Remote pipeline execution was not observed in this task, so blocking behavior on the hosted runners remains inferred from configuration rather than a live run.