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
fix(ci): run the cross-plugin source drift check in pre-push check-affected #12985
The pre-push check-affected run passed on PR #12954's branch, but CI's check-plugins job then failed on scripts/check-cross-plugin-source-drift.sh --check: a new shared copy (reference/one-way-doors.md in planning and review) was not in scripts/cross-plugin-source-registry.txt. scripts/check-affected.sh neither runs that check nor lists it under its "CI only" lines, so a branch that adds a cross-plugin copy learns about the registry only after a CI round (about 10 minutes here).
Fix
Run scripts/check-cross-plugin-source-drift.sh --check from check-affected.sh when the change set touches scripts/shared-copies.txt, lib/, or any file under plugins/*/ that another plugin carries byte-identical. If it is too slow for pre-push, list it under the "CI only" lines so the gap is visible.
Acceptance criteria
A branch that adds a byte-identical file to two plugins without a registry entry fails check-affected before the push, or check-affected names the check as CI only.
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: scripts/check-affected.sh doesn't run scripts/check-cross-plugin-source-drift.sh --check and doesn't list it as CI only. A branch that adds a cross-plugin shared copy therefore fails in CI after passing pre-push. The fix is either to run that check when the change set touches shared copies, or to list it under the "CI only" lines. The acceptance criterion is exact and nothing is missing. I found no duplicate among the open issues.
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41738023849, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-03T23:46:49Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.
The work-resolve-issue run that agent-ready started waited in its slot past a change to its lane workflow files on main, so it stopped before any model turn. The run's report-outcome removed and added agent-ready back to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41756369166, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-04T01:49:51Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.
Activity
github-actions commentedon Nov 3, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood:
scripts/check-affected.shdoesn't runscripts/check-cross-plugin-source-drift.sh --checkand doesn't list it as CI only. A branch that adds a cross-plugin shared copy therefore fails in CI after passing pre-push. The fix is either to run that check when the change set touches shared copies, or to list it under the "CI only" lines. The acceptance criterion is exact and nothing is missing. I found no duplicate among the open issues.Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 4, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41738023849, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-03T23:46:49Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.2 remaining items
github-actions commentedon Nov 4, 2026
github-actions commentedon Nov 4, 2026
melodic-automation-lanes commentedon Nov 4, 2026
The work-resolve-issue run that
agent-readystarted waited in its slot past a change to its lane workflow files on main, so it stopped before any model turn. The run's report-outcome removed and addedagent-readyback to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.melodic-automation-lanes commentedon Nov 4, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41756369166, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-04T01:49:51Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.github-actions commentedon Nov 4, 2026
github-actions commentedon Nov 4, 2026