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
Outcome metrics that steer allocation toward work that ships and sticks #6974
Capacity used is an input; the goal is merged work that stays merged. Decide which outcome signals to record per lane (merged changes, reverts, review findings after merge, needs-human escalations, reruns) and how they feed back into allocation and the filler queue.
Decisions (owner, 2026-10-16)
Published per-run fields: lane, outcome, duration, turns, models, tokens, estimated cost (labeled an estimate on subscription runs), and run link. The harness writes them after the run, outside the prompt.
Closing as not planned here: the work moves. #6970 is closed, so the open design (which outcome signals to record per lane, and how they steer allocation and the filler queue) is carried to the map, #6958: #6958 (comment). The per-run fields the lane-outcome record does not publish yet (duration, tokens, run link) are split to melodic-software/ci-workflows#885.
To reopen: reopen this issue and say what is still missing.
Activity
github-actions commentedon Oct 11, 2026
Thanks for the report. Automated triage handed this issue to a maintainer.
Automated triage. A maintainer reviews it.
kyle-sexton commentedon Oct 25, 2026
Closing as not planned here: the work moves. #6970 is closed, so the open design (which outcome signals to record per lane, and how they steer allocation and the filler queue) is carried to the map, #6958: #6958 (comment). The per-run fields the lane-outcome record does not publish yet (duration, tokens, run link) are split to melodic-software/ci-workflows#885.
To reopen: reopen this issue and say what is still missing.