gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-09-10 02:25:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Preserve live alert truth during input deferral

Browse Source 
Document the alert-side ownership boundary for the shared websocket input gate: resource projections may wait for idle, while active and resolved alert lifecycle updates remain immediate.

Change-source: pulse-maintainer
This commit is contained in:
pulse-triage[bot]
2026-08-26 17:52:36 +01:00
parent 7d34e27b30
commit 6ecdc81d1c
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/release-control/v6/internal/subsystems/alerts.md
+7
View File
@@ -313,6 +313,13 @@ contamination) and performs one canonical catch-up reconciliation on
`visibilitychange` to visible. Alert and
resolved-alert truth continues to update normally while hidden; this resource
optimization must not defer, clear, or reinterpret alert lifecycle state.
Active operator input applies the same separation: scroll, wheel, pointer
press, and key activity may defer resource deltas, reporting projection, and
the shared realtime tick token until the input-idle flush, but alert and
resolved-alert payloads must still commit on the message that carries them.
The input gate must never delay acknowledgement, recovery, navigation counts,
resource alert indicators, or notification-facing alert truth merely because
the resource projection is waiting for an idle window.
The visible-tick resource commit may apply metrics-only rows as per-key
subtree writes instead of whole-row reconciles, but alert truth is outside
that fast path entirely: active-alert and resolved-alert stores keep their