@onodocs/canvas 0.4.0 → 0.5.1

package/LICENSE

@@ -1,10 +1,18 @@
-OnoDocs SDK
+OnoDocs SDK and Canvas
 All rights reserved, except for the permissions below and separately licensed third-party components.
 
+These terms apply to @onodocs/sdk and @onodocs/canvas. OnoDocs-authored @onodocs/editor source is separately licensed under MIT, including its interface, application sessions, form and template controls, and collaboration client. These commercial terms do not restrict the MIT rights to use, modify or redistribute that editor code. The editor's MIT license does not grant production or redistribution rights in SDK or Canvas dependencies. Third-party code retains its own license.
+
 Free evaluation permits installation, development, testing, and internal demonstrations for the purpose of evaluating OnoDocs. It has no time limit. It does not permit production use, including internal production workflows or services supplied to others. Preserve evaluation notices and watermarks. A signed trial license permits watermark-free evaluation for 30 days from issuance; it does not grant production rights.
 
-Production use requires a commercial license issued by OnoDocs. The named licensee may use and deploy the SDK within the scope recorded in that license and the associated purchase agreement. Covered SDK releases may be used perpetually. The updates-through date includes releases published on that UTC date; it is not a runtime expiry. Renewal grants access to subsequent releases and support under the purchase agreement. A license to an application does not grant rights to redistribute the SDK as a competing standalone product.
+Production use requires a commercial license issued by OnoDocs. The named licensee may use and deploy OnoDocs within the application scope recorded in that license and the associated purchase agreement. One application license covers the SDK and Canvas packages and all capabilities serving that named product, including its frontend, backend, workers and self-hosted collaboration. Backend-only document automation also counts as an application. The same product's domains, environments, tenants and customer-hosted installations are included. A shared backend serving three distinct products requires scope covering three applications. Developers, users and processed documents are unlimited within the covered application scope.
+
+Ordinary embedding and custom branding within a covered application are included. A finished document editor sold to end users is permitted under an ordinary application license. Reselling a reusable component containing the SDK or Canvas, granting independent downstream development rights to those packages, or selling a general document-processing API using them to developers requires a separate written redistribution agreement with OnoDocs. An agency or its client may be the named licensee, with the client application identified in the agreed scope.
+
+Generated DOCX and PDF files and extracted data may be distributed without OnoDocs royalties or recipient licenses. Recipients who run SDK or Canvas in their own software must have that use covered by an application license or separate redistribution agreement. Evaluation notices and watermarks must still be preserved.
+
+Covered releases may be used perpetually. The initial purchase includes 12 months of updates and email support for product issues. The updates-through date includes releases published on that UTC date; it is not a runtime expiry. Renewal is optional and grants further updates and support under the purchase agreement.
 
-Do not use another customer's key or remove licensing checks or evaluation notices to obtain unlicensed production use. The same terms apply to low-level stage APIs, custom adapters, browser applications, and server rendering. A publicly downloadable package does not grant production rights.
+Do not use another customer's key or remove licensing checks or evaluation notices to obtain unlicensed production use. The same terms apply to low-level stage APIs, custom adapters, browser applications and server processing. A publicly downloadable package does not grant production rights.
 
-The SDK is provided as is, without warranties, except as expressly agreed in a commercial agreement. Third-party components retain their respective licenses.
+OnoDocs is provided as is, without warranties, except as expressly agreed in a commercial agreement. Third-party components retain their respective licenses.

package/LICENSING.md

@@ -1,6 +1,6 @@
 # Offline licensing
 
-The OnoDocs SDK and Canvas packages support evaluation, trial and commercial use under the same terms. Packages can be installed from an npm registry or supplied archives and copied into an offline environment. Runtime licensing makes no network requests.
+The OnoDocs SDK and Canvas packages support evaluation, trial and commercial use under the terms below. OnoDocs-authored `@onodocs/editor` code is licensed under MIT, including its UI, application sessions, form/template controls and collaboration client. You may use, modify and redistribute that editor code in commercial products under MIT. Preserve its copyright notice and applicable third-party notices. MIT rights in Editor do not grant production or redistribution rights in the commercial SDK and Canvas dependencies. Editor has no separate entitlement. Packages can be installed from an npm registry or supplied archives and copied into an offline environment. Runtime licensing makes no network requests.
 
 | Mode | Behavior |
 | --- | --- |
@@ -9,6 +9,18 @@ The OnoDocs SDK and Canvas packages support evaluation, trial and commercial use
 | Commercial | Signed key permits the purchased scope and removes evaluation notices. Covered releases work indefinitely. |
 | Demo | OnoDocs website demonstrations only. Valid for at most 24 hours at one exact browser origin; not valid for backend use. |
 
+## Application scope
+
+One application license covers SDK and Canvas and all capabilities serving one named product, including frontend, backend, workers and self-hosted collaboration. Backend-only document automation counts as an application. Multiple domains, environments, tenants and customer-hosted installations of that same product are included. A shared backend serving three distinct products needs scope covering three applications. Developers, users and documents are unlimited within that scope.
+
+Ordinary embedding and custom branding are included, as is selling a finished document editor to end users. Reselling reusable components containing SDK or Canvas, granting independent downstream development rights to those commercial packages, or selling a general document-processing API using them to developers requires a separately quoted written redistribution agreement. Redistribution of the MIT editor code itself remains permitted under MIT. For agency work, identify the client application and whether the agency or client is the license holder in the purchase agreement.
+
+Generated DOCX, PDF and extracted data can be distributed without OnoDocs royalties or recipient licenses. A recipient running SDK or Canvas in their own software needs covered application scope or a separate redistribution agreement. Preserve evaluation notices and watermarks. DOCX export does not add a watermark or restrict document content.
+
+A one-application license costs $999 and a five-application license costs $2,499. Both include all capabilities, perpetual use of covered releases, and 12 months of updates and email product-issue support. Optional renewals cost $499 and $1,249 respectively. Renewals extend updates and support; covered releases continue working without renewal.
+
+## Runtime configuration
+
 Pass the issued token as `licenseKey` when opening a document:
 
 ```ts
@@ -24,10 +36,14 @@ The default Node analysis entry point accepts the same option. With `@onodocs/sd
 
 Missing or invalid keys preserve document functionality and return evaluation mode with a `reason`: `missing-key`, `invalid-key`, `verification-unavailable`, `not-yet-valid`, `trial-expired`, or `release-not-covered`. Trial expiry is checked on opening, status access and rendering. Already produced images remain unchanged. Browsers need HTTPS or a secure local context for native signature verification; no internet connection is needed. The headless renderer supplies its own isolated secure context.
 
-Commercial keys contain an inclusive `updatesThrough` date. A key covering 2027-10-04 permits releases published on or before that UTC date forever. Renew to use later releases and receive further support. `sdkReleaseDate`, exported from each entry point, identifies the running release date. Scope is recorded in the key and purchase agreement; it is not inferred from a hostname or tracked online.
+Commercial keys contain an inclusive `updatesThrough` date. A key covering 2027-10-04 permits releases published on or before that UTC date forever. Renew to use later releases and receive further support. `sdkReleaseDate`, exported from the SDK analysis, browser and server entry points, identifies the running release date. Scope is recorded in the key and purchase agreement; it is not inferred from a hostname or tracked online.
 
 Canvas, mounted views, PNG, JPEG and PDF receive the same evaluation watermark. Queries, source models, layouts and display lists remain complete. Low-level stage APIs and custom adapters are covered by the same terms; custom evaluation presentations must preserve an evaluation notice. Offline JavaScript checks can be bypassed by changing code or the clock; they do not provide immediate revocation or seat counting.
 
 Demo licenses also report `demo-expired` or `origin-not-covered`. The website handles early renewal; the SDK continues to verify locally without contacting a license server. They do not grant customer production rights.
 
-The included `LICENSE` states evaluation and commercial usage permissions.
+SDK and Canvas include the commercial `LICENSE`; Editor includes the MIT `LICENSE`. Third-party components retain their respective licenses.
+
+Editor and application sessions accept the key through `document: { licenseKey }`. Form views and designers use the same document option. Collaborative browser sessions use `editor: { document: { licenseKey } }`; their host service accepts `createCollaborationService({ licenseKey, authorize, storage })`. Configure both sides of the named application. Templates retain their opening key when generating documents, and data-only forms use their supplied document's entitlement. The HTTP service forwards its `document` options to the renderer.
+
+Application counts and redistribution permissions are contractual. The verifier checks signed identity, trial expiry and release coverage, with no application counter or customer host binding. The origin restriction applies only to short-lived OnoDocs website demo keys. Existing commercial keys remain valid within their agreed scope.

package/README.md

@@ -8,11 +8,11 @@ For form authoring, controlled answer regions and completed DOCX plus structured
 
 For application events, autosave, recovery, framework lifecycle and self-hosted HTTP, see [application integration](application-integration.md).
 
-`@onodocs/sdk` processes Word documents. Its default entry performs analysis in Node or a browser; `/browser` adds layout and immutable page publication using browser font services; `/server` runs that processing in headless Chromium. `@onodocs/canvas` paints prepared pages and provides the viewer, selection and DOM attachments. The Canvas package runs independently of the parser, semantic engine and layout engine.
+`@onodocs/sdk` processes Word documents. Its default entry performs analysis in Node or a browser; `/browser` adds layout and immutable page publication using browser font services; `/server` runs that processing in headless Chromium. `@onodocs/canvas` paints prepared pages and provides the viewer, selection and DOM attachments. The Canvas package runs independently of the parser, semantic engine and layout engine. `@onodocs/editor` provides the ready-made editor and its UI workflows through public SDK and Canvas APIs. See the [editor package and migration guide](editor.md).
 
 Supported Word inputs are DOCX, DOCM, DOTX and DOTM. Macro-enabled files are rendered without executing VBA. Older binary DOC/DOT files and RTF are not supported.
 
-Install with `npm install @onodocs/sdk @onodocs/canvas`. Use matching versions of both packages. A backend can install only the SDK; a frontend receiving prepared pages can install only Canvas. Both packages include TypeScript declarations and this guide. Archives are also available from the [public releases](https://github.com/onodocs/onodocs/releases). Server rendering requires an installed Chromium-family browser. The server adapter includes the Canvas runtime it uses for image and PDF export.
+Install with `npm install @onodocs/sdk @onodocs/canvas`. Use matching versions of both packages. A backend performing data operations can install only the SDK; a frontend receiving prepared pages can install only Canvas. Both packages include TypeScript declarations and this guide. Archives are also available from the [public releases](https://github.com/onodocs/onodocs/releases). Server rendering requires `npm install @onodocs/sdk playwright-core` and an installed Chromium-family browser. Playwright is an optional peer dependency, so browser and data-only installs do not install it. The server adapter includes the Canvas runtime it uses for image and PDF export.
 
 Without a key, the SDK runs in free, non-production evaluation mode with full features and a watermark on rendered output. Pass `{ licenseKey }` to `openDocument` for a 30-day trial or commercial entitlement; this works in all three entry points. Verification is entirely offline. Commercial keys permit covered releases indefinitely, with renewal for later releases and support. Browser verification requires HTTPS or a secure local context. See the included `LICENSING.md` and `LICENSE` for details.
 
@@ -87,7 +87,7 @@ The [report review example](https://github.com/ionoy/onodocs/blob/main/docs/ai-r
 
 ## Design and generate Word templates
 
-Use `createTemplateEditor` from `@onodocs/sdk/editor` for visual field authoring and preview. `openTemplate` and `templateTag` from the default SDK and browser entries support fields, repeated content, conditions, images, formatted values, reusable sections and batch generation. See [Word templates and generation](templates.md) for the binding model, authoring commands and output workflow.
+Use `createTemplateEditor` from `@onodocs/editor` for visual field authoring and preview. `openTemplate` and `templateTag` from the default SDK and browser entries support fields, repeated content, conditions, images, formatted values, reusable sections and batch generation. See [Word templates and generation](templates.md) for the binding model, authoring commands and output workflow.
 
 ## Replace text and fill templates
 
@@ -171,7 +171,7 @@ Node and browser documents expose `edit`; server documents forward the same oper
 ## Embed the Word editor
 
 ```js
-import { createEditor } from "@onodocs/sdk/editor";
+import { createEditor } from "@onodocs/editor";
 
 const editor = createEditor({ container: document.querySelector("#editor") });
 await editor.newDocument();
@@ -181,9 +181,23 @@ editor.dispose();
 
 The component includes file opening, a new-document command, formatting, imported paragraph styles, lists, regular tables, paragraph images, links, page settings, default headers and footers, find/replace, clipboard operations, undo/redo and Word/PDF downloads. It runs in the browser. `examples/browser-editor/` is the standalone application; run `npm run example:editor` from the source workspace.
 
-Customize the toolbar by passing an ordered list of control names, or `false` to supply your own controls. Available names are `open`, `new`, `save`, `pdf`, `undo`, `redo`, `bold`, `italic`, `underline`, `strike`, `font`, `size`, `color`, `alignment`, `style`, `list`, `table`, `tableTools`, `link`, `image`, `imageTools`, `page`, `header`, `footer`, `find` and `replace`. `fonts` supplies font-family choices; `styles` supplies `{ id, label }` choices using existing Word style IDs. `commands` adds `{ id, label, execute(editor) }` actions. `onChange` receives the editor after committed changes; `onError` reports queued operation failures. Use `document` for browser SDK options such as licensing and font sources, and `readOnly: true` to disable authoring.
+Use `toolbar` to choose which controls are available in the ribbon, or pass `false` to supply your own controls. The editor groups controls into File, Home, Insert and Layout tabs, with Table and Picture tabs for the selected content. Available names are `open`, `new`, `save`, `pdf`, `undo`, `redo`, `bold`, `italic`, `underline`, `strike`, `font`, `size`, `color`, `alignment`, `style`, `list`, `table`, `tableTools`, `link`, `image`, `imageTools`, `page`, `header`, `footer`, `find` and `replace`. `fonts` supplies font-family choices; `styles` supplies `{ id, label }` choices using existing Word style IDs. `onChange` receives the editor after committed changes; `onError` reports queued operation failures. Use `document` for browser SDK options such as licensing and font sources, and `readOnly: true` to disable authoring.
 
-The editor supports native text selection and IME input. F6 switches between the document and toolbar, Escape focuses the toolbar, and Shift+Tab leaves the editing area. On touch screens, tap to place the caret, hold to select a word, and drag the selection endpoints. Narrow toolbars scroll horizontally. Mounted pages expose text and headings to browser accessibility tools, including pages whose canvases have been evicted.
+`commands` adds application actions to the Home tab. Set a command's `ribbon` metadata to place it in a named tab and group. Include its ID when restricting `toolbar` to a list of controls.
+
+```js
+const editor = createEditor({
+  container: document.querySelector("#editor"),
+  commands: [{
+    id: "save-to-project",
+    label: "Save to project",
+    ribbon: { tab: "File", group: "Project" },
+    execute: async editor => saveToProject(await editor.save()),
+  }],
+});
+```
+
+The editor supports native text selection and IME input. F6 switches between the document and ribbon, Escape focuses the ribbon, and Shift+Tab leaves the editing area. Arrow keys move between ribbon tabs. On touch screens, tap to place the caret, hold to select a word, and drag the selection endpoints. Narrow ribbons scroll horizontally. Mounted pages expose text and headings to browser accessibility tools, including pages whose canvases have been evicted.
 
 Each instance has isolated styles and history. Customize `--onodocs-color`, `--onodocs-background`, `--onodocs-toolbar-background`, `--onodocs-accent` and `--onodocs-selection` on the host container. The `toolbar`, `pages` and `status` shadow parts are available for host styling. Call `dispose()` when removing an editor.
 
@@ -221,7 +235,7 @@ input.name = "customerName";
 const attachment = view.attach(input, { anchor: doc.geometry.fragments(field)[0] });
 ```
 
-The example requires a tagged control that produces one visible fragment. Call `doc.geometry.fragments(field)` for content spanning lines, pages, or repeated stories, and attach to an explicitly chosen fragment. Fragments retain transforms and clipping. Table/cell anchors use their final physical rectangles. `offset` and `size` optionally adjust attachment placement in page units. Values, validation, submission, focus, and accessibility labels belong to the application. Attaching an element moves it into the view. Detachment removes it and restores its original inline style. Reattaching the same HTML element disposes its previous attachment; old handles become inert. An attachment exposes its disposed state.
+The example requires a tagged control that produces one visible fragment. Call `doc.geometry.fragments(field)` for content spanning lines, pages, or repeated stories, and attach to an explicitly chosen fragment. Fragments retain transforms and clipping. Table/cell anchors use their final physical rectangles. `offset` and `size` optionally adjust attachment placement in page units. Use `interactive: false` for decorative overlays so clicks reach the document underneath. Values, validation, submission, focus, and accessibility labels belong to the application. Attaching an element moves it into the view. Detachment removes it and restores its original inline style. Reattaching the same HTML element disposes its previous attachment; old handles become inert. An attachment exposes its disposed state.
 
 Pages are anchors too. Placement avoids manual rectangle arithmetic:
 
@@ -383,6 +397,8 @@ Open with `revisionView: "accepted"` when editing current text. `readReview()` i
 
 Enable the editor panel with `review: { identity: () => identity, history }`. The optional `history` object implements `list(signal)`, `load(id, signal)` and `save(version, bytes, signal)`. Your application stores the complete Word bytes and version metadata. The SDK adds no persistence service or user account system. Restoring a version is undoable and raises the editor's change event, so application autosave can persist it. `compareDocuments(savedBytes, doc)` returns paragraph text and formatting differences without modifying the document.
 
+Browser and server opening options accept `commentDisplay: "hidden"` to hide comment indicators in rendered pages and PDF exports. Comments remain available through `readReview()` and in saved Word files. The editor uses this display by default and shows comments in its Review pane. Set `document: { commentDisplay: "markers" }` to display indicators in the editor; SDK rendering defaults to markers.
+
 ## Searchable PDF in the browser
 
 ```js
@@ -405,3 +421,5 @@ try {
 PDF export runs locally and uses the same implementation as server `doc.pdf()`. It waits for earlier edits to finish. Pass `signal` to cancel an export without closing the document. The PDF writer loads on demand; deploy the browser entry's generated chunks alongside it. Text extraction order for bidirectional paragraphs and selection across complex clusters depend on the PDF reader. Solid graphics use vector PDF paths where supported. Native text and complex effects retain browser rendering in cropped lossless image layers, including evaluation marks. Higher DPI increases the sharpness, file size and temporary memory use of those layers; compressed output remains in memory until export finishes.
 
 The PDF includes tagged headings, paragraphs, nested lists, tables, header cells, merged-cell row/column spans, authored figure descriptions and links, plus heading and bookmark navigation. Set `title` and `language` for reader metadata. DrawingML descriptions use `wp:docPr/@descr`, falling back to `title`; VML uses authored `alt` text. Undescribed graphics remain artifacts. Reader support varies. Firefox PDF.js exposes named images, list nesting and table spans in its accessibility tree. This does not claim PDF/UA conformance or validation with every screen reader.
+
+One named-application license covers SDK and Canvas, including the application's backend and self-hosted collaboration. Finished editors for end users are included. Editor source is separately licensed under MIT. See [application scope, output rights and redistribution terms](licensing.md).

package/SDK.md

@@ -8,11 +8,11 @@ For form authoring, controlled answer regions and completed DOCX plus structured
 
 For application events, autosave, recovery, framework lifecycle and self-hosted HTTP, see [application integration](application-integration.md).
 
-`@onodocs/sdk` processes Word documents. Its default entry performs analysis in Node or a browser; `/browser` adds layout and immutable page publication using browser font services; `/server` runs that processing in headless Chromium. `@onodocs/canvas` paints prepared pages and provides the viewer, selection and DOM attachments. The Canvas package runs independently of the parser, semantic engine and layout engine.
+`@onodocs/sdk` processes Word documents. Its default entry performs analysis in Node or a browser; `/browser` adds layout and immutable page publication using browser font services; `/server` runs that processing in headless Chromium. `@onodocs/canvas` paints prepared pages and provides the viewer, selection and DOM attachments. The Canvas package runs independently of the parser, semantic engine and layout engine. `@onodocs/editor` provides the ready-made editor and its UI workflows through public SDK and Canvas APIs. See the [editor package and migration guide](editor.md).
 
 Supported Word inputs are DOCX, DOCM, DOTX and DOTM. Macro-enabled files are rendered without executing VBA. Older binary DOC/DOT files and RTF are not supported.
 
-Install with `npm install @onodocs/sdk @onodocs/canvas`. Use matching versions of both packages. A backend can install only the SDK; a frontend receiving prepared pages can install only Canvas. Both packages include TypeScript declarations and this guide. Archives are also available from the [public releases](https://github.com/onodocs/onodocs/releases). Server rendering requires an installed Chromium-family browser. The server adapter includes the Canvas runtime it uses for image and PDF export.
+Install with `npm install @onodocs/sdk @onodocs/canvas`. Use matching versions of both packages. A backend performing data operations can install only the SDK; a frontend receiving prepared pages can install only Canvas. Both packages include TypeScript declarations and this guide. Archives are also available from the [public releases](https://github.com/onodocs/onodocs/releases). Server rendering requires `npm install @onodocs/sdk playwright-core` and an installed Chromium-family browser. Playwright is an optional peer dependency, so browser and data-only installs do not install it. The server adapter includes the Canvas runtime it uses for image and PDF export.
 
 Without a key, the SDK runs in free, non-production evaluation mode with full features and a watermark on rendered output. Pass `{ licenseKey }` to `openDocument` for a 30-day trial or commercial entitlement; this works in all three entry points. Verification is entirely offline. Commercial keys permit covered releases indefinitely, with renewal for later releases and support. Browser verification requires HTTPS or a secure local context. See the included `LICENSING.md` and `LICENSE` for details.
 
@@ -87,7 +87,7 @@ The [report review example](https://github.com/ionoy/onodocs/blob/main/docs/ai-r
 
 ## Design and generate Word templates
 
-Use `createTemplateEditor` from `@onodocs/sdk/editor` for visual field authoring and preview. `openTemplate` and `templateTag` from the default SDK and browser entries support fields, repeated content, conditions, images, formatted values, reusable sections and batch generation. See [Word templates and generation](templates.md) for the binding model, authoring commands and output workflow.
+Use `createTemplateEditor` from `@onodocs/editor` for visual field authoring and preview. `openTemplate` and `templateTag` from the default SDK and browser entries support fields, repeated content, conditions, images, formatted values, reusable sections and batch generation. See [Word templates and generation](templates.md) for the binding model, authoring commands and output workflow.
 
 ## Replace text and fill templates
 
@@ -171,7 +171,7 @@ Node and browser documents expose `edit`; server documents forward the same oper
 ## Embed the Word editor
 
 ```js
-import { createEditor } from "@onodocs/sdk/editor";
+import { createEditor } from "@onodocs/editor";
 
 const editor = createEditor({ container: document.querySelector("#editor") });
 await editor.newDocument();
@@ -181,9 +181,23 @@ editor.dispose();
 
 The component includes file opening, a new-document command, formatting, imported paragraph styles, lists, regular tables, paragraph images, links, page settings, default headers and footers, find/replace, clipboard operations, undo/redo and Word/PDF downloads. It runs in the browser. `examples/browser-editor/` is the standalone application; run `npm run example:editor` from the source workspace.
 
-Customize the toolbar by passing an ordered list of control names, or `false` to supply your own controls. Available names are `open`, `new`, `save`, `pdf`, `undo`, `redo`, `bold`, `italic`, `underline`, `strike`, `font`, `size`, `color`, `alignment`, `style`, `list`, `table`, `tableTools`, `link`, `image`, `imageTools`, `page`, `header`, `footer`, `find` and `replace`. `fonts` supplies font-family choices; `styles` supplies `{ id, label }` choices using existing Word style IDs. `commands` adds `{ id, label, execute(editor) }` actions. `onChange` receives the editor after committed changes; `onError` reports queued operation failures. Use `document` for browser SDK options such as licensing and font sources, and `readOnly: true` to disable authoring.
+Use `toolbar` to choose which controls are available in the ribbon, or pass `false` to supply your own controls. The editor groups controls into File, Home, Insert and Layout tabs, with Table and Picture tabs for the selected content. Available names are `open`, `new`, `save`, `pdf`, `undo`, `redo`, `bold`, `italic`, `underline`, `strike`, `font`, `size`, `color`, `alignment`, `style`, `list`, `table`, `tableTools`, `link`, `image`, `imageTools`, `page`, `header`, `footer`, `find` and `replace`. `fonts` supplies font-family choices; `styles` supplies `{ id, label }` choices using existing Word style IDs. `onChange` receives the editor after committed changes; `onError` reports queued operation failures. Use `document` for browser SDK options such as licensing and font sources, and `readOnly: true` to disable authoring.
 
-The editor supports native text selection and IME input. F6 switches between the document and toolbar, Escape focuses the toolbar, and Shift+Tab leaves the editing area. On touch screens, tap to place the caret, hold to select a word, and drag the selection endpoints. Narrow toolbars scroll horizontally. Mounted pages expose text and headings to browser accessibility tools, including pages whose canvases have been evicted.
+`commands` adds application actions to the Home tab. Set a command's `ribbon` metadata to place it in a named tab and group. Include its ID when restricting `toolbar` to a list of controls.
+
+```js
+const editor = createEditor({
+  container: document.querySelector("#editor"),
+  commands: [{
+    id: "save-to-project",
+    label: "Save to project",
+    ribbon: { tab: "File", group: "Project" },
+    execute: async editor => saveToProject(await editor.save()),
+  }],
+});
+```
+
+The editor supports native text selection and IME input. F6 switches between the document and ribbon, Escape focuses the ribbon, and Shift+Tab leaves the editing area. Arrow keys move between ribbon tabs. On touch screens, tap to place the caret, hold to select a word, and drag the selection endpoints. Narrow ribbons scroll horizontally. Mounted pages expose text and headings to browser accessibility tools, including pages whose canvases have been evicted.
 
 Each instance has isolated styles and history. Customize `--onodocs-color`, `--onodocs-background`, `--onodocs-toolbar-background`, `--onodocs-accent` and `--onodocs-selection` on the host container. The `toolbar`, `pages` and `status` shadow parts are available for host styling. Call `dispose()` when removing an editor.
 
@@ -221,7 +235,7 @@ input.name = "customerName";
 const attachment = view.attach(input, { anchor: doc.geometry.fragments(field)[0] });
 ```
 
-The example requires a tagged control that produces one visible fragment. Call `doc.geometry.fragments(field)` for content spanning lines, pages, or repeated stories, and attach to an explicitly chosen fragment. Fragments retain transforms and clipping. Table/cell anchors use their final physical rectangles. `offset` and `size` optionally adjust attachment placement in page units. Values, validation, submission, focus, and accessibility labels belong to the application. Attaching an element moves it into the view. Detachment removes it and restores its original inline style. Reattaching the same HTML element disposes its previous attachment; old handles become inert. An attachment exposes its disposed state.
+The example requires a tagged control that produces one visible fragment. Call `doc.geometry.fragments(field)` for content spanning lines, pages, or repeated stories, and attach to an explicitly chosen fragment. Fragments retain transforms and clipping. Table/cell anchors use their final physical rectangles. `offset` and `size` optionally adjust attachment placement in page units. Use `interactive: false` for decorative overlays so clicks reach the document underneath. Values, validation, submission, focus, and accessibility labels belong to the application. Attaching an element moves it into the view. Detachment removes it and restores its original inline style. Reattaching the same HTML element disposes its previous attachment; old handles become inert. An attachment exposes its disposed state.
 
 Pages are anchors too. Placement avoids manual rectangle arithmetic:
 
@@ -383,6 +397,8 @@ Open with `revisionView: "accepted"` when editing current text. `readReview()` i
 
 Enable the editor panel with `review: { identity: () => identity, history }`. The optional `history` object implements `list(signal)`, `load(id, signal)` and `save(version, bytes, signal)`. Your application stores the complete Word bytes and version metadata. The SDK adds no persistence service or user account system. Restoring a version is undoable and raises the editor's change event, so application autosave can persist it. `compareDocuments(savedBytes, doc)` returns paragraph text and formatting differences without modifying the document.
 
+Browser and server opening options accept `commentDisplay: "hidden"` to hide comment indicators in rendered pages and PDF exports. Comments remain available through `readReview()` and in saved Word files. The editor uses this display by default and shows comments in its Review pane. Set `document: { commentDisplay: "markers" }` to display indicators in the editor; SDK rendering defaults to markers.
+
 ## Searchable PDF in the browser
 
 ```js
@@ -405,3 +421,5 @@ try {
 PDF export runs locally and uses the same implementation as server `doc.pdf()`. It waits for earlier edits to finish. Pass `signal` to cancel an export without closing the document. The PDF writer loads on demand; deploy the browser entry's generated chunks alongside it. Text extraction order for bidirectional paragraphs and selection across complex clusters depend on the PDF reader. Solid graphics use vector PDF paths where supported. Native text and complex effects retain browser rendering in cropped lossless image layers, including evaluation marks. Higher DPI increases the sharpness, file size and temporary memory use of those layers; compressed output remains in memory until export finishes.
 
 The PDF includes tagged headings, paragraphs, nested lists, tables, header cells, merged-cell row/column spans, authored figure descriptions and links, plus heading and bookmark navigation. Set `title` and `language` for reader metadata. DrawingML descriptions use `wp:docPr/@descr`, falling back to `title`; VML uses authored `alt` text. Undescribed graphics remain artifacts. Reader support varies. Firefox PDF.js exposes named images, list nesting and table spans in its accessibility tree. This does not claim PDF/UA conformance or validation with every screen reader.
+
+One named-application license covers SDK and Canvas, including the application's backend and self-hosted collaboration. Finished editors for end users are included. Editor source is separately licensed under MIT. See [application scope, output rights and redistribution terms](licensing.md).

package/agreement-review.md

@@ -1,6 +1,6 @@
 # Agreement review
 
-Run `npm run build`, then `npm run example:agreement-review` and open the printed local address. From an installed SDK package, install `esbuild` alongside `@onodocs/sdk` and run `node node_modules/@onodocs/sdk/examples/agreement-review/serve.mjs`.
+Run `npm run build`, then `npm run example:agreement-review` and open the printed local address. From an installed Editor package, install `esbuild` alongside `@onodocs/editor` and run `node node_modules/@onodocs/editor/examples/agreement-review/serve.mjs`.
 
 Choose a clause and add a comment in the review panel. Switch reviewer identity to reply as the other fictional party. Select Suggest wording, edit the clause, and submit. The review panel shows the deletion and insertion separately. Accept all or Reject all decides the entire replacement; individual buttons decide one revision at a time. Compare with original shows the current text against the original agreement.
 

package/application-integration.md

@@ -2,10 +2,10 @@
 
 The session accepts the editor's [document modes](document-modes.md). A mode change preserves session revision and dirty state; edits, review actions and filled answers use the same committed-change and autosave path.
 
-`@onodocs/sdk/application` embeds the existing Word editor with application saving and recovery. Use matching SDK and Canvas packages built with these entry points. Older published packages do not include them.
+`@onodocs/editor/application` embeds the existing Word editor with application saving and recovery. Use matching SDK and Canvas packages built with these entry points. Older published packages do not include them.
 
 ```js
-import { openApplicationEditor } from "@onodocs/sdk/application";
+import { openApplicationEditor } from "@onodocs/editor/application";
 import { recoveryStore } from "./recovery.js";
 
 const application = await openApplicationEditor({
@@ -59,7 +59,7 @@ Abort source fetching when unmounting. Do not invoke mounting during SSR. The he
 
 `@onodocs/sdk/http` exports `createHttpService({ renderer, authorize, document?, onError? })`. It wraps the existing server renderer and backend-viewer manifest/page contract. Authorization returns a stable application-controlled principal string or undefined. Every request authenticates; each document belongs to its principal. Call service.handle from a Node HTTP listener. Stop requests, await service.dispose, then dispose the renderer. TypeScript backends should install @types/node and include node in their compiler types.
 
-Run `npm run build`, set `ONODOCS_SERVICE_TOKEN`, then run `npm run example:http`. The sample in `examples/http-service/server.mjs` defaults to loopback port 5191 and Chrome. HOST, PORT, CHROMIUM_PATH and ONODOCS_LICENSE_KEY configure it. Keep its bearer credential on the backend. Browsers should use an application-owned authenticated gateway. For installed-package use, copy the sample and install matching SDK/Canvas releases containing these entry points.
+Run `npm run build`, set `ONODOCS_SERVICE_TOKEN`, then run `npm run example:http`. The sample in `examples/http-service/server.mjs` defaults to loopback port 5191 and Chrome. HOST, PORT, CHROMIUM_PATH and ONODOCS_LICENSE_KEY configure it. Keep its bearer credential on the backend. Browsers should use an application-owned authenticated gateway. For installed-package use, install `@onodocs/sdk playwright-core` and run `node node_modules/@onodocs/sdk/examples/http-service/server.mjs`.
 
 | Request | Response |
 | --- | --- |
@@ -85,3 +85,5 @@ These clients upload, export and delete. They use ONODOCS_SERVICE_TOKEN and opti
 Deploy behind your application's TLS proxy on a private interface using an unprivileged account. Install Node, Chromium and the required fonts; keep browser sandbox support enabled. Use a supervisor that sends SIGTERM and permits cleanup. Inject secrets through its protected environment. Verify an authenticated upload/export/delete after startup to check browser and font availability. This work supplies deployment code and guidance without publishing or changing a production deployment.
 
 Browser builds must deploy generated lazy PDF chunks alongside the entry bundle. Serve over HTTPS with a content security policy that permits required font/image sources and Blob/data resources. Authentication, durable storage, draft retention and backups remain application-owned.
+
+Install `@onodocs/sdk playwright-core` for server rendering and the HTTP service example. Browser editor sessions use `@onodocs/editor/application` and do not require Playwright.

package/document-collaboration.md

@@ -1,11 +1,12 @@
 # Shared document sessions
 
-Use `@onodocs/sdk/collaboration` for a customer-hosted shared document service and `@onodocs/sdk/collaboration/browser` for the browser editor. Collaboration is optional. Ordinary browser editing and rendering need neither entry point nor a network service.
+Use `@onodocs/sdk/collaboration` for a customer-hosted shared document service and `@onodocs/editor/collaboration` for the browser editor. Collaboration is optional. Ordinary browser editing and rendering need neither entry point nor a network service.
 
 ```ts
 import { createCollaborationService } from "@onodocs/sdk/collaboration";
 
 const service = createCollaborationService({
+  licenseKey,
   authorize: async (documentId, requestContext) => {
     const user = await authenticate(requestContext);
     return await documentPermission(documentId, user);
@@ -29,9 +30,10 @@ import {
   openCollaborativeEditor,
   createCollaborationTransport,
   createCollaborationRecovery,
-} from "@onodocs/sdk/collaboration/browser";
+} from "@onodocs/editor/collaboration";
 
 const session = await openCollaborativeEditor({
+  editor: { document: { licenseKey } },
   container: document.querySelector("main")!,
   exchange: createCollaborationTransport("/documents/brief/collaboration"),
   recovery: createCollaborationRecovery(`${documentId}:${userId}:${tabId}`),
@@ -48,3 +50,5 @@ Synchronization clears local snapshot undo history at each shared checkpoint. Ot
 Use the collaboration composition's editor for authoring. Direct mutations through `editor.document` bypass its journal and are trusted host operations. Opening another document through that editor is also a host lifecycle operation, not a shared replacement; close the session and open the other document's session instead. `WordEditor.synchronize` runs a host callback within the editor queue. Return `{bytes, allowedModes}` to publish a new checkpoint. Never call another queued editor operation from that callback or from an awaited `onChange`; use the underlying document's `save()` when capturing bytes.
 
 Run `npm run example:collaboration` after building. Open `http://127.0.0.1:5195/?user=alex` and `?user=sam` in separate browser profiles, or `?user=jo` for review-only access. The sample uses fixed demo identities, loopback HTTP and a local SQLite database under the user's temporary OnoDocs directory. Replace its identity picker with customer authentication for production. Run `npm run validate:collaboration` for the independent browser feature suite.
+
+Configure the application license on both the service and browser editor as shown above. Self-hosted collaboration is included in the same named-application scope. Omitting a key preserves non-production evaluation behavior. See [licensing](licensing.md).

package/document-forms.md

@@ -38,7 +38,7 @@ Blank answers are `null`. Each field requires a distinct `id` and `tag`, a `labe
 ## Browser filling and authoring
 
 ```js
-import { openForm, createFormDesigner } from "@onodocs/sdk/forms/browser";
+import { openForm, createFormDesigner } from "@onodocs/editor/forms";
 
 const view = await openForm({
   container, input: templateBytes, definition,
@@ -56,7 +56,7 @@ view.dispose();
 
 The designer writes native Word content controls with a protected container and editable contents. These controls remain readable in Word. The form's type rules and read-only policy belong to the host definition. They are not document encryption or a tamper-proof restriction in external editors. Applications accepting submissions should use their trusted definition and enforce their own authorization and validation.
 
-Run `npm run build` followed by `npm run example:forms` for the equipment-request example at localhost port 5192. It supports template and definition downloads, browser-local drafts, and completed DOCX plus answers JSON downloads. Installed packages include `examples/document-forms` and its shared `examples/application/recovery.js`; copy both directories, install `esbuild` and matching SDK/Canvas packages, and run `node examples/document-forms/serve.mjs`. No hosted service is required.
+Run `npm run build` followed by `npm run example:forms` for the equipment-request example at localhost port 5192. It supports template and definition downloads, browser-local drafts, and completed DOCX plus answers JSON downloads. The Editor package includes the form example and its shared recovery helper; install `@onodocs/editor esbuild` and run `node node_modules/@onodocs/editor/examples/document-forms/serve.mjs`. No hosted service is required.
 
 ## Try the equipment-request workflow
 
@@ -72,11 +72,11 @@ Drafts use the shared IndexedDB recovery example. The storage key includes a dig
 
 Open **Developer tools & template authoring** to edit the template, import a Word document and matching definition, or download both source files. Authoring intentionally permits document changes; the filling preview only permits the defined answers. Field changes create a separate draft identity. This panel is an evaluation tool, not a user authorization boundary.
 
-To run the shipped example directly from an installed SDK:
+To run the shipped example directly from an installed Editor package:
 
 ```powershell
-npm install @onodocs/sdk esbuild
-node node_modules/@onodocs/sdk/examples/document-forms/serve.mjs
+npm install @onodocs/editor esbuild
+node node_modules/@onodocs/editor/examples/document-forms/serve.mjs
 ```
 
 Evaluation mode adds a watermark. For licensed use, provide the license key in the `document` options passed to both `openForm` and `createFormDesigner`, following the SDK licensing guide.

package/document-modes.md

@@ -12,7 +12,7 @@ Configure `createEditor` or `openApplicationEditor` with `mode` and `allowedMode
 Save and PDF export are available in every mode. Review mode requires `review` options, including the host's reviewer identity callback. Form mode requires a `FormDefinition`. [Document forms](document-forms.md) describes field rules and answer types. [Application integration](application-integration.md) describes saving, recovery and host lifecycle.
 
 ```js
-import { openApplicationEditor } from "@onodocs/sdk/application";
+import { openApplicationEditor } from "@onodocs/editor/application";
 
 const application = await openApplicationEditor({
   container, input: bytes,
@@ -41,4 +41,4 @@ History is retained across modes. Viewing cannot undo or redo. Form and review m
 
 Derive the allowed modes from your application's permissions. This is an interface and editor-operation policy, not application authorization, file encryption or a restriction on external Word editors. The low-level `editor.document` API remains available to trusted application code and is not filtered by editor mode. The host must authorize storage, review identity, history and submissions. If permissions change, preserve permitted draft work and create a session with the new allowed modes; merely switching to viewing does not revoke modes already offered by that session.
 
-Run `npm run build` and `npm run example:modes` for the local four-mode request at port 5196. Its Save draft stores bytes only in memory for the current session. The installed SDK includes `examples/document-modes` and its shared `document-forms` server/template files. Copy both directories, install matching SDK/Canvas packages and `esbuild`, then run `node examples/document-modes/serve.mjs`.
+Run `npm run build` and `npm run example:modes` for the local four-mode request at port 5196. Its Save draft stores bytes only in memory for the current session. The Editor package includes the mode example and its shared form assets. Install `@onodocs/editor esbuild`, then run `node node_modules/@onodocs/editor/examples/document-modes/serve.mjs`.

package/editor.md

@@ -0,0 +1,39 @@
+# OnoDocs Editor
+
+`@onodocs/editor` provides the browser editor, template and form authoring, review controls, application sessions and collaborative editing UI. It uses the public document operations in `@onodocs/sdk` and presentation in `@onodocs/canvas`. Installing Editor installs matching SDK and Canvas versions. OnoDocs-authored Editor code is licensed under MIT, including its UI, application sessions, forms, templates and collaboration client. You may modify and redistribute that code, including in commercial products, while preserving the MIT notice and applicable third-party notices. SDK and Canvas remain separately commercially licensed; their production use requires covered application scope. Editor has no separate entitlement or purchase.
+
+The [editor source](https://github.com/onodocs/onodocs/tree/main/packages/editor) and runnable examples are maintained in the public OnoDocs repository. MIT permission for the editor does not grant production or redistribution rights in its SDK and Canvas dependencies.
+
+```sh
+npm install @onodocs/editor
+```
+
+```js
+import { createEditor } from "@onodocs/editor";
+
+const editor = createEditor({ container, document: { licenseKey } });
+await editor.open(bytes);
+const saved = await editor.save();
+editor.dispose();
+```
+
+Use `createTemplateEditor` from the same entry for template authoring. `@onodocs/editor/application` provides autosave, recovery and host lifecycle. `@onodocs/editor/forms` provides controlled form filling and the form designer. `@onodocs/editor/collaboration` provides the collaborative editor, browser recovery and transport client. The host supplies authentication, persistence and collaboration service endpoints.
+
+`createFormDesigner` includes a Forms tab for adding fields and opening their sidebar settings. Supply `onPreview(designer)` and `onExportProject(designer)` to expose your host's preview and project-export actions there. Both callbacks can call `designer.save()` to obtain matching Word bytes and field rules. Set `ribbon: false` to keep only the standard editor tabs and field sidebar. The complete document-forms example connects these actions to its existing fill and ZIP export workflows.
+
+The installed package includes complete browser-editor, template-editor, proposal, form, agreement-review, document-mode and collaboration examples. Install `esbuild`, then run `node node_modules/@onodocs/editor/examples/browser-editor/serve.mjs` to start the standalone editor. See the SDK guide and the included workflow guides for supported document operations and limitations.
+
+## Migration from 0.4
+
+| Previous import | Current import |
+| --- | --- |
+| `@onodocs/sdk/editor` | `@onodocs/editor` |
+| `@onodocs/sdk/application` | `@onodocs/editor/application` |
+| `@onodocs/sdk/forms/browser` | `@onodocs/editor/forms` |
+| `@onodocs/sdk/collaboration/browser` | `@onodocs/editor/collaboration` |
+
+Function names and supported behavior remain the same. The previous SDK entry points are removed. Document operations stay in `@onodocs/sdk`, `/browser` and `/server`. Form definitions, answers and validation stay in `@onodocs/sdk/forms`; the collaboration service and protocol stay in `@onodocs/sdk/collaboration`. HTTP integration stays in `@onodocs/sdk/http`. Canvas imports remain unchanged.
+
+For backend rendering, install `@onodocs/sdk playwright-core` and provide a Chromium-family browser. Playwright is an optional SDK peer dependency; browser and data-only installations do not need it. The server adapter, HTTP service, form data operations and collaboration service have independent entry points and do not load the editor UI.
+
+One named-application license covers commercial SDK and Canvas use, including the application's backend and self-hosted collaboration. Finished editors for end users are included. Editor source remains available under MIT. See [application scope, output rights and redistribution terms](licensing.md).

package/index.js

@@ -2365,7 +2365,7 @@ function mountDocument(document2, container, options = {}, onDispose) {
       const [anchorX, anchorY, elementX, elementY] = placementPoints[options2.placement ?? "overlay"];
       const x = r.x + anchorX * r.width - elementX * size.width + (1 - 2 * anchorX) * inset + (anchorX - elementX) * gap2 + (options2.offset?.x ?? 0);
       const y = r.y + anchorY * r.height - elementY * size.height + (1 - 2 * anchorY) * inset + (anchorY - elementY) * gap2 + (options2.offset?.y ?? 0);
-      Object.assign(box.style, { position: "absolute", left: "0", top: "0", width: `${size.width * cssScale}px`, height: `${size.height * cssScale}px`, transformOrigin: "0 0", transform: `matrix(${t.a},${t.b},${t.c},${t.d},${(t.a * x + t.c * y + t.e) * cssScale},${(t.b * x + t.d * y + t.f) * cssScale})`, pointerEvents: "auto" });
+      Object.assign(box.style, { position: "absolute", left: "0", top: "0", width: `${size.width * cssScale}px`, height: `${size.height * cssScale}px`, transformOrigin: "0 0", transform: `matrix(${t.a},${t.b},${t.c},${t.d},${(t.a * x + t.c * y + t.e) * cssScale},${(t.b * x + t.d * y + t.f) * cssScale})`, pointerEvents: options2.interactive === false ? "none" : "auto" });
       attachedElements.get(node)?.dispose();
       const oldStyle = node.getAttribute("style");
       Object.assign(node.style, { width: "100%", height: "100%", boxSizing: "border-box", margin: "0" });
@@ -2546,7 +2546,11 @@ function createDocument(source, options = {}) {
   const lifetime = new AbortController();
   const views = /* @__PURE__ */ new Set();
   const faces = /* @__PURE__ */ new Map();
-  const ownedFaces = /* @__PURE__ */ new Set();
+  const fontCleanup = /* @__PURE__ */ new Set();
+  const fontFinalizer = new FinalizationRegistry((close) => {
+    close();
+    fontCleanup.delete(close);
+  });
   let pages = [];
   let disposed = false;
   let mounted;
@@ -2569,6 +2573,9 @@ function createDocument(source, options = {}) {
     },
     refresh() {
       checkOpen();
+      const fonts = createFontResources(faces, checkOpen);
+      fontCleanup.add(fonts.dispose);
+      fontFinalizer.register(fonts, fonts.dispose);
       pages = source.pages.map((page) => ({ index: page.index, size: page.size, get interaction() {
         return page.interaction;
       }, async render(canvas, options2 = {}) {
@@ -2579,7 +2586,7 @@ function createDocument(source, options = {}) {
         if (!Number.isFinite(dpi) || dpi <= 0) throw new RangeError("dpi must be positive and finite.");
         const data = await page.load(signal);
         signal.throwIfAborted();
-        await Promise.all((data.fonts ?? []).map(loadFont));
+        await Promise.all((data.fonts ?? []).map((resource) => fonts.load(resource)));
         signal.throwIfAborted();
         const images = data.images && await materializeImageResources(data.images, signal);
         try {
@@ -2608,10 +2615,9 @@ function createDocument(source, options = {}) {
       lifetime.abort();
       unsubscribe?.();
       for (const view of views) view.dispose();
-      for (const face of ownedFaces) document.fonts.delete(face);
+      for (const close of fontCleanup) close();
       views.clear();
-      ownedFaces.clear();
-      faces.clear();
+      fontCleanup.clear();
     }
   };
   unsubscribe = source.subscribe?.(() => source.disposed ? result.dispose() : result.refresh());
@@ -2627,24 +2633,52 @@ function createDocument(source, options = {}) {
     if (disposed || source.disposed) throw new Error("Canvas document is disposed.");
   }
   __name(checkOpen, "checkOpen");
-  function loadFont(resource) {
+}
+__name(createDocument, "createDocument");
+function createFontResources(faces, checkOpen) {
+  const acquired = /* @__PURE__ */ new Map();
+  let disposed = false;
+  function load(resource) {
+    checkOpen();
+    if (disposed) return Promise.reject(new Error("Canvas font resources are disposed."));
     const key = JSON.stringify([resource.family, resource.descriptors]);
-    let pending = faces.get(key);
-    if (!pending) {
+    let entry = faces.get(key);
+    if (!entry) {
       const face = new FontFace(resource.family, typeof resource.source === "string" ? resource.source : resource.source.slice().buffer, resource.descriptors);
-      pending = face.load().then(() => {
+      const pending = { face, users: 0, ready: face.load().then(() => {
         checkOpen();
-        document.fonts.add(face);
-        ownedFaces.add(face);
-      });
+        if (pending.users) document.fonts.add(face);
+      }) };
       faces.set(key, pending);
-      void pending.catch(() => faces.delete(key));
+      entry = pending;
+      void pending.ready.catch(() => {
+        if (faces.get(key) === pending) faces.delete(key);
+      });
+    }
+    const previous = acquired.get(key);
+    if (previous !== entry) {
+      if (previous) release(key, previous);
+      acquired.set(key, entry);
+      entry.users++;
     }
-    return pending;
+    return entry.ready;
   }
-  __name(loadFont, "loadFont");
+  __name(load, "load");
+  function release(key, entry) {
+    if (--entry.users === 0) {
+      document.fonts.delete(entry.face);
+      if (faces.get(key) === entry) faces.delete(key);
+    }
+  }
+  __name(release, "release");
+  return { load, dispose() {
+    if (disposed) return;
+    disposed = true;
+    for (const [key, entry] of acquired) release(key, entry);
+    acquired.clear();
+  } };
 }
-__name(createDocument, "createDocument");
+__name(createFontResources, "createFontResources");
 async function openDocument(url, options = {}) {
   const endpoint = new URL(url, document.baseURI);
   const manifest = await load(endpoint, options.signal);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@onodocs/canvas",
-  "version": "0.4.0",
+  "version": "0.5.1",
   "private": false,
   "description": "OnoDocs canvas viewer, selection and HTML attachments for prepared Word document pages.",
   "homepage": "https://onodocs.com/developers/",
@@ -33,6 +33,7 @@
     "types",
     "README.md",
     "SDK.md",
+    "editor.md",
     "templates.md",
     "proposal.md",
     "agreement-review.md",
@@ -48,5 +49,5 @@
     "type": "git",
     "url": "https://github.com/onodocs/onodocs.git"
   },
-  "gitHead": "3227556064a15863db186152f40ee94cff0a7d9b"
+  "gitHead": "a4043b6b334e0090f9cc2439d74120357a59aa76"
 }

package/proposal.md

@@ -11,14 +11,14 @@ npm run example:proposal
 
 Open `http://127.0.0.1:5196`. Use `PORT` to choose another local port.
 
-## Run from an installed SDK
+## Run from an installed Editor
 
 ```powershell
-npm install @onodocs/sdk esbuild
-node node_modules/@onodocs/sdk/examples/proposal/serve.mjs
+npm install @onodocs/editor esbuild
+node node_modules/@onodocs/editor/examples/proposal/serve.mjs
 ```
 
-The SDK includes the HTML, CSS, JavaScript and reusable `sample.docx`. Evaluation mode adds a watermark. For licensed use, pass your license key in the browser options supplied to both `openTemplate` and `createEditor` in `main.js`, following the SDK licensing guide.
+The Editor package includes the HTML, CSS, JavaScript and reusable `sample.docx`. Evaluation mode adds a watermark. For licensed use, pass your license key in the browser options supplied to both `openTemplate` and `createEditor` in `main.js`, following the SDK licensing guide.
 
 ## Try the workflow
 

package/templates.md

@@ -1,11 +1,11 @@
 # Word templates and document generation
 
-Use `createTemplateEditor` from `@onodocs/sdk/editor` to design reusable DOCX templates. Run `npm run example:templates` in the source workspace for the invoice example at localhost port 5193. The designer uses the ordinary Word editor for layout, formatting and generated-document adjustments.
+Use `createTemplateEditor` from `@onodocs/editor` to design reusable DOCX templates. Run `npm run example:templates` in the source workspace for the invoice example at localhost port 5193. The designer uses the ordinary Word editor for layout, formatting and generated-document adjustments.
 
 For a complete business-data-to-export journey, run `npm run example:proposal`. The [proposal studio guide](proposal.md) covers setup, repeating fee rows, wording edits and Word/PDF downloads.
 
 ```ts
-import { createTemplateEditor } from "@onodocs/sdk/editor";
+import { createTemplateEditor } from "@onodocs/editor";
 
 const designer = createTemplateEditor({
   container: document.querySelector("#templates"),
@@ -64,7 +64,7 @@ The command supports `selection`, `paragraph`, `row` and `table` scopes. Inline
 | `section` | `name` | Reusable content definition, omitted from output |
 | `include` | `name`, optional `path` | Section inserted with the current context or selected subrecord |
 
-Paths are arrays of own-property names, not executable expressions. An empty path selects the current record. Missing data, wrong value types and recursive sections report an error. Currency options are ordinary `Intl.NumberFormatOptions`, for example `{ style: "currency", currency: "USD" }`. Date values can be a `Date`, timestamp or ISO date string; use an explicit offset for timestamps. The default locale is `en-US` and the default date time zone is UTC.
+Paths are arrays of own-property names, not executable expressions. An empty path selects the current record. Missing data, wrong value types and recursive sections report an error. Currency options are ordinary `Intl.NumberFormatOptions`, for example `{ style: "currency", currency: "USD" }`. Date values can be a `Date`, timestamp or ISO date string; use an explicit offset for timestamps. Formatting uses JavaScript `Date` conversion and rejects invalid timestamps. It does not strictly validate calendar strings: for example, `2026-02-30` converts to 2 March 2026. Validate calendar dates in the host application if strict rejection is required. The default locale is `en-US` and the default date time zone is UTC.
 
 Formatting comes from the first run of a text placeholder. Unrelated Word content and package resources are preserved. Generation refreshes supported sequence and bookmark-reference fields. The browser template API also lays out the generated document to refresh page numbers, page references and supported tables of contents. Node callers can supply a `finalize` callback that opens the generated bytes with the server renderer and returns `document.save(options)`.
 

package/types/canvas/presentation.d.ts

@@ -21,6 +21,7 @@ export type AttachmentOptions = Readonly<{
     anchor: ViewAnchor;
     offset?: DocumentPoint;
     size?: PageSize;
+    interactive?: boolean;
 }> & (Readonly<{
     placement?: "overlay";
     inset?: never;

package/types/render-api/page-display-list.d.ts

@@ -7,6 +7,10 @@ import type { GeometryPathOperation } from "../foundation/index.js";
 /** Spec: spec/document/body/drawing/vml/gradient-fills.md */
 /** Spec: `spec/pipeline/render/page-display-list/_index.md`; `spec/pipeline/render/page-display-list/positioned-text/shading.md#positioned-text-shading-compilation`; `spec/pipeline/render/page-display-list/positioned-text/highlight.md#highlight-command-compilation`; `spec/pipeline/render/page-display-list/positioned-text/decoration.md#strike-command-compilation`. */
 import type { RasterColorEffectPlan, RasterSourceRectangle, VectorShapeFill, VectorShapePath } from "../foundation/index.js";
+/** Spec: pipeline.render.page-display-list.comment-projection */
+export interface PageDisplayListOptions {
+    readonly commentDisplay?: "markers" | "hidden";
+}
 export interface PaintRectangle {
     readonly x: bigint;
     readonly y: bigint;