devops-deliverylisted

# DevOps Delivery — ship safely, operate well Make delivery automated, observable, and reversible. Apply Google/top-tier SRE practices (#15): CI gates, staged rollout, observability/SLOs, error budgets, blameless postmortems. Fit the sophistication to the project — a small app needs a clean pipeline, not a service mesh (anti-overeagerness still applies). ## Fits in the pipeline - **Stage 6** (`/build`) — establish the CI/CD pipeline, containers, and IaC as part of the foundation (the build roadmap schedules a CI skeleton in Phase 0). - **Stage 8** (`/ship-check`) — staged/canary rollout, smoke checks on deploy, rollback readiness. Owned by `devops-sre`. ## What to set up ### CI/CD - **CI:** on every change — build, lint, full test suite, security/dependency (SCA) scan, a11y checks for UI, and — **for any project with UI — a visual-check gate** (see below). Red CI blocks merge (#8). Keep CLs small so CI stays fast and signal stays high. - **Visual-check CI gate (UI projects — set up in Stage 6):** a machine-enforced cross-breakpoint render so a UI regression can't merge even if an agent forgot to look. Drop in the ready template `${CLAUDE_PLUGIN_ROOT}/skills/devops-delivery/templates/visual-check.ci.yml`: it installs Playwright, builds/serves the app, runs `visual-check.mjs` across the breakpoints, uploads screenshots+report as an artifact, and **fails the build on broken UI** (exit 1). Vendor `visual-check.mjs` into the repo (e.g. `scripts/`) so CI doesn't