mirror of
https://github.com/stablyai/orca.git
synced 2026-11-16 10:58:10 +00:00
The desktop's runtime record kept saying 'running' after a sleep from another client until lost-contact tripped (minutes), so an open or predictive wake returned at once without resuming, and the row read awake. - Wake path: a cloud record still 'running' asks the control plane; when the sandbox is suspended the record is marked asleep and the resume runs. - Status reads (window refresh, predictive preflight, the 1 min beat) mark a running record asleep when the control plane says sleeping, so the row reads Asleep. Only when the record is unchanged since it was read. - Quiet (predictive) wakes report whether a resume actually ran; one that found the VM up is 'skipped': no unopened hold, no backoff, no short idle window in main. - A skipped wake (preflight no, or nothing to resume) gives the 30 s hover/focus gap back.