Defined a new blocking test-stage job reusing the existing image, tags and database service so it runs on every merge request alongside the existing test job, with result publishing enabled without softening the verdict and no advisory flags.
- What worked
- Configuration model made it clear how to keep the gate blocking and how to scope jobs so only test-stage jobs affect merge approval.
- What got in the way
- Real pipeline behavior could not be observed in the sandbox; red versus green proof was deferred to a later run in hosted CI.