feat(sync): PRES-2 — main-side presence manager (relay bridge)#136
Merged
Conversation
…lay bridge) The main half of presence (design 74): per shared entity, a proxy y-protocols Awareness the 10.6 AwarenessBroadcaster tracks, bridging the renderer's light state map to the DEK-sealed relay. setLocal (renderer publish) → proxy local → broadcast; applyInbound (relay frame) → proxy remotes → onChange → renderer; remoteStates for the peer push; untrack/dispose broadcast a final null. emit is injectable so two managers loopback in-process — no relay/DEK stack. Display-only, persists nothing, inbound untrusted. +5 tests: two vaults converge, null clears, untrack drops peers, onChange fires, entities isolated. sync suite 286 green; typecheck + lint clean. Next (PRES-2b): the capability-gated 'presence' broker/preload IPC route driving setLocal/onChange from the sandbox + broadcaster activation in the runtime. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
The main half of presence (0.4.0, design 74). Per shared entity, a proxy y-protocols Awareness the dormant-no-longer 10.6
AwarenessBroadcastertracks — bridging the renderer's light presence state map (PRES-1) to the DEK-sealed relay.setLocal(renderer publish) → proxy local → broadcast;applyInbound(relay frame) → proxy remotes →onChange→ renderer;remoteStatesfor the peer push;untrack/disposebroadcast a final null.emitinjectable → two managers loopback in-process, no relay/DEK stack needed to test convergence.peerFromState).Tests: two vaults converge on each other's presence (not self), null clears, untrack drops immediately, onChange fires, entities isolated. sync suite 286 green.
Next — PRES-2b: the capability-gated
presencebroker + preload IPC route (the sandbox surface, driving setLocal/onChange) + broadcaster activation in the runtime. That's the surface PRES-4's security review gates on.🤖 Generated with Claude Code