@arbidocs/blocks 0.4.101 → 0.4.102

package/node_modules/@docx-editor.dev/core/dist/contracts/interaction.d.ts

@@ -0,0 +1,103 @@
+/**
+ * `@docx-editor.dev/core/contracts/interaction` — semantic addressing and interaction outcomes.
+ *
+ * Semantic identities and targets: the vocabulary a caller uses to say WHICH text it means,
+ * independent of layout, DOM or any editing engine's positions. Plus the outcome type an
+ * interaction attempt answers with. That is the whole module.
+ *
+ * It used to be 599 lines. An "interaction frame" lived here — a revision-tagged projection
+ * of display, page geometry, caret and selection overlays, focus, composition and
+ * accessibility, plus a typed pointer-intent dispatch protocol and a render IR of glyph
+ * runs — and every one of those declarations was consumed by exactly nothing. They
+ * described an architecture the engine does not use: the paginated surface owns pointer
+ * interaction internally and paints through `Editor.attach`, so no frame was ever published
+ * and no intent ever dispatched.
+ * THREE of them (`CaretGeometry`, `HitTestOptions`, `ShapedCluster`) also collided by name
+ * with the REAL, differently-shaped types in `layout/`, so the published contract carried a
+ * second definition of a live concept and `import { ShapedCluster }` meant different things
+ * depending on which module you reached for.
+ * `InteractionFrameId` and a frame-tagged `SemanticSelection` outlived that cut. Both were
+ * the same mistake: the id was a placeholder nothing ever minted (`focus` returned a literal
+ * `{ value: 0 }`), and the selection could not be CONSTRUCTED without one, which made it a
+ * fourth name-collision with the real `SemanticSelection` in `layout/` that a caller could
+ * never actually satisfy.
+ *
+ * CONTRACT ONLY — declarations, not an implementation.
+ *
+ * @packageDocumentation
+ * @public
+ */
+import { V as ViewScope } from '../editor-scope-OHPwVQ5l.js';
+export { E as EditorScope } from '../editor-scope-OHPwVQ5l.js';
+
+/**
+ * `@docx-editor.dev/core/contracts/interaction` — semantic addressing and interaction outcomes.
+ *
+ * Semantic identities and targets: the vocabulary a caller uses to say WHICH text it means,
+ * independent of layout, DOM or any editing engine's positions. Plus the outcome type an
+ * interaction attempt answers with. That is the whole module.
+ *
+ * It used to be 599 lines. An "interaction frame" lived here — a revision-tagged projection
+ * of display, page geometry, caret and selection overlays, focus, composition and
+ * accessibility, plus a typed pointer-intent dispatch protocol and a render IR of glyph
+ * runs — and every one of those declarations was consumed by exactly nothing. They
+ * described an architecture the engine does not use: the paginated surface owns pointer
+ * interaction internally and paints through `Editor.attach`, so no frame was ever published
+ * and no intent ever dispatched.
+ * THREE of them (`CaretGeometry`, `HitTestOptions`, `ShapedCluster`) also collided by name
+ * with the REAL, differently-shaped types in `layout/`, so the published contract carried a
+ * second definition of a live concept and `import { ShapedCluster }` meant different things
+ * depending on which module you reached for.
+ * `InteractionFrameId` and a frame-tagged `SemanticSelection` outlived that cut. Both were
+ * the same mistake: the id was a placeholder nothing ever minted (`focus` returned a literal
+ * `{ value: 0 }`), and the selection could not be CONSTRUCTED without one, which made it a
+ * fourth name-collision with the real `SemanticSelection` in `layout/` that a caller could
+ * never actually satisfy.
+ *
+ * CONTRACT ONLY — declarations, not an implementation.
+ *
+ * @packageDocumentation
+ * @public
+ */
+
+/** Bidi/grapheme affinity for a text caret or hit target. */
+type InteractionAffinity = 'upstream' | 'downstream';
+/**
+ * Model-derived stable identity within a scope. Positions resolve through this
+ * index, not accumulated display-item lengths or editing-engine coordinates.
+ */
+interface SemanticIdentity {
+    readonly storyId: string;
+    readonly blockId: string;
+}
+/** A PM-free semantic caret, range endpoint, or atomic selection target. */
+type SemanticTarget = {
+    readonly kind: 'text';
+    readonly scope: ViewScope;
+    readonly identity: SemanticIdentity;
+    readonly graphemeOffset: number;
+    readonly affinity: InteractionAffinity;
+} | {
+    readonly kind: 'atomic';
+    readonly scope: ViewScope;
+    readonly objectId: string;
+};
+/** Typed rejection for pending, read-only, invalid, or unsupported interaction. */
+type InteractionOutcomeCode = 'pendingLayout' | 'pendingSelection' | 'readOnly' | 'invalidTarget' | 'unsupported';
+/**
+ * The result of one interaction attempt.
+ *
+ * A rejection carries the ENGINE's own `reason`, which is what lets a caller surface why an
+ * interaction was refused instead of guessing.
+ */
+type InteractionOutcome<T> = {
+    readonly ok: true;
+    readonly value: T;
+} | {
+    readonly ok: false;
+    readonly code: InteractionOutcomeCode;
+    readonly reason: string;
+};
+
+export { ViewScope };
+export type { InteractionAffinity, InteractionOutcome, InteractionOutcomeCode, SemanticIdentity, SemanticTarget };

package/node_modules/@docx-editor.dev/core/dist/contracts/modules.cjs

@@ -0,0 +1 @@
+'use strict';var chunkNBCVVZOM_cjs=require('../chunk-NBCVVZOM.cjs');Object.defineProperty(exports,"resolveEditorModules",{enumerable:true,get:function(){return chunkNBCVVZOM_cjs.a}});

package/node_modules/@docx-editor.dev/core/dist/contracts/modules.d.ts

@@ -0,0 +1,143 @@
+/**
+ * `@docx-editor.dev/core/contracts/modules` — the `EditorModule` seam.
+ *
+ * How a paid or optional capability contributes to the engine without the free tier importing
+ * it: the review module and custom nodes both arrive through here, and their absence leaves the
+ * corresponding chrome disabled with the engine's own reason.
+ *
+ * NOT a plugin system. The shape is closed: every contribution point is named
+ * here, core iterates registered modules at its existing dispatch points, and
+ * core never imports a capability package. A capability absent from this file
+ * is not extendable from outside — deliberately, so the one-pipeline principle
+ * survives the packaging boundary.
+ * The free engine behaves identically with an empty registry: documents
+ * round-trip losslessly, revisions render in their final-state projection, and
+ * the review chrome slots stay disabled with the engine's own reason.
+ *
+ * @packageDocumentation
+ * @public
+ */
+import { R as RevisionMarkupDialogSession, a as ReviewDisplayMode } from '../revision-projection-DZ4kKVev.js';
+export { b as RevisionDisplayMode } from '../revision-projection-DZ4kKVev.js';
+import { R as ReviewPaneOptions } from '../review-pane-D9jm8DcY.js';
+import { R as ReviewModelInput, a as ReviewItem, O as OoxmlPart, b as ReviewRevisionItem } from '../types-barrel-D3xCgQX6.js';
+export { C as CommentRecord, c as ReviewCommentItem, d as ReviewCustomItem, e as ReviewPosition, f as ReviewRange, g as ReviewRevisionKind, h as RevisionAddress } from '../types-barrel-D3xCgQX6.js';
+import { CollaborationModuleContribution } from '../collaboration.js';
+import '../editor-scope-OHPwVQ5l.js';
+import '../tree-package-fragment-BeeKxDw8.js';
+import '../image-resources-BN-hUgCn.js';
+import '../collaboration/replication.js';
+import '../failure-NS2lsya4.js';
+
+/**
+ * Derives the review queue — every pending revision decision and comment
+ * thread — from one story part plus its comment parts. Implemented by the pro
+ * review module; the free engine has no implementation and reports an empty
+ * queue.
+ *
+ * @public
+ */
+type CollectReviewItems = (input: ReviewModelInput) => readonly ReviewItem[];
+/** Viewer settings dialog supplied by the review module. @public */
+interface RevisionMarkupDialog {
+    open(): void;
+    destroy(): void;
+}
+/** Local settings access for review chrome. No document mutations occur here. @public */
+interface RevisionMarkupDialogHost extends RevisionMarkupDialogSession {
+    readonly container: HTMLElement;
+    readonly translate?: (key: string) => string | undefined;
+}
+/**
+ * What a review module contributes: the queue derivation, and the revision
+ * display modes the editor may enter beyond the free tier's final-state
+ * projection.
+ *
+ * @public
+ */
+interface ReviewModuleContribution {
+    /** Create local review settings chrome when a host opens the dialog. */
+    readonly createRevisionMarkupDialog?: (host: RevisionMarkupDialogHost) => RevisionMarkupDialog;
+    /**
+     * Display modes this module unlocks (the free engine renders `proposed` only).
+     *
+     * The module enables the listed review projections.
+     */
+    readonly displayModes: readonly ReviewDisplayMode[];
+    /**
+     * The review pane settings the editor starts with. `setReviewPaneOptions` changes them later.
+     */
+    readonly pane?: ReviewPaneOptions;
+    /** The review queue derivation. */
+    readonly collectReviewItems: CollectReviewItems;
+    /**
+     * Revisions wholly inside one paragraph — for the conservative local review
+     * patch after a text-local body edit.
+     */
+    readonly revisionItemsOfParagraph: (part: OoxmlPart, paragraphId: string) => readonly ReviewRevisionItem[];
+}
+
+/**
+ * One registered capability module. Registration is construction-time
+ * (`createDocxEditor({ modules })`) and immutable for the instance's lifetime.
+ *
+ * @public
+ */
+interface EditorModule {
+    /** Diagnostic identity (`'review'`, `'custom-nodes'`); not a dispatch key. */
+    readonly id: string;
+    /** Review capability: queue derivation, commands gate, display modes. */
+    readonly review?: ReviewModuleContribution;
+    /**
+     * Collaboration replica. Absent, the editor stays single-user: local undo
+     * stays the authority, and `snapshot().collaborationStatus` is `'inactive'`.
+     */
+    readonly collaboration?: CollaborationModuleContribution;
+    /**
+     * Custom inline node definitions. Reserved: the definition shape lands with
+     * the custom-nodes lane; the registry carries them opaquely until then.
+     */
+    readonly customNodes?: readonly unknown[];
+    /**
+     * customXml payload namespaces this module OWNS, swept for orphans when a document opens.
+     *
+     * A payload lives in a customXml data part, and Word will not delete one when a user deletes
+     * the control bound to it — nothing in OOXML asks it to. So a document can arrive holding
+     * payloads for chips that no longer exist, and reconciling against what the story actually
+     * binds is the only thing that collects them.
+     *
+     * The claim is what keeps the sweep off other people's stores: Word's own Cover Page
+     * Properties store rides in most templates, and a sweep that walked every customXml part
+     * would be deleting from it on the strength of a name collision. A namespace no module names
+     * is never touched.
+     */
+    readonly customNodePayloadNamespaces?: readonly string[];
+    /**
+     * Told when the recognition pass finds something wrong with a node in THIS editor's document.
+     *
+     * Carried per module rather than kept by the capability package, so two editors on one page
+     * hear only their own documents and a detached editor's listener goes with it. The shape is
+     * opaque here for the same reason `customNodes` is: what a diagnostic means belongs to the
+     * package that raised it.
+     */
+    readonly onCustomNodeDiagnostic?: (diagnostic: unknown) => void;
+}
+/**
+ * The resolved registry the editor instance holds: at most one review
+ * contribution and at most one collaboration contribution (first registration
+ * wins for each), all custom node definitions in registration order.
+ */
+interface EditorModuleRegistry {
+    readonly review: ReviewModuleContribution | null;
+    readonly collaboration: CollaborationModuleContribution | null;
+    readonly customNodes: readonly unknown[];
+    /** Every claimed payload namespace, deduplicated, in registration order. */
+    readonly customNodePayloadNamespaces: readonly string[];
+    /** Every registered diagnostic listener, in registration order. */
+    readonly customNodeDiagnostics: readonly ((diagnostic: unknown) => void)[];
+}
+/** Resolve construction-time modules into the registry the instance dispatches over. */
+declare function resolveEditorModules(modules: readonly EditorModule[] | undefined): EditorModuleRegistry;
+
+export { CollaborationModuleContribution, OoxmlPart, ReviewDisplayMode, ReviewItem, ReviewModelInput, ReviewRevisionItem, resolveEditorModules };
+export type { CollectReviewItems, EditorModule, EditorModuleRegistry, ReviewModuleContribution, RevisionMarkupDialog, RevisionMarkupDialogHost };

package/node_modules/@docx-editor.dev/core/dist/contracts/modules.js

@@ -0,0 +1 @@
+export{a as resolveEditorModules}from'../chunk-O5INAWZQ.js';

package/node_modules/@docx-editor.dev/core/dist/contracts/types.cjs

@@ -0,0 +1 @@
+'use strict';

package/node_modules/@docx-editor.dev/core/dist/contracts/types.d.ts

@@ -0,0 +1,11 @@
+/**
+ * `@docx-editor.dev/core/contracts/types` — the shared type vocabulary. Zero runtime.
+ *
+ * Addressing (`DocAnchor`, `DocTarget`), the document model, and the geometry primitives every
+ * other contract is written in terms of.
+ *
+ * @packageDocumentation
+ * @public
+ */
+export { B as Block, r as ColorValue, m as ContainerRef, s as ContentControl, n as ContentControlFilter, i as ContentControlType, t as DocAnchor, u as DocAnchorRange, q as DocComment, v as DocLocation, o as DocRange, j as DocTarget, w as DocumentBody, D as DocxDocument, av as DocxDocumentJSON, x as ExecErrorCode, E as ExecResult, l as Extent, ay as FontDefinition, H as HeaderFooterSet, y as IndentFormatting, I as InsertableContentControlType, az as NumberingRef, aA as PageMargins, P as Paragraph, aB as ParagraphDisagreements, z as ParagraphFlags, aq as ParagraphFormatCommand, A as ParagraphTabStop, aC as Point, as as Rect, p as Revision, F as RevisionType, aD as Run, k as RunFormatting, G as Section, J as SectionProperties, at as SelectionPin, K as StyleDefinition, S as StyleDefinitions, T as Table, aE as TableCell, aF as TableRow, L as Theme, M as ThemeColorScheme, au as Unsubscribe, ar as Watermark } from '../types-barrel-D3xCgQX6.js';
+import '../editor-scope-OHPwVQ5l.js';

package/node_modules/@docx-editor.dev/core/dist/custom-node-writes-cvL5rhcD.d.ts

@@ -0,0 +1,323 @@
+import { Q as OoxmlPackage, O as OoxmlPart, N as OoxmlNode, a8 as TreeOpRejection } from './types-barrel-D3xCgQX6.js';
+import { e as TreeModelChange, f as TreeDocumentStore } from './tree-package-fragment-BeeKxDw8.js';
+
+/** Which of a family's four faces an embedded font relationship supplies. */
+type FontStyleKey = 'regular' | 'bold' | 'italic' | 'boldItalic';
+/**
+ * One font whose bytes travel inside the package.
+ *
+ * The family name is the DOCUMENT's and is not validated — it is attacker-controlled, so it is
+ * escaped into CSS and never registered globally on `document.fonts`, where it would shadow the
+ * host application's own fonts.
+ */
+interface EmbeddedFont {
+    /** The family as the document names it. Not validated against anything. */
+    readonly family: string;
+    readonly style: FontStyleKey;
+    /** Deobfuscated bytes, ready to be offered to a font validator. */
+    readonly bytes: Uint8Array;
+    /** The part they came from, for diagnostics. */
+    readonly partName: string;
+}
+/**
+ * Undo Word's embedded-font obfuscation (ECMA-376 Part 4 §2.8.1).
+ *
+ * The key is the `w:fontKey` GUID's 16 bytes in REVERSED order — not the per-group
+ * little-endian reading a GUID usually gets. It is XORed over the first 32 bytes of the
+ * part, applied twice. Getting the order wrong produces a font that looks corrupt rather
+ * than obfuscated, which is indistinguishable from a damaged file at the point it fails.
+ *
+ * Pure XOR, so the same operation obfuscates and deobfuscates.
+ */
+declare function deobfuscateFont(bytes: Uint8Array, fontKey: string): Uint8Array | null;
+/** Limits and instrumentation for reading embedded fonts out of a package. */
+interface ReadEmbeddedFontsOptions {
+    /** Refuse a font part larger than this. Defaults to 16 MB. */
+    readonly maxFontBytes?: number;
+    /** Refuse more than this many fonts. Defaults to 64. */
+    readonly maxFonts?: number;
+}
+/**
+ * Every font the package embeds, deobfuscated.
+ *
+ * Silently skips anything malformed rather than rejecting the document: a broken font table
+ * is a reason to fall back to substitution, never a reason to refuse to open the file.
+ */
+declare function readEmbeddedFonts(pkg: OoxmlPackage, fontTable: OoxmlPart | undefined, options?: ReadEmbeddedFontsOptions): EmbeddedFont[];
+
+/** The two list kinds a toolbar offers. */
+type ListKind = 'bullet' | 'ordered';
+interface EnsuredListDefinition {
+    readonly pkg: OoxmlPackage;
+    /** The `w:numId` a paragraph's `w:numPr` should name. */
+    readonly numId: string;
+}
+/**
+ * Find or create a list definition of `kind`, returning the package that holds it.
+ *
+ * An existing abstract definition of the same kind is reused, but every disconnected list
+ * gets a fresh `w:num` instance. Counters belong to `w:num`, so reusing that instance would
+ * continue an earlier list. Returns null only when the part cannot be built at all.
+ */
+declare function ensureListDefinition(pkg: OoxmlPackage, kind: ListKind): EnsuredListDefinition | null;
+/**
+ * Declare `level` in the definition `numId` names, with Word's default format for that
+ * level, or refuse.
+ *
+ * Word never greys Increase Indent out on a list item: demoting past the deepest level a
+ * `w:abstractNum` declares makes Word DEFINE the level, cycling its stock bullets
+ * (Symbol •, Courier `o`, Wingdings ▪) or number formats (decimal, lowerLetter,
+ * lowerRoman) by depth. This is that write. An already-declared level returns the package
+ * unchanged, so callers may ask first and act second without a second lookup.
+ *
+ * A delegating definition (`w:numStyleLink`, 17.9.21) is refused: its levels live on the
+ * linked style's definition, and a `w:lvl` grafted here would be shadowed the moment the
+ * link resolves.
+ */
+declare function ensureNumberingLevel(pkg: OoxmlPackage, numId: string, level: number, kind: ListKind): OoxmlPackage | null;
+
+/** One bookmark's name and the range its marker pair currently encloses. */
+interface BookmarkAnchor {
+    readonly name: string;
+    /** Canonical node id of the paragraph the marker sits in. */
+    readonly paragraphId: string;
+    /** UTF-16 offset within that paragraph, in `paragraphTextOf`'s vocabulary. */
+    readonly offset: number;
+}
+/** Bookmarks by name. A name the document declares twice resolves to the first in order. */
+type BookmarkIndex = ReadonlyMap<string, BookmarkAnchor>;
+/**
+ * Build `name -> position` for every bookmark start in a part, in document order.
+ *
+ * FIRST IN DOCUMENT ORDER WINS on a duplicate name. Word treats a repeated bookmark name as
+ * the same bookmark and jumps to the first, and the alternative — last-wins — makes a jump
+ * target move when an edit far away happens to duplicate a name.
+ *
+ * The offset is measured the way the ops measure: text of the runs before the marker inside
+ * its own paragraph, hyperlink runs included, so the position a jump places the caret at is a
+ * position `setSelection` accepts.
+ */
+declare function buildBookmarkIndex(part: OoxmlPart): BookmarkIndex;
+
+/** What the document asks for. Every field defaults to "the document said nothing". */
+interface DocumentTrackingSettings {
+    /** `w:trackRevisions` — the document asks for edits to be tracked. */
+    readonly trackRevisions: boolean;
+    /**
+     * `w:documentProtection/@w:edit="trackedChanges"` — tracking may not be turned OFF.
+     *
+     * Advisory. Presenting it as enforcement would be a lie about a file anyone can edit.
+     */
+    readonly restrictedToTrackedChanges: boolean;
+    /**
+     * `w:documentProtection/@w:edit="forms"` enforced — Track Changes is UNAVAILABLE.
+     *
+     * Word refuses to turn tracking on while a document is protected for filling in forms. A
+     * document tracked BEFORE it was protected keeps the revisions it already carries; what the
+     * protection stops is making new ones.
+     */
+    readonly restrictedToForms: boolean;
+    /** `w:documentProtection/@w:edit="readOnly"` enforced — no edit is permitted at all. */
+    readonly restrictedToReadOnly: boolean;
+    /** `w:documentProtection/@w:edit="comments"` enforced — only comments are permitted. */
+    readonly restrictedToComments: boolean;
+    /** `w:doNotTrackMoves` — write a move as a delete and an insert. */
+    readonly doNotTrackMoves: boolean;
+    /** `w:doNotTrackFormatting` — apply formatting without recording a `w:rPrChange`. */
+    readonly doNotTrackFormatting: boolean;
+}
+/** The frozen "nothing is tracked" settings — what a document with no `w:trackChanges` gets. */
+declare const NO_TRACKING_SETTINGS: DocumentTrackingSettings;
+/** Read the tracking settings from a `settings.xml` root, or the defaults when it has none. */
+declare function readTrackingSettings(settingsRoot: OoxmlNode | null | undefined): DocumentTrackingSettings;
+
+/**
+ * The payload half of an insert: which store, which node, and what it holds.
+ *
+ * `data` is opaque here. The lane that owns a schema is the one that declared it, and a store
+ * that parsed payloads would be a second opinion about what a host's node means.
+ */
+interface CustomNodePayloadWrite {
+    /** Namespace of the store's root element — what identifies one store among several. */
+    readonly namespaceUri: string;
+    /** Local name of that root. An NCName; anything else refuses. */
+    readonly rootLocalName: string;
+    /** The node's own id, which the binding's xpath quotes. */
+    readonly nodeId: string;
+    /** The text the control shows. Word paints this from the store, so an empty one is an empty chip. */
+    readonly label: string;
+    /** The payload, serialized. JSON by convention; never parsed here. */
+    readonly data: string;
+}
+/** Where the control goes, what it says, and the payload it carries. */
+interface InsertCustomNodeWrite {
+    readonly paragraphId: string;
+    readonly offset: number;
+    /**
+     * Wrap rather than insert: the text from `offset` to here is removed first.
+     *
+     * The node's label REPLACES the words it covered, because that is what turning a stretch of a
+     * sentence into a citation means. Removed inside the same transaction, so a refused insert
+     * leaves the text where it was.
+     */
+    readonly replaceUntil?: number;
+    /**
+     * Rewrite an existing control: it and the payload it bound go first, in this transaction.
+     *
+     * An UPDATE is remove-and-reinsert, because the tag codec has no in-place rewrite and
+     * pretending it did would put a second write path beside this one. Doing both halves here is
+     * what keeps it one undo step, and what stops an update from leaving a label and a payload
+     * that disagree.
+     */
+    readonly replaceControlId?: string;
+    readonly tag: string;
+    readonly text: string;
+    readonly alias?: string;
+    /** Defaults to none. Callers that want Word's own "cannot type into it" pass `contentLocked`. */
+    readonly lock?: 'sdtLocked' | 'sdtContentLocked' | 'contentLocked';
+    /** Omitted authors an ordinary tagged control with no store — the pre-payload behaviour. */
+    readonly payload?: CustomNodePayloadWrite;
+}
+/**
+ * Why a payload write was refused.
+ *
+ * The tree rejections pass through unchanged, so a locked paragraph refuses a bound insert for
+ * the same named reason it refuses a plain one. The three added here are the payload's own.
+ */
+type CustomNodeWriteRejection = TreeOpRejection
+/** The id, root name or namespace cannot be spelled in an XPath, so no binding could name it. */
+ | 'unaddressable-payload'
+/** The store could not be authored — see `withCustomXmlDataPart` for every way that happens. */
+ | 'store-not-authored'
+/** The payload or the label is past the cap. */
+ | 'payload-too-large';
+type CustomNodeWriteResult = {
+    readonly ok: true;
+    readonly change: TreeModelChange | null;
+    /**
+     * The control this write authored, when it authored one. A rewrite replaces the control
+     * rather than editing it, so the id the caller passed in names nothing afterwards.
+     */
+    readonly nodeId?: string;
+} | {
+    readonly ok: false;
+    readonly reason: CustomNodeWriteRejection;
+    readonly detail?: string;
+};
+/**
+ * The largest payload one node may carry, in UTF-16 code units.
+ *
+ * Same figure as the read side's (`parseCustomNodeData`) and for the same reason: far past any
+ * legitimate chip, far short of anything that hurts. Checked on the WRITE too, so a document
+ * cannot be authored here holding a payload the reader will later refuse to parse.
+ */
+declare const MAX_CUSTOM_NODE_PAYLOAD_LENGTH: number;
+/** The longest label a binding may paint. Word renders it as the control's whole content. */
+declare const MAX_CUSTOM_NODE_LABEL_LENGTH = 4096;
+/**
+ * Insert one custom node, with its payload, as a single transaction.
+ *
+ * Answers the store transaction's own change so the caller can publish it — a payload write is a
+ * package write reaching through a story store, exactly as a comment is, and the coordinator
+ * needs the change to know which paragraphs went dirty.
+ */
+declare function insertCustomNodeWrite(store: TreeDocumentStore, write: InsertCustomNodeWrite, 
+/**
+ * The part the customXml store hangs off, defaulting to the story being written.
+ *
+ * A chip in a header is written against the HEADER store, but Word enumerates the data
+ * store from the main document part — a store authored off a header is one Word never
+ * sees. So the caller passes the main part while the control itself lands in the story.
+ */
+dataOwnerPartName?: string): CustomNodeWriteResult;
+/**
+ * Remove a control and, in the same transaction, the payload it bound.
+ *
+ * The sweep would collect the node eventually — that is what makes deletion in Word survivable —
+ * but "eventually" is the next open, and a document saved in between carries a payload for a
+ * chip that is gone. Doing it here means the ordinary case is exact and the sweep is a backstop.
+ */
+declare function removeCustomNodeWrite(store: TreeDocumentStore, controlNodeId: string): CustomNodeWriteResult;
+/**
+ * What one sweep collected, or why it collected nothing.
+ *
+ * `ok: false` is NOT "the document was already tidy" — that is `ok: true` with an empty
+ * `removed`. It means a store this sweep was asked to tidy refused the rewrite, which a caller
+ * that keeps saving into the same document should know about rather than silently retry forever.
+ */
+type CustomNodeSweepResult = {
+    readonly ok: true;
+    readonly pkg: OoxmlPackage;
+    /** Node ids removed, across every store swept. Empty means there were no orphans. */
+    readonly removed: readonly string[];
+} | {
+    readonly ok: false;
+    readonly reason: string;
+};
+/**
+ * Drop every payload no control binds, in the stores whose namespaces a host claims.
+ *
+ * ON OPEN, NOT ON SAVE. A chip cut to the clipboard is unbound for as long as it sits there, so a
+ * save mid-cut would destroy the payload the user is about to paste. On open the only unbound
+ * nodes are ones a control genuinely lost — deleted here, or deleted in Word, which is the case
+ * nothing else can collect.
+ *
+ * `namespaces` is the claim, and it is what keeps this off other people's stores: Word's own Cover
+ * Page Properties store rides in most templates, and a sweep that walked every customXml part
+ * would be deleting from it on the strength of a name collision.
+ */
+declare function sweepCustomNodePayloads(pkg: OoxmlPackage, storyPartName: string, namespaces: readonly string[]): CustomNodeSweepResult;
+/** One control's payload, as the store holds it. Both strings are untrusted file input. */
+interface CustomNodePayloadRead {
+    /** The store node's own id. */
+    readonly nodeId: string;
+    /** The text Word paints the control from. */
+    readonly label: string;
+    /** The payload as authored. JSON by convention, unparsed here. */
+    readonly data: string;
+}
+/**
+ * The payload every control in a story binds to, keyed by the CONTROL's canonical node id.
+ *
+ * Keyed by the control rather than by the store node because that is the question a reader
+ * actually has — "what does this chip carry" — and because two stores may each hold a `cx1`.
+ * Resolved here rather than by a capability package: the stores are package parts, and a
+ * derivation that only gets story parts has no way to reach them.
+ *
+ * Every store the story relates to, so a document carrying two definitions' payloads answers
+ * for both without anyone naming a namespace.
+ */
+declare function customNodePayloadsByControl(pkg: OoxmlPackage, storyPartName: string, 
+/**
+ * The part that RELATES the customXml store, when it is not the story's own.
+ *
+ * Two different questions wear one name here: which part holds the CONTROLS, and which part
+ * relates the STORE they bind into. Word only reads a store hung off the main document part,
+ * so {@link writeCustomNode} already takes them separately — this read did not, and answered
+ * with the body's controls whatever story it was asked about. A chip in a header therefore
+ * read as having no payload at all, and an update that meant to keep the existing data
+ * dropped it.
+ */
+dataOwnerPartName?: string): ReadonlyMap<string, CustomNodePayloadRead>;
+/** Every payload one store holds, for a caller resolving a control's `data`. */
+declare function customNodePayloadsOf(pkg: OoxmlPackage, storyPartName: string, namespaceUri: string): ReadonlyMap<string, {
+    readonly label: string;
+    readonly data: string;
+}>;
+/**
+ * What the session answers for a sweep: the ids collected, or the reason none were.
+ *
+ * Narrower than {@link CustomNodeSweepResult}, which also carries the rewritten package — the
+ * session has already installed that, and handing it back would invite a caller to install it
+ * twice.
+ */
+type CustomNodeSweepOutcome = {
+    readonly ok: true;
+    readonly removed: readonly string[];
+} | {
+    readonly ok: false;
+    readonly reason: string;
+};
+
+export { MAX_CUSTOM_NODE_LABEL_LENGTH as M, NO_TRACKING_SETTINGS as N, MAX_CUSTOM_NODE_PAYLOAD_LENGTH as g, buildBookmarkIndex as h, customNodePayloadsByControl as i, customNodePayloadsOf as j, deobfuscateFont as k, ensureListDefinition as l, ensureNumberingLevel as m, insertCustomNodeWrite as n, readTrackingSettings as o, removeCustomNodeWrite as p, readEmbeddedFonts as r, sweepCustomNodePayloads as s };
+export type { BookmarkIndex as B, CustomNodeWriteResult as C, DocumentTrackingSettings as D, EmbeddedFont as E, FontStyleKey as F, InsertCustomNodeWrite as I, ListKind as L, ReadEmbeddedFontsOptions as R, CustomNodeSweepOutcome as a, BookmarkAnchor as b, CustomNodePayloadRead as c, CustomNodePayloadWrite as d, CustomNodeSweepResult as e, CustomNodeWriteRejection as f };