test(e2e): add the CI image pull rows, blocked (monolith/S16 plan: 2/6)

Summary

  • Problem: monolith/S16's criteria 7 and 8 name two e2e scenarios, and the Docker catalog has no rows for them.
  • Impact: none for users; the catalog lists the two journeys before they ship.
  • Change: adds e2e.docker.auth.ci-image-pull and e2e.docker.auth.ci-image-pull-denied to the Docker catalog's Authentication section, both blocked and not started, with the section intro naming the blocker: the harness's job claim reports no executor, and the harness does not enable the ci_artifact_registry_pull_credentials flag. The rig's monolith already issues the payload credential from Step 1 (gitlab-org/gitlab!268444 (merged)). Step 2 of the monolith/S16 plan. The glee scenario-id constants are regenerated.
  • Downsides: none; Step 3 flips both rows to automatable and implemented.

Plan and spec amendments

  • monolith/S16 plan, Step 2: the section intro names the harness as the blocker, not Step 1 in the rig's monolith.

Checklist

  • Ran it: n/a, catalog rows only. glee catalog generate --check and glee check pass; both rows are listed under "No scenario yet".
  • Interfaces and data: none.
  • Failure: n/a.
  • Rollout: n/a.
  • Hot path: no.
  • Database: no.
  • Security: no.
  • ADRs: none govern catalog rows.
  • E2E: adds the two rows above, blocked until the harness work in Step 3, per Writing a row.
  • Simplicity: the rows land now, as the plan's Step 2, so Step 3 changes only their state.

Related to #1863 (closed)

🤖 Generated with Claude Code

Edited by Daniel Prause

Merge request reports

Loading
Loading