Abstract

A method is disclosed for recovering work that automated coding agents pushed to a code-hosting service but never proposed for merge, as when request creation fails softly yet the run is recorded as successful. A periodic collector classifies each branch in a namespace reserved for agents by a pure, ordered decision. Change requests whose head is that very branch are decided first: an open request means the work is visible, a merged one means residue, and a closed-unmerged one, when the observation carries it, is a recorded human verdict. Only branches with no such request get the costly comparison against the main line. A branch that is ahead, has no request and carries a recoverable work-item identifier is stranded work. Findings are reconciled against a ledger keyed on branch name that stores the tip at which each flag was raised. A flag at an unchanged tip is reported quietly, a new tip raises the alarm again, and branches no longer actionable are pruned by full-state synchronisation. In the default report mode, new findings end the run with a distinct exit status, marking a scheduled run failed. Every service read checks status and declared content type before parsing, so an error or non-JSON answer becomes a loud collector failure rather than an empty sweep; only a comparison answered "not found" is read as a deleted branch. An optional, confirmed recovery mode opens change requests for that run's new findings; a closed-request finding is re-proposed only under a separate inclusion switch.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.

Share

COinS