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
Commit 175298a
Browse filesBrowse the repository at this point in the historyBrowse files
fix: monitor holds apply only to progress wakes and survive reconnects
Only a progress wake (notification outcome "updated", such as a Monitor
line) counts as a background wake now. Terminal wakes like "Command …
finished" or "Monitor … was stopped" alert at once, even while an unrelated
monitor is pending. The in-memory shell builder and the SQL shell query
apply the same rule.
The notification gate waits out the grace for any settled background-wake
completion, not only one whose hold was just released. A wake that
completes after its monitor already left no longer alerts on top of the
final wake. When the shell leaves live, the gate pauses its grace timers.
The next live snapshot restarts the grace if the same completion is still
latest, and drops it otherwise, so no completion fires while disconnected
and then again after the reconnect.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments