Add presence heartbeat liveness guard#389
Open
zergzorg wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
/claim #12
Summary
collab-presence-heartbeat-liveness-guard, a focused Real-Time Collaborative Editor slice for live cursor and presence fanout safety.Why this solves part of #12
Issue #12 asks for Google Docs-style multi-user editing, live cursor tracking, user presence indicators, and activity status. Those features need a liveness gate before every presence fanout; otherwise stale tabs and broken reconnects can leave ghost collaborators, old cursors, or expired typing state visible to active authors.
This PR adds that pre-broadcast liveness layer without implementing editor UI, transport, privacy redaction, notebook execution, or section-lock recovery.
Sponsor decision packet
reports/presence-liveness-packet.json,reports/presence-liveness-report.md,reports/summary.svg, andreports/demo.mp4.Non-overlap audit
This is separate from the existing #12 work on broad editor foundations, operation replay, offline conflict, notebook workbench and kernel leases, reference formatting and merging, authorship/submission governance, freeze/lock/checkpoint recovery, review lanes, discussion/sidebar audit, autosave recovery, round-trip fidelity, review decision, task dependency, equation/figure anchors, presence privacy, accessibility parity, evidence binding, embargo release, notification visibility, and data availability.
Scope is limited to heartbeat-based liveness and cleanup immediately before cursor/presence snapshots are broadcast.
Scope boundaries
Validation
cd collab-presence-heartbeat-liveness-guard && npm run checkcd collab-presence-heartbeat-liveness-guard && npm testcd collab-presence-heartbeat-liveness-guard && npm run demoffprobe -v error -select_streams v:0 -show_entries stream=codec_name,width,height,duration,avg_frame_rate -show_entries format=size,duration -of default=noprint_wrappers=1 collab-presence-heartbeat-liveness-guard/reports/demo.mp4-> H.264, 960x540, 5s, 15 fpsgit diff --checkgit diff --cached --checknode:cryptoreferencesDemo and artifacts
collab-presence-heartbeat-liveness-guard/reports/demo.mp4collab-presence-heartbeat-liveness-guard/reports/presence-liveness-packet.jsoncollab-presence-heartbeat-liveness-guard/reports/presence-liveness-report.mdcollab-presence-heartbeat-liveness-guard/reports/summary.svg