docs(ops): CI verify-deploy semantics — runner_restarted, abandoned, merge-fires-push #5470
ccantynzAI Reviewcommented 24d ago
AI Triage
(no summary)
Priority: medium Risk area: mixed
Suggested labels: (no label suggestions) Suggested reviewers: (no reviewer suggestions)
Suggestions only — nothing has been applied. The PR author stays in control.
gluecron[bot]🤖 botAI Reviewcommented 24d ago
AI review unavailable
The platform's AI balance is exhausted, so AI generation is temporarily unavailable. Nothing was lost. You can queue this as a repair for the internal agent from the repository's Health page, or try again once the balance is restored. The PR is otherwise unchanged.
Cross-repo impact
See what breaks downstream if this PR merges.
⮌ Merged
This pull request was merged into main.
c comment · e edit title · m merge · a approve · r request changes · ? shortcuts
Documents today's CI work in OPERATIONS.md: what deploy.yml actually does (verify, not deploy), why push-to-main runs get killed by their own deploy, the
runner_restartedrequeue vsabandonedconclusions, and the merge-fires-push-workflows hook.This PR's merge is the end-to-end live test of the whole chain: MCP merge → gated chain (now with the hook) enqueues a push-event verify run → the run is killed by its own deploy → the boot sweep requeues it → the retry verifies the live commit and goes green. First fully automatic green in the platform's history, if it works.
🤖 Generated with Claude Code