TipTap → BlockNote editor migration (0312)

.changeset/ai-surface-blocknote-page-markdown.md

@@ -0,0 +1,30 @@
+---
+'@xnetjs/plugins': major
+---
+
+AI page-markdown surface re-targeted to the BlockNote editor (exploration 0312).
+
+- **Breaking**: the page-markdown apply adapter mode `'tiptap-yjs'` is renamed
+  to `'blocknote-yjs'` in `AiPageMarkdownApplyAdapterResult['mode']` and
+  `AiPageMarkdownApplyResult['mode']`. Adapters that returned
+  `mode: 'tiptap-yjs'` must return `'blocknote-yjs'` (or `'yjs'`/`'custom'`).
+- New Yjs-fragment ↔ markdown conversion for BlockNote (`content-v4`)
+  documents, dependency-light (walks the Yjs XML tree directly, no editor/DOM):
+  - `xnetPageFragmentToMarkdown(doc)` reads the BlockNote fragment
+    (paragraph/heading/lists/check items/code/quote/callout/table + inline
+    `mention`/`hashtag`/`wikilink`/`inlineMath` atoms), falling back to the
+    legacy TipTap `content` fragment when `content-v4` is empty
+    (`blockNoteFragmentToMarkdown` / `legacyFragmentToMarkdown` are also
+    exported).
+  - `replaceXNetPageFragmentWithMarkdown(doc, markdown)` writes the AI
+    markdown subset (paragraphs, headings, bullet/numbered/check lists with
+    nesting, fenced code, quotes, callouts, wikilinks) as BlockNote PM XML —
+    `blockGroup > blockContainer` (unique `id` per block) wrappers — in one
+    Yjs transaction.
+  - `createBlockNotePageMarkdownAdapter({ resolveDoc })` packages both as an
+    `AiPageMarkdownApplyAdapter` (plus `readMarkdown`) for
+    `xnet_apply_page_markdown`, replacing the TipTap-era document bridge.
+  - `XNET_PAGE_FRAGMENT_FIELD` (`'content-v4'`) and
+    `XNET_PAGE_LEGACY_FRAGMENT_FIELD` (`'content'`) constants.
+- `@xnetjs/plugins` now depends on `yjs`; the unused `@tiptap/core`
+  devDependency is gone.

.changeset/blocknote-editor-contribution.md

@@ -0,0 +1,19 @@
+---
+'@xnetjs/plugins': major
+---
+
+`EditorContribution` carries BlockNote specs instead of TipTap extensions (exploration 0312).
+
+- **Breaking**: `EditorContribution.extension` (TipTap `Extension`) and
+  `EditorContribution.toolbar` (`ToolbarContribution`, removed entirely) are
+  gone. Plugins now contribute `blockSpecs` / `inlineContentSpecs` /
+  `styleSpecs` (opaque BlockNote spec objects keyed by spec name) plus
+  behavior-only `slashMenuItems`.
+- **Breaking**: the editor schema-skew guard is spec-based —
+  `isSchemaDefiningExtension` is replaced by `isSchemaDefiningContribution`,
+  and `findEditorSchemaRisks` / `warnOnEditorSchemaRisks` take the host's
+  statically bundled spec names and flag any contributed spec outside that
+  set (0205 invariant: schema specs must be identical across all
+  collaborators or Yjs silently drops content).
+- `SlashCommandContext.editor` is now a BlockNote editor instance.
+- The `@tiptap/core` dependency is removed.

.changeset/blocknote-fragment-readers.md

@@ -0,0 +1,29 @@
+---
+'@xnetjs/data': minor
+'@xnetjs/history': minor
+'@xnetjs/react': minor
+'@xnetjs/runtime': patch
+---
+
+Yjs fragment readers understand the BlockNote document schema (exploration 0312).
+
+Documents now live in the `content-v4` fragment using BlockNote's ProseMirror
+shape (`blockGroup > blockContainer > blockContent`); the legacy TipTap
+`content` fragment remains readable as a fallback until each doc is lazily
+imported.
+
+- `@xnetjs/data`: `getRichTextPlainText` extracts text from BlockNote-shaped
+  rich-text cells, including the new inline atoms (`mention` → `@label`,
+  `hashtag` → `#name`, `wikilink` → title, `inlineMath` → latex), while still
+  reading legacy TipTap-shaped cells.
+- `@xnetjs/history`: version-diff text extraction prefers `content-v4` (legacy
+  `content` fallback) and renders BlockNote inline atoms as readable text.
+- `@xnetjs/react`: new `useMergedEditorContributions` /
+  `mergeEditorContributions` (+ `MergedEditorContributions` type) collect
+  plugin-contributed BlockNote `blockSpecs`/`inlineContentSpecs`/`styleSpecs`
+  and slash menu items from the plugin registry, running the editor
+  schema-skew guard (`warnOnEditorSchemaRisks`) against the host's statically
+  bundled spec names and excluding un-bundled (skew-hazard) specs.
+- `@xnetjs/runtime`: blob-CID retention scanning now also walks the
+  `content-v4` and `content` fragments, so blobs referenced from page
+  documents are discovered.

.github/workflows/ci.yml

@@ -182,7 +182,7 @@ jobs:
         run: pnpm --filter @xnetjs/e2e-tests exec playwright install-deps chromium webkit
 
       - name: Run focused editor interaction tests
-        run: pnpm --filter @xnetjs/editor exec vitest run src/nodeviews/hooks/useNodeFocus.test.ts src/components/FloatingToolbar.test.tsx src/components/SlashMenu.test.tsx src/components/editor-ux-state.test.ts src/extensions/live-preview/inline-marks.integration.test.ts
+        run: pnpm --filter @xnetjs/editor exec vitest run src/blocknote/collab-convergence.test.tsx src/blocknote/doc-utils.test.ts src/blocknote/legacy-import.test.ts
 
       - name: Start web app
         run: pnpm --filter xnet-web dev --host 127.0.0.1 --port 5173 > /tmp/xnet-web.log 2>&1 &

.storybook/shims/xnet-plugins-browser.ts

@@ -106,3 +106,12 @@ export type {
 } from '../../packages/plugins/src/workspace'
 export type { SlotContribution, SlotRegion } from '../../packages/plugins/src/contributions'
 export { evaluateInstallConsent, scaffoldPlugin } from '../../packages/plugins/src/ecosystem'
+
+// Editor schema-skew guard (0205, spec-based since 0312) — used by
+// packages/react's useMergedEditorContributions.
+export {
+  findEditorSchemaRisks,
+  isSchemaDefiningContribution,
+  warnOnEditorSchemaRisks
+} from '../../packages/plugins/src/editor-schema-safety'
+export type { EditorSchemaRisk } from '../../packages/plugins/src/editor-schema-safety'

apps/electron/src/renderer/components/MeetingsView.tsx

@@ -4,12 +4,12 @@
  * The recorder/list/detail cores are shared from @xnetjs/views (0277
  * shared-view-core pattern); this wrapper keeps the desktop deltas: local
  * mode state (the desktop shell has no router — same idiom as
- * DataWorkspaceView), the EditorSurface notes editor, and the close
+ * DataWorkspaceView), the XNetEditor notes editor, and the close
  * affordance back to the home canvas. `window.xnetMeetings` is present here,
  * so the recorder runs at the system-audio tier with the native engines.
  */
 
-import { EditorSurface } from '@xnetjs/editor/react'
+import { XNetEditor } from '@xnetjs/editor/react'
 import { MeetingDetailView, MeetingRecorderView, MeetingsListView } from '@xnetjs/views'
 import { ArrowLeft, X } from 'lucide-react'
 import React, { useState } from 'react'
@@ -58,7 +58,7 @@ export function MeetingsView({ onClose }: MeetingsViewProps): React.ReactElement
         <MeetingDetailView
           className="min-h-0 flex-1"
           meetingId={mode.meetingId}
-          renderNotes={({ doc }) => <EditorSurface ydoc={doc} surfaceMode="page" />}
+          renderNotes={({ doc }) => <XNetEditor ydoc={doc} />}
         />
       ) : (
         <MeetingsListView