Help & runbooks

Enablement flow

1. Access — confirm job-token allowlist on devops/ci-ai-toolkit (Sentinel does this on Apply when you have Maintainer there).
2. Variables — Bedrock / LLM keys and GITLAB_TOKEN must be readable on MR pipelines (usually unprotected).
3. Modules — pick a preset, review the live ci/ai-toolkit.yml preview.
4. Apply — opens a Draft MR on feature/enable-ci-ai-toolkit.
5. Verify — wait for AI jobs on the MR pipeline (not only “MR created”).

Common failures

• Component permissions error — consumer not on the toolkit allowlist. Re-run Apply, or use Variables → Allowlist.
• Pipeline with 0 jobs — YAML failed to compose (same root cause as above, or missing AI stages).
• No ai_* jobs on branch push — many modules are MR-only. Open the Draft MR pipeline.
• Soft-skipped AI jobs — missing clone token / Bedrock vars.

Docs

• Consumer integration guide — Pattern A (component) vs Pattern B (local jobs)
• Bedrock setup
• Enablement dashboard — portfolio posture & scorecards
• Repositories — start a new enablement

Audit tip

Enablement history lives in GitLab: search MRs titled enable the CI AI Toolkit or source branch feature/enable-ci-ai-toolkit. The dashboard lists pending and merged enablements it can see with your token.