#13 Prevent a repeat of incident #12: add a regression test

Every step from GitLab's own records: the issue, its merge request and their label history.

1. Filed The dispatcher, after an incident

   Screened and filed as a GitLab issue.

   19 Oct, 07:00 UTC

2. Triage accepted Triage agent ai-shipyard-triage-gitlab-ai-hackathon

   Wrote the acceptance criteria. Record

   19 Oct, 07:01 UTC · 1 min 12 s later

3. Build started Dispatcher

   Started the build agent with the criteria.

   19 Oct, 07:01 UTC · 1 s later

4. Merge request opened Build agent

   Add regression tests for non-ASCII request titles Record

   19 Oct, 07:03 UTC · 1 min 54 s later

5. In review Dispatcher

   Every test and scan passed; the review agent started.

   19 Oct, 07:06 UTC · 3 min 31 s later

6. Approved Review agent ai-shipyard-review-gitlab-ai-hackathon

   Checked against the criteria.

   19 Oct, 07:07 UTC · 56 s later

7. Merged Dispatcher

   Merged at the reviewed commit, with a release decision record. Record

   19 Oct, 07:07 UTC · 6 s later

8. On staging Pipeline

   Merged, deployed to staging and smoke-tested.

   19 Oct, 07:18 UTC · 10 min later

9. Live Pipeline

   Passed a canary and a 60-second watch in production.

   19 Oct, 07:21 UTC · 2 min 44 s later

Why it was safe to merge

What the dispatcher verified before merging, from its release decision record (open it).

• Pipeline ✅ #2961936013 passed at 0f8392bf: 13 jobs
• Tests ✅ 215 passed, 0 failed
• Security gate ✅ no blocking findings after SAST, secret detection, dependency audit, image scan, licences and SBOM
• Scope policy ✅ 1 files changed, all inside the agent scope
• Authority boundary ✅ protected policy tests passed
• Review ✅ review::approved added by ai-shipyard-review-gitlab-ai-hackathon (the review flow's own account), verified in GitLab's label history
• GitLab approval ✅ approval rule satisfied at 0f8392bf
• Scope of work ✅ closes #13; reviewed against the triage agent's acceptance criteria
• Fix attempts · none needed