@byline/richtext-lexical 3.15.2 → 3.16.1

package/package.json

@@ -3,7 +3,7 @@
   "private": false,
   "type": "module",
   "license": "MPL-2.0",
-  "version": "3.15.2",
+  "version": "3.16.1",
   "engines": {
     "node": ">=20.9.0"
   },
@@ -56,12 +56,9 @@
     }
   },
   "dependencies": {
-    "@lexical/clipboard": "0.44.0",
     "@lexical/code": "0.44.0",
     "@lexical/extension": "0.44.0",
-    "@lexical/hashtag": "0.44.0",
     "@lexical/headless": "0.44.0",
-    "@lexical/html": "0.44.0",
     "@lexical/link": "0.44.0",
     "@lexical/list": "0.44.0",
     "@lexical/mark": "0.44.0",
@@ -75,12 +72,11 @@
     "classnames": "^2.5.1",
     "lexical": "0.44.0",
     "npm-run-all": "^4.1.5",
-    "prism-react-renderer": "^2.4.1",
     "react-error-boundary": "^6.1.1",
-    "@byline/core": "3.15.2",
-    "@byline/admin": "3.15.2",
-    "@byline/client": "3.15.2",
-    "@byline/ui": "3.15.2"
+    "@byline/admin": "3.16.1",
+    "@byline/core": "3.16.1",
+    "@byline/ui": "3.16.1",
+    "@byline/client": "3.16.1"
   },
   "peerDependencies": {
     "react": "^19.0.0",

package/src/field/extensions/README.md

@@ -2,7 +2,7 @@
 
 Every built-in feature of the Lexical adapter — and every supported way for a third party to extend it — lives in this directory as a Lexical `defineExtension(...)` co-located with its node class(es), modal, decorator, and (where relevant) populate visitor.
 
-This README is a navigation aid only. The full reference and authoring contract lives in the project's [`docs/RICHTEXT.md`](../../../../../docs/RICHTEXT.md) — start with the **Extensibility** section.
+This README is a navigation aid only. The full reference and authoring contract lives in the project's [`docs/04-collections/06-rich-text.md`](../../../../../docs/04-collections/06-rich-text.md) — start with the **Extensibility** section.
 
 ## What's where
 
@@ -25,7 +25,7 @@ This README is a navigation aid only. The full reference and authoring contract
 
 1. Create a directory next to these.
 2. Implement your `defineExtension(...)` (and any nodes / decorators).
-3. To contribute a toolbar item or a floating UI, declare a peer dependency against `BylineToolbarExtension` / `BylineFloatingUIExtension` — see the worked recipes in `docs/RICHTEXT.md`.
+3. To contribute a toolbar item or a floating UI, declare a peer dependency against `BylineToolbarExtension` / `BylineFloatingUIExtension` — see the worked recipes in `docs/04-collections/06-rich-text.md`.
 4. Either register your extension at site level via `lexicalEditor((c) => c.extensions.add(MyExtension))`, or — if it's a built-in being shipped by this package — append it to `defaultExtensionsArray()` in `field/config/default-extensions.ts`.
 
 You should never need to touch `field/editor.tsx` to add a feature.

package/src/field/markdown/lexical-to-markdown.test.node.ts

@@ -10,7 +10,7 @@
  * Contract tests for the one-way Lexical → markdown export serializer.
  * The expected strings below ARE the format contract — agents build on
  * this shape, so a change here is a consumer-visible format change and
- * should be deliberate (see docs/TODO.md → "The output is a contract
+ * should be deliberate (see TODO-INTERNAL.md → "The output is a contract
  * surface").
  */
 

package/src/field/markdown/lexical-to-markdown.ts

@@ -8,7 +8,7 @@
 
 /**
  * One-way Lexical → markdown serializer for the agent-readable export
- * surface (`.md` routes, `llms.txt` — see docs/TODO.md → markdown export).
+ * surface (`.md` routes, `llms.txt` — see TODO-INTERNAL.md → markdown export).
  *
  * Walks the **stored** `SerializedEditorState` JSON directly — no
  * `@lexical/headless`, no DOM, no node registration. Output is read-only