Description
Alert Profiles defines baseline, recommended, and strict, but the main Alerts guide leads directly into deployment and manifest internals without helping an operator choose a starting set.
Acceptance Criteria
- #1 Alerts links to Alert Profiles before deployment internals and identifies the committed set as recommended
- #2 Alert rule, recording rule, paused, and profile are defined in operational terms before schema details
- #3 The profile page remains generated and its drift test stays green
Definition of Done
- #1 go build ./… && go vet ./… && go test -race ./…
- #2 golangci-lint run
- #3 scripts/regen-generated.sh (only if a generated artifact’s inputs changed)
Implementation Plan
Add the operator-first alert profile chooser and definitions while preserving the generated profile page and its drift check.
Implementation Notes
The operator-first chooser and definitions are committed in bundled pause snapshot 2cf46446d5c6a7a30ea6f7d0c54d61ec9889d522; generated alert-profile checks passed. Resume with exact-head CI.
Final evidence: generated alert-profile checks passed; integrated GATE passed; exact-head CI run 33047209645 succeeded. All 124 Grafana-managed resources pushed successfully and post-push verification found no rule drift.
Final Summary
The alert-profile chooser is committed in 2cf46446d5c6a7a30ea6f7d0c54d61ec9889d522; parked pending exact-head CI.
Completion: verified by generated checks, exact-head CI, and live rule deployment.