When an agent stage exhausts its step budget the run parks with the budget as the reason (the parked outcome now reports to the daemon). What it found is not delivered: the partial findings survive only as appended notes on the task.
Decide whether a budget stop should close with the partial findings as its outcome (posted where a completed run's result would go), or keep parking and leave them in notes. If it should deliver, a budget stop needs a delivery path that does not demand the stage's gate has passed, and the note content needs a place in the outcome text.
Done when a budget-stopped stage either delivers what it found or the decision to leave it in notes is recorded here.
Imported from beads archie-core-sceib · GitHub #1891 · type feature · priority P2 · created 2026-10-26
When an agent stage exhausts its step budget the run parks with the budget as the reason (the parked outcome now reports to the daemon). What it found is not delivered: the partial findings survive only as appended notes on the task.
Decide whether a budget stop should close with the partial findings as its outcome (posted where a completed run's result would go), or keep parking and leave them in notes. If it should deliver, a budget stop needs a delivery path that does not demand the stage's gate has passed, and the note content needs a place in the outcome text.
Done when a budget-stopped stage either delivers what it found or the decision to leave it in notes is recorded here.
---
_Imported from beads `archie-core-sceib` · GitHub #1891 · type feature · priority P2 · created 2026-10-26_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When an agent stage exhausts its step budget the run parks with the budget as the reason (the parked outcome now reports to the daemon). What it found is not delivered: the partial findings survive only as appended notes on the task.
Decide whether a budget stop should close with the partial findings as its outcome (posted where a completed run's result would go), or keep parking and leave them in notes. If it should deliver, a budget stop needs a delivery path that does not demand the stage's gate has passed, and the note content needs a place in the outcome text.
Done when a budget-stopped stage either delivers what it found or the decision to leave it in notes is recorded here.
Imported from beads
archie-core-sceib· GitHub #1891 · type feature · priority P2 · created 2026-10-26