FigureWidget state desynchronization with multiple concurrent Jupyter clients

Goal: maintain identical figure state across all Jupyter clients connected to the same kernel when using Plotly FigureWidget for live updates.

Constraint: state synchronization relies on ipywidgets WebSocket messages; batching reduces traffic but does not guarantee ordering or deduplication when retries occur, especially with multiple subscribers.

Uncertainty: it is unclear whether Plotly automatically deduplicates write retries or if duplicate messages can cause divergent state.

Questions: Does FigureWidget internally deduplicate retried updates to prevent duplicate writes? How can developers detect state divergence between clients? What configuration options exist to enforce exactly‑once semantics?