Repository navigation
[CONT16-01] Continue original work after needs-you hand-back - #464
Conversation
[Medium impact] The reviewed changes appear safe to merge; no new actionable issue was found. SummaryAutomatically continues the original task after a needs-you hand-back, without another owner message.
All four earlier findings are addressed: stranded queues no longer block scheduling, each wake checks continuations, bounded history retains the latest progress, and older results load through the guarded request endpoint.
|
|
@greptileai please re-review exact head |
Closes #459.
After the owner hands back a needs-you computer, the Bot automatically continues the existing task without another message. A durable screen-event cursor and per-card binding schedule one fresh CHAT receipt/VM session/MODEL step while retaining the original work grant, frozen task, physical-computer workspace, model pin and charged allowance. Decline, expiry, ordinary takeover and routine occurrences do not schedule this path.
The scheduler waits for active work, coalesces a run that already carried the outcome, recovers only unclaimed queued requests and never replays an interrupted claim. Bounded prior observations are separate data; handoff facts still use ADR 0092's existing outcome source and publication-only delivery. Original policy, stop, Bot/private scope, unknown claims and memory/file withdrawal fences remain current. Copied instructions never become new owner ingress or interpretation history.
English/Thai cards project actual continuation state, the transcript labels host continuation, and usage maps exact work plus MODEL step to its receipt. ADR 0094 and the browser contract document the scoped behavior and alternatives.
Validation and review follow-up at head a8d8630:
vm_state_path_too_long). The fixture now uses the existing QEMU tests' short-root convention; its 21 tests passed. Production path validation is unchanged.Restart tests reopen journals and explicitly seed an interrupted claim; they do not certify physical power loss. Models, guest protocol and hypervisor input are fixtures. Live guest/account/SSH/sudo/subscription/native-device evidence and owner-host adoption remain separate (#431/#432). No upstream runtime/dependency/source was imported.