What problem does it solve? Building multiplayer collaborative editing with CRDTs involves subtle pitfalls: wrong store types cause merge conflicts, missing initialization breaks sync, deprecated v1 APIs lack status and error handling, and editor integrations (Tiptap, BlockNote, CodeMirror, ReactFlow) each have framework-specific wiring that fails silently when misconfigured. ## Core Features & Use Cases - Core CRDT Store Guidance: Rules for choosing store types (text, array, map, xml), initializing the Velt client, subscribing to remote updates, saving version checkpoints, encryption, webhooks, and debugging with VeltCrdtStoreMap. - Editor Integration Patterns: Step-by-step rules for Tiptap (SSR, disabling history, cursor CSS), BlockNote, CodeMirror (yCollab wiring), and ReactFlow (CRDT node/edge handlers), each with incorrect vs. correct code examples. - v1 to v2 Migration: Migration tables and checklists for moving from deprecated hooks like useVeltCrdtStore to the v2 useStore and useCollaboration APIs with reactive status, sync, and error state. - Use Case: When adding real-time co-editing to a Tiptap editor in Next.js, the agent applies the SSR-disabled loading pattern, disables Tiptap history, installs the correct v2 packages, and wires the CollaborationManager for status and version restore. ## Quick Start Ask the agent to set up Velt CRDT collaboration for your Tiptap editor with a unique editorId and version history support.