You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Canary confirm: agent-shield ring1->stable — human go/no-go before stable #1520
Canary rollout — human confirmation requested (ring1->stable).
The release gate holds agent-shield in AWAITING_CONFIRMATION: reliability has PASSED (dwell + sample + cumulative health all clean), but this transition is flagged require_confirmation (#668 Layer 3), so a human confirms the candidate is behaving correctly — not merely exiting green — before it reaches the stable tier (all consumers). Filed + maintained by the Canary Rollout workflow; regenerated each run and auto-closes when the promotion is confirmed or the candidate changes — do not edit by hand.
Skim the changed reusable logic and the recent green runs on the ring1 tier before confirming.
Confirm or hold
Go: dispatch the Canary Rollout workflow → command promote, agent agent-shield, confirm = true (or run promote agent-shield --confirm locally). --confirm advances ONLY this reliability-clean state; it is not--override and cannot bypass a failing gate.
No-go: if the candidate looks wrong, roll back instead of confirming (rollback agent-shield <ring> --to <prior release>).
Whole-fleet status is in the Canary Rollout workflow run's job summary (Actions → Canary Rollout → latest run → Summary).
Activity