feat(editor): Editor molecule

[netchampfaris]

Summary

Adds the v1 editor family under the frappe-ui/editor subpath (source in src/molecules/editor). The API is built around one renderless <Editor> component plus composable building blocks and configurable extension kits — there are no monolithic "ready-made" editors; consumers compose the pieces they need.

Public surface (frappe-ui/editor)

• Engine — useEditor composable (built on @tiptap/core) and the <Editor> component. <Editor> is renderless: it owns the editor lifecycle, v-model (HTML or JSON via format), upload, and placeholder threading, and exposes { editor, isEmpty } to its slot.
• Building blocks — EditorContent, EditorFixedMenu, EditorBubbleMenu, EditorFloatingMenu. Usable inside <Editor> (they read the editor from context) or standalone on a useEditor ref via an explicit :editor prop.
• Kits — CommentKit, RichTextKit, InlineKit: configurable extension bundles. Each member can be reconfigured or removed (false), so one preset adapts across use cases.
• Extensions — flat named exports with frappe-ui defaults applied: Link, Code/CodeBlock, Image/ImageGroup/ImageViewer/Video/Iframe, Mention, Tag, Emoji, SlashCommands, Table, TaskList, Toc, Color/Highlight, Typography, TextAlign, Placeholder, plus StarterKit. Tree-shakes naturally.
• Menu items + presets — toolbar item definitions, groups, separators, and ready presets (minimalToolbar, commentToolbar, articleToolbar). Items self-prune when their extension isn't loaded.
• Upload plumbing — a shared media-upload engine; uploadFunction is threaded through editor storage and read at use-time (v3-safe, since extension.options is frozen).

Other changes

• Editor guide added under Molecules docs, with stories (RichText, Comment, Inline, Primitives).
• Source path aliases added (@components, @molecules, @utils, @composables, frappe-ui/editor) across Vite, Vitepress, and tsconfig.

Fixes from a TipTap-conventions review

• format="json" no longer resets the selection on every keystroke — the v-model echo guard previously only covered HTML; JSON's fresh-object identity defeated it, so each edit re-ran setContent() and rebuilt the doc. Now the exact emitted value is tracked and skipped.
• Toolbar active/disabled state is reactive again — the @tiptap/core-based editor isn't a reactive ref like @tiptap/vue-3's, so isActive/isDisabled reads in EditorFixedMenu went stale on selection changes. MenuItems now bumps a version on each editor transaction to drive re-evaluation (scoped per instance, works with or without <Editor>).

Validation

• yarn vitest --run src/molecules/editor — 97 passing
• yarn build
• yarn docs:build

Docs preview: https://ui.frappe.io/pr-preview/pr-718/

Coverage: 56.13% (+6.69% vs main)

[netchampfaris]

/barista review

[barista-for-frappe]

Re-reviewing per @netchampfaris — focused on the public API surface of the new editor family.

Concerns — the new surface is clean, but the deprecation bridge misdirects migrating consumers.

• src/components/TextEditor/TextEditor.vue (onMounted, the new console.warn) — the message says "Use <RichTextEditor> for standard rich text", but ADR 0004 explicitly does not ship RichTextEditor/CommentEditor/InlineEditor (spec/adr/0004-...md + index.ts exports none of them; docs/.../molecules/editor.md:337 documents <Editor> + kits instead). Anyone following the warning hunts for a component that doesn't exist. Point it at the real surface: <Editor> + RichTextKit from frappe-ui/editor. The string looks carried over from the stale v1-release/research/12-editor-v1-preview.md:25866 plan that predates the no-ready-mades decision.
• Same line — the warn is an unconditional console.warn in onMounted, so it fires once per instance per mount. The migration plan called for a "one-time warning per mount lifecycle"; a module-level warnOnce guard (and/or dev-only gate) would avoid spamming prod consoles where many <TextEditor>s render.

API tightness — looks good. This is the direction the library should move:

• Editor.vue uses canonical events (change/focus/blur), unnamed v-model via defineModel, and a single format: 'html' | 'json' instead of v-model:html/:json — good P1/P2 call.
• Building blocks (EditorContent/EditorFixedMenu/EditorBubbleMenu/EditorFloatingMenu) style via data-slot rather than class-injection props (P10), and resolve the editor from context with an optional editor? override — no forced :editor threading.
• useEditor options stay primitive (content/format/editable/autofocus/uploadFunction/extensions); no config-blob, no semantic-color axis, no per-component renames. Kits configure via the standard tiptap .configure({ member: false }) pattern. Tests cover kit composition and the Cypress behaviors.

No public prop/slot/event drift found. The two items above are both in the deprecation shim, not the new API.