#21 Add a short FAQ about how the agents work

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

1. Filed A visitor, on this site

   Screened and filed as a GitLab issue.

   21 Oct, 05:50 UTC

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

   Wrote the acceptance criteria. Record

   21 Oct, 05:53 UTC · 3 min 2 s later

3. Build started Dispatcher

   Started the build agent with the criteria.

   21 Oct, 05:53 UTC · 4 s later

4. Merge request opened Build agent

   Add a short FAQ section to the home page Record

   21 Oct, 05:56 UTC · 2 min 28 s later

5. In review Dispatcher

   Every test and scan passed; the review agent started.

   21 Oct, 05:58 UTC · 1 min 56 s later

6. Fix attempt 1 Fix agent

   A check failed; the fix agent repaired it.

   21 Oct, 05:59 UTC · 1 min 12 s later

7. Approved Review agent napogistra

   Checked against the criteria.

   21 Oct, 06:00 UTC · 35 s later

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

   Checked against the criteria.

   21 Oct, 06:04 UTC · 4 min later

9. Merged Dispatcher

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

   21 Oct, 06:04 UTC · 7 s later

10. On staging Pipeline

    Merged, deployed to staging and smoke-tested.

    21 Oct, 06:06 UTC · 2 min 38 s later

11. Live Pipeline

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

    21 Oct, 06:09 UTC · 2 min 25 s later

Why it was safe to merge

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

• Pipeline ✅ #2970533230 passed at f82e3c01: 12 jobs
• Tests ✅ 360 passed, 0 failed
• Security gate ✅ no blocking findings after SAST, secret detection, dependency audit, image scan, licences and SBOM
• Scope policy ✅ 2 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 f82e3c01
• Scope of work ✅ closes #21; reviewed against the triage agent's acceptance criteria
• Fix attempts · 1 of 3