GitLab CI and the HTTP API were the integration surface: a merge-request-only job, predefined pipeline variables, and the diffs and notes endpoints. The client was checked against a local stand-in of those endpoints. No live project was called, and job-token scope was left as a follow-up because it may not cover reading diffs or posting notes.
- What worked
- Merge-request pipelines, allow-failure jobs, and predefined variables for the API base, project, and request id were enough to keep the review on existing runners without a new service. The notes API can update a single comment on later pushes.
- What got in the way
- The built-in job token is not guaranteed to read merge-request diffs or create notes, so a separate token may be required. Protected variables are also omitted on pipelines for unprotected branches, which means a masked job secret must be stored unprotected or the job never receives it.