@docx-editor.dev/core 2.4.1 → 2.6.0

package/dist/{review-support-DgXTIYBW.d.ts → review-support-D4ZBdUXa.d.ts}

@@ -1,5 +1,5 @@
 import { e as OoxmlPart, a as OoxmlElement } from './ooxml-tree-BU0e3DVi.js';
-import { R as RevisionAddress } from './tree-op-types-8a6xyRCN.js';
+import { R as RevisionAddress } from './tree-op-types-D0fTNBVW.js';
 
 /** The `w15` namespace: `commentsExtended.xml` — thread parent and resolved state. */
 declare const W15_NAMESPACE_URI = "http://schemas.microsoft.com/office/word/2012/wordml";
@@ -101,12 +101,29 @@ interface ReviewRevisionItem {
     /** The words a replacement removes. Empty for every other kind. */
     readonly replacedText: string;
     readonly revisionKind: ReviewRevisionKind;
+    /**
+     * WHICH decision a `paragraphMark` records, absent for every other kind.
+     *
+     * `EG_ParaRPrTrackChanges` is `ins? del? moveFrom? moveTo?`, and the four say opposite
+     * things about one break. Without this a card called a deleted break an inserted one, which
+     * is the reverse of what Accept on that card does.
+     */
+    readonly markDirection?: 'insert' | 'delete' | 'moveFrom' | 'moveTo';
     readonly author: string;
     readonly date?: string;
     /** Text the revision covers, for the card summary. Empty for changes with no characters. */
     readonly text: string;
     /** Every site this decision touches, in document order. */
     readonly ranges: readonly ReviewRange[];
+    /**
+     * How deeply this change is NESTED inside other changes, 0 for an unenclosed one.
+     *
+     * `w:ins` wrapping `w:del` is content one reviewer added and another struck. Both stay
+     * pending, so both are cards, over one identical range — and a range then cannot say which
+     * change a caret is in. Word treats the innermost as the operative one, so it wins the caret
+     * and the change enclosing it stays listed and reachable.
+     */
+    readonly nesting: number;
     /**
      * How many leading `ranges` are the STRUCK half of a replacement.
      *
@@ -321,8 +338,28 @@ interface ReviewParagraphAnchor {
         readonly box: {
             readonly y: number;
         };
+        /**
+         * Present on a real line. A merged fragment's join line carries spans from two
+         * paragraphs, and its `range` can only name one of them, so the OTHER paragraph's extent
+         * on that line is readable here and nowhere else.
+         */
+        readonly spans?: readonly {
+            readonly range: {
+                readonly paragraphId: string;
+                readonly end: number;
+            };
+        }[];
     }[];
 }
+/**
+ * The y of the line a position sits on, measured from the anchor's own origin.
+ *
+ * An ordinary line answers from its own range, exactly as it always did. On a merged
+ * fragment's join line the range names one of the two paragraphs, so an offset compared
+ * against it either overshot — putting a card in the absorbed half beside the wrong line —
+ * or matched the first line every time.
+ */
+declare function anchorLineY(anchor: ReviewParagraphAnchor, paragraphId: string, offset: number): number;
 /**
  * Paragraph id to its place on the page, in ONE pass over the layout.
  *
@@ -350,6 +387,13 @@ declare function reviewAnchorIndex<TPage extends {
         readonly box: {
             readonly y: number;
         };
+        /** Present on a real line; a merged one carries spans from more than one paragraph. */
+        readonly spans?: readonly {
+            readonly range: {
+                readonly paragraphId: string;
+                readonly end: number;
+            };
+        }[];
     }[];
 }[]): Map<string, ReviewParagraphAnchor>;
 /**
@@ -367,4 +411,4 @@ declare function reviewItemGeometry(item: ReviewItem, index: ReadonlyMap<string,
     readonly y: number;
 } | null;
 
-export { type CommentRecord as C, type ReviewModelInput as R, W15_NAMESPACE_URI as W, type ReviewItem as a, type ReviewRevisionItem as b, type ReviewCommentItem as c, type ReviewCustomItem as d, type ReviewPosition as e, type ReviewRange as f, type ReviewRevisionKind as g, type CommentAnchor as h, type CommentPosition as i, type CommentThreadState as j, type ReviewParagraphAnchor as k, activeReviewItem as l, commentBodyText as m, commentInitials as n, firstReviewRange as o, reviewItemGeometry as p, reviewItemKey as q, reviewAnchorIndex as r, reviewItemPositionRank as s, reviewItemRanges as t, reviewItemsAt as u, reviewThreadRootOf as v };
+export { type CommentRecord as C, type ReviewModelInput as R, W15_NAMESPACE_URI as W, type ReviewItem as a, type ReviewRevisionItem as b, type ReviewCommentItem as c, type ReviewCustomItem as d, type ReviewPosition as e, type ReviewRange as f, type ReviewRevisionKind as g, type CommentAnchor as h, type CommentPosition as i, type CommentThreadState as j, type ReviewParagraphAnchor as k, activeReviewItem as l, anchorLineY as m, commentBodyText as n, commentInitials as o, firstReviewRange as p, reviewItemGeometry as q, reviewAnchorIndex as r, reviewItemKey as s, reviewItemPositionRank as t, reviewItemRanges as u, reviewItemsAt as v, reviewThreadRootOf as w };

package/dist/{review-support-BJ-YjGmD.d.cts → review-support-T-riLz4Y.d.cts}

@@ -1,5 +1,5 @@
 import { e as OoxmlPart, a as OoxmlElement } from './ooxml-tree-BU0e3DVi.cjs';
-import { R as RevisionAddress } from './tree-op-types-EZXbR8bW.cjs';
+import { R as RevisionAddress } from './tree-op-types-CUCwPWjT.cjs';
 
 /** The `w15` namespace: `commentsExtended.xml` — thread parent and resolved state. */
 declare const W15_NAMESPACE_URI = "http://schemas.microsoft.com/office/word/2012/wordml";
@@ -101,12 +101,29 @@ interface ReviewRevisionItem {
     /** The words a replacement removes. Empty for every other kind. */
     readonly replacedText: string;
     readonly revisionKind: ReviewRevisionKind;
+    /**
+     * WHICH decision a `paragraphMark` records, absent for every other kind.
+     *
+     * `EG_ParaRPrTrackChanges` is `ins? del? moveFrom? moveTo?`, and the four say opposite
+     * things about one break. Without this a card called a deleted break an inserted one, which
+     * is the reverse of what Accept on that card does.
+     */
+    readonly markDirection?: 'insert' | 'delete' | 'moveFrom' | 'moveTo';
     readonly author: string;
     readonly date?: string;
     /** Text the revision covers, for the card summary. Empty for changes with no characters. */
     readonly text: string;
     /** Every site this decision touches, in document order. */
     readonly ranges: readonly ReviewRange[];
+    /**
+     * How deeply this change is NESTED inside other changes, 0 for an unenclosed one.
+     *
+     * `w:ins` wrapping `w:del` is content one reviewer added and another struck. Both stay
+     * pending, so both are cards, over one identical range — and a range then cannot say which
+     * change a caret is in. Word treats the innermost as the operative one, so it wins the caret
+     * and the change enclosing it stays listed and reachable.
+     */
+    readonly nesting: number;
     /**
      * How many leading `ranges` are the STRUCK half of a replacement.
      *
@@ -321,8 +338,28 @@ interface ReviewParagraphAnchor {
         readonly box: {
             readonly y: number;
         };
+        /**
+         * Present on a real line. A merged fragment's join line carries spans from two
+         * paragraphs, and its `range` can only name one of them, so the OTHER paragraph's extent
+         * on that line is readable here and nowhere else.
+         */
+        readonly spans?: readonly {
+            readonly range: {
+                readonly paragraphId: string;
+                readonly end: number;
+            };
+        }[];
     }[];
 }
+/**
+ * The y of the line a position sits on, measured from the anchor's own origin.
+ *
+ * An ordinary line answers from its own range, exactly as it always did. On a merged
+ * fragment's join line the range names one of the two paragraphs, so an offset compared
+ * against it either overshot — putting a card in the absorbed half beside the wrong line —
+ * or matched the first line every time.
+ */
+declare function anchorLineY(anchor: ReviewParagraphAnchor, paragraphId: string, offset: number): number;
 /**
  * Paragraph id to its place on the page, in ONE pass over the layout.
  *
@@ -350,6 +387,13 @@ declare function reviewAnchorIndex<TPage extends {
         readonly box: {
             readonly y: number;
         };
+        /** Present on a real line; a merged one carries spans from more than one paragraph. */
+        readonly spans?: readonly {
+            readonly range: {
+                readonly paragraphId: string;
+                readonly end: number;
+            };
+        }[];
     }[];
 }[]): Map<string, ReviewParagraphAnchor>;
 /**
@@ -367,4 +411,4 @@ declare function reviewItemGeometry(item: ReviewItem, index: ReadonlyMap<string,
     readonly y: number;
 } | null;
 
-export { type CommentRecord as C, type ReviewModelInput as R, W15_NAMESPACE_URI as W, type ReviewItem as a, type ReviewRevisionItem as b, type ReviewCommentItem as c, type ReviewCustomItem as d, type ReviewPosition as e, type ReviewRange as f, type ReviewRevisionKind as g, type CommentAnchor as h, type CommentPosition as i, type CommentThreadState as j, type ReviewParagraphAnchor as k, activeReviewItem as l, commentBodyText as m, commentInitials as n, firstReviewRange as o, reviewItemGeometry as p, reviewItemKey as q, reviewAnchorIndex as r, reviewItemPositionRank as s, reviewItemRanges as t, reviewItemsAt as u, reviewThreadRootOf as v };
+export { type CommentRecord as C, type ReviewModelInput as R, W15_NAMESPACE_URI as W, type ReviewItem as a, type ReviewRevisionItem as b, type ReviewCommentItem as c, type ReviewCustomItem as d, type ReviewPosition as e, type ReviewRange as f, type ReviewRevisionKind as g, type CommentAnchor as h, type CommentPosition as i, type CommentThreadState as j, type ReviewParagraphAnchor as k, activeReviewItem as l, anchorLineY as m, commentBodyText as n, commentInitials as o, firstReviewRange as p, reviewItemGeometry as q, reviewAnchorIndex as r, reviewItemKey as s, reviewItemPositionRank as t, reviewItemRanges as u, reviewItemsAt as v, reviewThreadRootOf as w };

package/dist/{revision-projection-DHAkcD_L.d.ts → revision-projection-UKqvPa4-.d.ts}

@@ -53,16 +53,67 @@ declare const DEFAULT_REVISION_DISPLAY_MODE: RevisionDisplayMode;
  */
 declare function revisionsVisible(revisions: readonly RevisionAttribution[], mode: RevisionDisplayMode): boolean;
 /**
- * The revision on a paragraph's own MARK, from `w:pPr/w:rPr/w:ins|w:del`.
+ * Every revision on a paragraph's own MARK, from `w:pPr/w:rPr/w:ins|w:del|w:moveFrom|w:moveTo`.
+ *
+ * All four members of `EG_ParaRPrTrackChanges`. A moved paragraph carries `w:moveFrom` on the
+ * mark of the copy it left and `w:moveTo` on the mark of the copy it arrived at, so a move
+ * that spans whole paragraphs is recorded here and nowhere else.
  *
  * `EG_ParaRPrTrackChanges` records that the pilcrow itself was inserted or deleted, which is how
  * Word writes a paragraph split or merge. It is not content — there is no text to decorate — so
  * a surface shows it as a mark of its own beside the paragraph, the way Word draws a struck-
  * through ¶.
  *
+ * A LIST, because the group is `ins? del? moveFrom? moveTo?` and the first two can both be
+ * there: that pair is what Word writes when a second author proposes removing a mark the first
+ * proposed adding, and it is what this engine's own writer emits (`tree-op-tracked.ts`).
+ * Answering with the first one hid the second author's decision from the PAGE. The review pane
+ * walks the tree itself and always listed both, which is the worse shape of the two: a card
+ * offering a decision the reader could see no sign of.
+ *
+ * Ordered as the file orders them, which is the order the group declares.
+ *
  * Property-position `w:ins`/`w:del` stay `generic` in the tree deliberately, so this reads them
  * by name rather than by kind.
  */
+declare function paragraphMarkRevisionsOf(paragraph: OoxmlNode): readonly RevisionAttribution[];
+/**
+ * The tracked FORMAT change on a paragraph's own mark, from `w:pPr/w:rPr/w:rPrChange`.
+ *
+ * `CT_ParaRPr` ends with it (§17.13.5.32), and Word writes it when a user changes the mark's
+ * own run properties with tracking on. It reaches the fragment rather than a span because it
+ * decorates no characters, and it is not in `props`: a fragment's `props` carry the mark's
+ * `w:rPr` by NAME only, with none of its children.
+ *
+ * Note that `w:rPrChange/w:rPr` is `CT_ParaRPrOriginal`, which may carry its own revision
+ * marks. Those describe the mark as it WAS and must not be read as live ones, which is why
+ * this reads the change element's own attributes and never descends into it.
+ */
+declare function paragraphMarkFormatRevisionOf(paragraph: OoxmlNode): RevisionAttribution | null;
+/**
+ * The single decision a one-field reader sees.
+ *
+ * A DELETION wins when a mark carries both, for the reason paint draws it that way: a break
+ * proposed and then unproposed ends up removed, so that is the decision a reader who can only
+ * see one must see. One function decides it, so the deprecated field, the deprecated function
+ * and the painted glyph cannot answer differently.
+ */
+declare function shownMarkRevision(revisions: readonly RevisionAttribution[]): RevisionAttribution | undefined;
+/**
+ * Does this decision, taken, remove the paragraph mark?
+ *
+ * A deletion does, and so does a `moveFrom`: the copy the paragraph moved OUT of goes away
+ * when the move is accepted. `insert` and `moveTo` are the other half of each pair, and they
+ * keep the break. Paint, the change bar and the resolved views all ask this one question, so
+ * a `moveFrom` cannot end up struck through in the margin and blue on the glyph.
+ */
+declare function markRevisionRemovesMark(revision: RevisionAttribution): boolean;
+/**
+ * The one decision on a paragraph's mark that a single-field reader sees.
+ *
+ * @deprecated Reads one of the revisions a mark can carry. Use {@link paragraphMarkRevisionsOf},
+ * which answers with all of them.
+ */
 declare function paragraphMarkRevisionOf(paragraph: OoxmlNode): RevisionAttribution | null;
 /**
  * The tracked FORMAT change on a property list, from `w:rPrChange` or `w:pPrChange`.
@@ -81,4 +132,4 @@ declare function formatRevisionOf(properties: readonly {
 /** True when this stack of revisions marks its content as deleted from the live document. */
 declare function revisionsAreDeletion(revisions: readonly RevisionAttribution[]): boolean;
 
-export { DEFAULT_REVISION_DISPLAY_MODE as D, type RevisionDisplayMode as R, type RevisionAttribution as a, type RevisionKind as b, revisionsVisible as c, formatRevisionOf as f, paragraphMarkRevisionOf as p, revisionsAreDeletion as r };
+export { DEFAULT_REVISION_DISPLAY_MODE as D, type RevisionDisplayMode as R, type RevisionAttribution as a, type RevisionKind as b, paragraphMarkRevisionOf as c, paragraphMarkRevisionsOf as d, revisionsVisible as e, formatRevisionOf as f, markRevisionRemovesMark as m, paragraphMarkFormatRevisionOf as p, revisionsAreDeletion as r, shownMarkRevision as s };

package/dist/{revision-projection-72ZApe-g.d.cts → revision-projection-WzlQGBJx.d.cts}

@@ -53,16 +53,67 @@ declare const DEFAULT_REVISION_DISPLAY_MODE: RevisionDisplayMode;
  */
 declare function revisionsVisible(revisions: readonly RevisionAttribution[], mode: RevisionDisplayMode): boolean;
 /**
- * The revision on a paragraph's own MARK, from `w:pPr/w:rPr/w:ins|w:del`.
+ * Every revision on a paragraph's own MARK, from `w:pPr/w:rPr/w:ins|w:del|w:moveFrom|w:moveTo`.
+ *
+ * All four members of `EG_ParaRPrTrackChanges`. A moved paragraph carries `w:moveFrom` on the
+ * mark of the copy it left and `w:moveTo` on the mark of the copy it arrived at, so a move
+ * that spans whole paragraphs is recorded here and nowhere else.
  *
  * `EG_ParaRPrTrackChanges` records that the pilcrow itself was inserted or deleted, which is how
  * Word writes a paragraph split or merge. It is not content — there is no text to decorate — so
  * a surface shows it as a mark of its own beside the paragraph, the way Word draws a struck-
  * through ¶.
  *
+ * A LIST, because the group is `ins? del? moveFrom? moveTo?` and the first two can both be
+ * there: that pair is what Word writes when a second author proposes removing a mark the first
+ * proposed adding, and it is what this engine's own writer emits (`tree-op-tracked.ts`).
+ * Answering with the first one hid the second author's decision from the PAGE. The review pane
+ * walks the tree itself and always listed both, which is the worse shape of the two: a card
+ * offering a decision the reader could see no sign of.
+ *
+ * Ordered as the file orders them, which is the order the group declares.
+ *
  * Property-position `w:ins`/`w:del` stay `generic` in the tree deliberately, so this reads them
  * by name rather than by kind.
  */
+declare function paragraphMarkRevisionsOf(paragraph: OoxmlNode): readonly RevisionAttribution[];
+/**
+ * The tracked FORMAT change on a paragraph's own mark, from `w:pPr/w:rPr/w:rPrChange`.
+ *
+ * `CT_ParaRPr` ends with it (§17.13.5.32), and Word writes it when a user changes the mark's
+ * own run properties with tracking on. It reaches the fragment rather than a span because it
+ * decorates no characters, and it is not in `props`: a fragment's `props` carry the mark's
+ * `w:rPr` by NAME only, with none of its children.
+ *
+ * Note that `w:rPrChange/w:rPr` is `CT_ParaRPrOriginal`, which may carry its own revision
+ * marks. Those describe the mark as it WAS and must not be read as live ones, which is why
+ * this reads the change element's own attributes and never descends into it.
+ */
+declare function paragraphMarkFormatRevisionOf(paragraph: OoxmlNode): RevisionAttribution | null;
+/**
+ * The single decision a one-field reader sees.
+ *
+ * A DELETION wins when a mark carries both, for the reason paint draws it that way: a break
+ * proposed and then unproposed ends up removed, so that is the decision a reader who can only
+ * see one must see. One function decides it, so the deprecated field, the deprecated function
+ * and the painted glyph cannot answer differently.
+ */
+declare function shownMarkRevision(revisions: readonly RevisionAttribution[]): RevisionAttribution | undefined;
+/**
+ * Does this decision, taken, remove the paragraph mark?
+ *
+ * A deletion does, and so does a `moveFrom`: the copy the paragraph moved OUT of goes away
+ * when the move is accepted. `insert` and `moveTo` are the other half of each pair, and they
+ * keep the break. Paint, the change bar and the resolved views all ask this one question, so
+ * a `moveFrom` cannot end up struck through in the margin and blue on the glyph.
+ */
+declare function markRevisionRemovesMark(revision: RevisionAttribution): boolean;
+/**
+ * The one decision on a paragraph's mark that a single-field reader sees.
+ *
+ * @deprecated Reads one of the revisions a mark can carry. Use {@link paragraphMarkRevisionsOf},
+ * which answers with all of them.
+ */
 declare function paragraphMarkRevisionOf(paragraph: OoxmlNode): RevisionAttribution | null;
 /**
  * The tracked FORMAT change on a property list, from `w:rPrChange` or `w:pPrChange`.
@@ -81,4 +132,4 @@ declare function formatRevisionOf(properties: readonly {
 /** True when this stack of revisions marks its content as deleted from the live document. */
 declare function revisionsAreDeletion(revisions: readonly RevisionAttribution[]): boolean;
 
-export { DEFAULT_REVISION_DISPLAY_MODE as D, type RevisionDisplayMode as R, type RevisionAttribution as a, type RevisionKind as b, revisionsVisible as c, formatRevisionOf as f, paragraphMarkRevisionOf as p, revisionsAreDeletion as r };
+export { DEFAULT_REVISION_DISPLAY_MODE as D, type RevisionDisplayMode as R, type RevisionAttribution as a, type RevisionKind as b, paragraphMarkRevisionOf as c, paragraphMarkRevisionsOf as d, revisionsVisible as e, formatRevisionOf as f, markRevisionRemovesMark as m, paragraphMarkFormatRevisionOf as p, revisionsAreDeletion as r, shownMarkRevision as s };

package/dist/{semantic-cell-selection-DZtyMXkH.d.ts → semantic-cell-selection-B5vfPz4Q.d.ts}

@@ -1,7 +1,7 @@
 import { e as OoxmlPart, a as OoxmlElement, O as OoxmlNode } from './ooxml-tree-BU0e3DVi.js';
-import { P as PageGeometry, I as InlineDrawingRecord, A as AnchoredDrawingRecord, T as TextMeasurer, L as LineRecord, S as SemanticLayout, C as ContentControlBoundaryRecord, a as StyleSpanRecord, b as TableRowFragmentRecord, c as TableCellFragmentRecord } from './semantic-records-CR5hTqMK.js';
-import { R as RevisionDisplayMode } from './revision-projection-DHAkcD_L.js';
-import { S as SemanticPosition, C as CaretGeometry, a as SemanticSelection } from './semantic-interaction-DrgbgKg6.js';
+import { P as PageGeometry, I as InlineDrawingRecord, A as AnchoredDrawingRecord, T as TextMeasurer, L as LineRecord, a as StyleSpanRecord, S as SemanticLayout, C as ContentControlBoundaryRecord, b as TableRowFragmentRecord, c as TableCellFragmentRecord } from './semantic-records-CdQvpUj1.js';
+import { R as RevisionDisplayMode } from './revision-projection-UKqvPa4-.js';
+import { S as SemanticPosition, C as CaretGeometry, a as SemanticSelection } from './semantic-interaction-lvpzZRpA.js';
 
 /**
  * Hard ceiling on sections enumerated from a document (matches write-path
@@ -320,7 +320,10 @@ declare function spanOffsetX(span: StyleSpanRecord, offset: number, measurer: Te
  *   - otherwise the run BEFORE the offset wins — the run a keystroke would continue —
  *     except at the start of the line, where there is nothing before it.
  */
-declare function caretBoxOnLine(line: LineRecord, offset: number, measurer: TextMeasurer | undefined): {
+declare function caretBoxOnLine(line: LineRecord, offset: number, measurer: TextMeasurer | undefined, segment?: {
+    readonly spans: readonly StyleSpanRecord[];
+    readonly drawings: readonly InlineDrawingRecord[];
+} | null): {
     x: number;
     y: number;
     height: number;

package/dist/{semantic-cell-selection--ezfezTe.d.cts → semantic-cell-selection-BTQFpN0S.d.cts}

@@ -1,7 +1,7 @@
 import { e as OoxmlPart, a as OoxmlElement, O as OoxmlNode } from './ooxml-tree-BU0e3DVi.cjs';
-import { P as PageGeometry, I as InlineDrawingRecord, A as AnchoredDrawingRecord, T as TextMeasurer, L as LineRecord, S as SemanticLayout, C as ContentControlBoundaryRecord, a as StyleSpanRecord, b as TableRowFragmentRecord, c as TableCellFragmentRecord } from './semantic-records-DSD8WENa.cjs';
-import { R as RevisionDisplayMode } from './revision-projection-72ZApe-g.cjs';
-import { S as SemanticPosition, C as CaretGeometry, a as SemanticSelection } from './semantic-interaction-2yxdv7q0.cjs';
+import { P as PageGeometry, I as InlineDrawingRecord, A as AnchoredDrawingRecord, T as TextMeasurer, L as LineRecord, a as StyleSpanRecord, S as SemanticLayout, C as ContentControlBoundaryRecord, b as TableRowFragmentRecord, c as TableCellFragmentRecord } from './semantic-records-DEOs3_tE.cjs';
+import { R as RevisionDisplayMode } from './revision-projection-WzlQGBJx.cjs';
+import { S as SemanticPosition, C as CaretGeometry, a as SemanticSelection } from './semantic-interaction-CDNEU_Tx.cjs';
 
 /**
  * Hard ceiling on sections enumerated from a document (matches write-path
@@ -320,7 +320,10 @@ declare function spanOffsetX(span: StyleSpanRecord, offset: number, measurer: Te
  *   - otherwise the run BEFORE the offset wins — the run a keystroke would continue —
  *     except at the start of the line, where there is nothing before it.
  */
-declare function caretBoxOnLine(line: LineRecord, offset: number, measurer: TextMeasurer | undefined): {
+declare function caretBoxOnLine(line: LineRecord, offset: number, measurer: TextMeasurer | undefined, segment?: {
+    readonly spans: readonly StyleSpanRecord[];
+    readonly drawings: readonly InlineDrawingRecord[];
+} | null): {
     x: number;
     y: number;
     height: number;

package/dist/{semantic-interaction-DrgbgKg6.d.ts → semantic-interaction-CDNEU_Tx.d.cts}

@@ -1,4 +1,4 @@
-import { T as TextMeasurer, S as SemanticLayout, B as BlockFragmentRecord, C as ContentControlBoundaryRecord, a as StyleSpanRecord } from './semantic-records-CR5hTqMK.js';
+import { T as TextMeasurer, S as SemanticLayout, B as BlockFragmentRecord, C as ContentControlBoundaryRecord, a as StyleSpanRecord } from './semantic-records-DEOs3_tE.cjs';
 
 /** A caret position in the model. */
 interface SemanticPosition {
@@ -87,34 +87,6 @@ declare function contentControlAtSemantic(layout: SemanticLayout, point: {
 }): ContentControlBoundaryRecord | null;
 /** Layout-published content-control boundaries in document order. */
 declare function contentControlsInLayout(layout: SemanticLayout): readonly ContentControlBoundaryRecord[];
-/** The rectangles covering a selection, one per line it spans. */
-declare function selectionRects(layout: SemanticLayout, selection: SemanticSelection): SelectionRect[];
-/** A model range to highlight, and the key the caller knows it by. */
-interface KeyedRange {
-    readonly key: string;
-    readonly from: SemanticPosition;
-    readonly to: SemanticPosition;
-}
-/**
- * Rectangles for MANY ranges in ONE pass over the lines.
- *
- * Not `selectionRects` in a loop. That walks every page, fragment and line per range, and a
- * contract with two hundred comments would re-walk the whole document two hundred times on
- * every layout — the highlight would cost more than the layout it decorates. One pass tests
- * each line against every range instead, which is the same work a single selection does.
- */
-declare function keyedRangeRects(layout: SemanticLayout, ranges: readonly KeyedRange[], 
-/**
- * Pages to measure, or every page when absent.
- *
- * A band that is not on screen is not painted, so measuring it is pure cost — and it is
- * cost paid per keystroke, because an edit republishes the layout. Bounding this to the
- * materialized pages is what keeps typing in a heavily reviewed document as fast as
- * typing in a clean one.
- */
-pages?: ReadonlySet<number>): Map<string, SelectionRect[]>;
-/** Paragraph ids in document order, deduplicated across fragments. */
-declare function documentOrder(layout: SemanticLayout): string[];
 /**
  * One caret movement, in Word's own vocabulary.
  *
@@ -152,4 +124,4 @@ declare function compositionAnchor(layout: SemanticLayout, position: SemanticPos
 /** The style spans a selection touches, for reporting active formatting. */
 declare function spansInSelection(layout: SemanticLayout, selection: SemanticSelection): StyleSpanRecord[];
 
-export { type CaretGeometry as C, type KeyedRange as K, type MoveCaretOptions as M, type NavigationCommand as N, type SemanticPosition as S, type SemanticSelection as a, type CaretAtOptions as b, type SelectionRect as c, caretAt as d, caretStops as e, caretStopsForBlocks as f, compositionAnchor as g, contentControlAtSemantic as h, contentControlsInLayout as i, documentOrder as j, hitTestSemantic as k, keyedRangeRects as l, moveCaret as m, spansInSelection as n, paragraphTextFromLayout as p, selectionRects as s };
+export { type CaretGeometry as C, type MoveCaretOptions as M, type NavigationCommand as N, type SemanticPosition as S, type SemanticSelection as a, type SelectionRect as b, type CaretAtOptions as c, caretAt as d, caretStops as e, caretStopsForBlocks as f, compositionAnchor as g, contentControlAtSemantic as h, contentControlsInLayout as i, hitTestSemantic as j, moveCaret as m, paragraphTextFromLayout as p, spansInSelection as s };

package/dist/{semantic-interaction-2yxdv7q0.d.cts → semantic-interaction-lvpzZRpA.d.ts}

@@ -1,4 +1,4 @@
-import { T as TextMeasurer, S as SemanticLayout, B as BlockFragmentRecord, C as ContentControlBoundaryRecord, a as StyleSpanRecord } from './semantic-records-DSD8WENa.cjs';
+import { T as TextMeasurer, S as SemanticLayout, B as BlockFragmentRecord, C as ContentControlBoundaryRecord, a as StyleSpanRecord } from './semantic-records-CdQvpUj1.js';
 
 /** A caret position in the model. */
 interface SemanticPosition {
@@ -87,34 +87,6 @@ declare function contentControlAtSemantic(layout: SemanticLayout, point: {
 }): ContentControlBoundaryRecord | null;
 /** Layout-published content-control boundaries in document order. */
 declare function contentControlsInLayout(layout: SemanticLayout): readonly ContentControlBoundaryRecord[];
-/** The rectangles covering a selection, one per line it spans. */
-declare function selectionRects(layout: SemanticLayout, selection: SemanticSelection): SelectionRect[];
-/** A model range to highlight, and the key the caller knows it by. */
-interface KeyedRange {
-    readonly key: string;
-    readonly from: SemanticPosition;
-    readonly to: SemanticPosition;
-}
-/**
- * Rectangles for MANY ranges in ONE pass over the lines.
- *
- * Not `selectionRects` in a loop. That walks every page, fragment and line per range, and a
- * contract with two hundred comments would re-walk the whole document two hundred times on
- * every layout — the highlight would cost more than the layout it decorates. One pass tests
- * each line against every range instead, which is the same work a single selection does.
- */
-declare function keyedRangeRects(layout: SemanticLayout, ranges: readonly KeyedRange[], 
-/**
- * Pages to measure, or every page when absent.
- *
- * A band that is not on screen is not painted, so measuring it is pure cost — and it is
- * cost paid per keystroke, because an edit republishes the layout. Bounding this to the
- * materialized pages is what keeps typing in a heavily reviewed document as fast as
- * typing in a clean one.
- */
-pages?: ReadonlySet<number>): Map<string, SelectionRect[]>;
-/** Paragraph ids in document order, deduplicated across fragments. */
-declare function documentOrder(layout: SemanticLayout): string[];
 /**
  * One caret movement, in Word's own vocabulary.
  *
@@ -152,4 +124,4 @@ declare function compositionAnchor(layout: SemanticLayout, position: SemanticPos
 /** The style spans a selection touches, for reporting active formatting. */
 declare function spansInSelection(layout: SemanticLayout, selection: SemanticSelection): StyleSpanRecord[];
 
-export { type CaretGeometry as C, type KeyedRange as K, type MoveCaretOptions as M, type NavigationCommand as N, type SemanticPosition as S, type SemanticSelection as a, type CaretAtOptions as b, type SelectionRect as c, caretAt as d, caretStops as e, caretStopsForBlocks as f, compositionAnchor as g, contentControlAtSemantic as h, contentControlsInLayout as i, documentOrder as j, hitTestSemantic as k, keyedRangeRects as l, moveCaret as m, spansInSelection as n, paragraphTextFromLayout as p, selectionRects as s };
+export { type CaretGeometry as C, type MoveCaretOptions as M, type NavigationCommand as N, type SemanticPosition as S, type SemanticSelection as a, type SelectionRect as b, type CaretAtOptions as c, caretAt as d, caretStops as e, caretStopsForBlocks as f, compositionAnchor as g, contentControlAtSemantic as h, contentControlsInLayout as i, hitTestSemantic as j, moveCaret as m, paragraphTextFromLayout as p, spansInSelection as s };

package/dist/{semantic-paint-BedBxkyY.d.ts → semantic-paint-BBPL3u5w.d.ts}

@@ -1,5 +1,98 @@
-import { C as ContentControlBoundaryRecord, S as SemanticLayout } from './semantic-records-CR5hTqMK.js';
-import { V as ValidatedImageBytesHandle, R as RenderableImageMime } from './image-resources-BG9DLyW7.js';
+import { C as ContentControlBoundaryRecord, S as SemanticLayout } from './semantic-records-CdQvpUj1.js';
+import { V as ValidatedImageBytesHandle, R as RenderableImageMime } from './image-resources-Cl5_cNi9.js';
+
+/**
+ * Everything a host can say about ONE author's presentation. Every field is optional and
+ * every field is presentation-only — nothing here is ever serialised into the document.
+ *
+ * Deliberately about the PAINTED DOCUMENT (which only the painter can style) plus the
+ * author's identity data. Review-card DESIGN is not configured here: the review chrome
+ * follows `color` as its accent automatically, and everything further is composition —
+ * a custom card reading this style through the review surface's `useReviewAuthor`, or
+ * CSS on the cards' `data-review-author`/`data-review-author-slot` hooks.
+ *
+ * @public
+ */
+interface RevisionAuthorStyle {
+    /**
+     * Ink and decoration colour of this author's changes in the document — and the accent
+     * the review chrome keys on (avatar disc, card variable, marker).
+     */
+    color?: string;
+    /** Background wash behind this author's changes in the document. */
+    background?: string;
+    /**
+     * Class names added to every painted span of this author's changes, for styling the
+     * typed fields do not cover. Keep the rules metric-safe (outlines, shadows, accents):
+     * the engine measures the text it paints, and a class that resizes glyphs drifts the
+     * page from its layout.
+     */
+    spanClassName?: string;
+    /** Avatar image for this author; the packaged card renders it in place of initials. */
+    avatarUrl?: string;
+}
+/**
+ * Per-author style assignments.
+ *
+ * Keys match `w:author` exactly; a value is a CSS colour or a full
+ * {@link RevisionAuthorStyle}. `others` says what authors WITHOUT an entry take: the
+ * `--doc-review-author-N` ramp by default, or `'kind'` to leave them on the kind colours —
+ * which is how "highlight these reviewers, leave everyone else green and red" is said.
+ *
+ * @public
+ */
+interface RevisionAuthorAssignments {
+    /** Authors without an entry: the ramp (default), or the `'kind'` colours. */
+    readonly others?: 'kind' | 'author';
+    readonly authors: Readonly<Record<string, string | RevisionAuthorStyle>>;
+}
+/**
+ * How painted tracked changes are coloured.
+ *
+ * - `'author'` (the DEFAULT) — every change takes its author's colour from the
+ *   `--doc-review-author-N` ramp, assigned by order of first appearance in the document.
+ *   Word's own default, and the reason it is this engine's: a paragraph three people
+ *   edited has to read as three people. Restyle a slot under `.docx-editor` to change the
+ *   ramp.
+ * - `'kind'` — insertions and deletions take the two kind colours
+ *   (`--doc-revision-insertion` / `--doc-revision-deletion`), so "added" and "removed" are
+ *   what a reader tells apart at a glance, whoever proposed them.
+ * - {@link RevisionAuthorAssignments} — style the named authors; `others` decides whether
+ *   the rest take the ramp (the default) or the kind colours.
+ *
+ * Presentation only: nothing here is ever serialised into the document.
+ *
+ * @public
+ */
+type RevisionStyles = 'kind' | 'author' | RevisionAuthorAssignments;
+/**
+ * One document author, resolved: who, which ramp slot, and what they draw in.
+ *
+ * @public
+ */
+interface ReviewAuthorInfo {
+    /** The `w:author` string, exactly as the file carries it. */
+    readonly author: string;
+    /**
+     * Rank by order of first appearance — an UNBOUNDED index, not a ramp slot.
+     *
+     * The ramp defines {@link REVIEW_AUTHOR_SLOTS} colours and every DOM hook wraps into it,
+     * so the ninth author ranks 8 here and carries `data-review-author-slot="0"`. Building a
+     * selector from this value needs the same wrap: `slot % 8`.
+     */
+    readonly slot: number;
+    /**
+     * The colour this author is DRAWN IN by the review chrome — their declared colour, or
+     * their ramp slot's token.
+     *
+     * Not necessarily what the document paints. `'kind'`, and `others: 'kind'` for an author
+     * with no declaration, colour the painted text by insertion/deletion instead, while the
+     * cards keep the per-author accent this reports.
+     */
+    readonly color: string;
+    /** The host-supplied style, normalised; absent when the author rides the ramp. */
+    readonly style?: RevisionAuthorStyle;
+}
 
 /** Host port for safe blob URLs — only called for {@link ImageResourceState.kind} `ready`. */
 interface PaintImageUrlPort {
@@ -67,6 +160,12 @@ interface PaintOptions {
     readonly fieldShading?: FieldShadingMode;
     /** See {@link PaintContext.shadeFormFields}. */
     readonly shadeFormFields?: boolean;
+    /**
+     * How tracked changes are coloured: by AUTHOR through the `--doc-review-author-N`
+     * ramp (the default, as in Word), by kind, or by author with host-pinned colours.
+     * See {@link RevisionStyles}.
+     */
+    readonly revisionStyles?: RevisionStyles;
     /**
      * Relationship id of the header/footer story currently open for editing.
      *
@@ -116,6 +215,15 @@ interface PaintOptions {
         readonly additionalBoundaries?: readonly ContentControlBoundaryRecord[];
         /** Control ids that represent TOC regions (hover-only chrome; never caret-sticky). */
         readonly tocControlIds?: ReadonlySet<string>;
+        /**
+         * No control may be written right now — viewing mode, or a protected document.
+         *
+         * The widget is a `<button>` the ENGINE paints, and a click on it commits a tree op, so
+         * an enabled-looking checkbox on a read-only document is not a cosmetic lie: it is the
+         * write itself. Disabling it here also stops the pointer lane, which already skips a
+         * widget carrying `data-disabled-reason`.
+         */
+        readonly readOnly?: boolean;
     };
     readonly drawingStrings?: DrawingPaintStrings;
     readonly imageUrlPort?: PaintImageUrlPort;
@@ -130,4 +238,4 @@ interface PaintOptions {
  */
 declare function paintSemanticLayout(container: HTMLElement, layout: SemanticLayout, options?: PaintOptions): void;
 
-export { DEFAULT_FIELD_SHADING as D, type FieldShadingMode as F, type PaintOptions as P, type DrawingPaintStrings as a, paintSemanticLayout as p };
+export { DEFAULT_FIELD_SHADING as D, type FieldShadingMode as F, type PaintOptions as P, type ReviewAuthorInfo as R, type RevisionAuthorAssignments as a, type RevisionAuthorStyle as b, type RevisionStyles as c, type DrawingPaintStrings as d, paintSemanticLayout as p };