@witchcraft/editor
    Preparing search index...
    Collaboration: Extension<any, any> = ...

    We can't use tiptap's collaboration extension (or any extension that creates the sync plugin) because it expects to be configured with the document's ydoc per editor.

    This doesn't mesh well with how the document api works (see DocumentApi).

    This extension only handles the per-view functionality which currently only includes handling collab cursors and keeping their positions stable. It DOES NOT handle the actual syncing or related options.

    That lives on the per-doc cached state, created once per document by createCollaborationPlugins (see useTestDocumentApi for an example).

    The extension only reads from the shared bridge to restore this view's selection after remote transactions.

    With an awareness provider configured, it also renders remote cursors via yCursorPlugin.

    The bridge is created at document load, before any view exists, so this extension is registered unconfigured and handed its bridge later via the setCollabBridge command.

    Any options missing here (such as enableContentCheck) from the regular tiptap collaboration extension are usually available in createCollaborationPlugins.