[codex] Guardrail candidate: Release train drift (release-train-drift)

[haasonsaas]

Release train drift

This issue routes a recurring review-feedback class to the repo that needs the prevention guardrail.

• Repo: evalops/maestro
• Class: release-train-drift
• Repo findings: 1
• Class findings: 2
• Generated at: 2026-05-26T01:18:32Z
• Window: merged since 2026-05-23 with minimum severity high
• Org tracker: [codex] Guardrail backlog: Release train drift (release-train-drift) .github#71

Guardrail to build

Add release metadata and changelog coverage checks tied to the package or deploy artifact that changed.

Representative feedback in this repo

• p1 chore: sync public mirror from internal #601 top-level feedback
  • Treat unguarded Rust test modules as package-impacting
  • chore: sync public mirror from internal #601 (comment)

Finding fingerprints

• 68dcb3a9672d384a60f3bf1a2639ebc1909c129982e3eb905db55dd0dea4679a

Acceptance criteria

• A repo-local guardrail fails for at least one representative feedback shape listed above.
• The guardrail is wired into the smallest relevant CI, preflight, or test target in this repo.
• The issue is closed only after the guardrail merges and the feedback sentinel reports this repo/class fingerprint set as already closed or absent.