@adeu/core 1.17.1 → 1.18.0

package/dist/index.d.cts

@@ -186,10 +186,49 @@ declare class RedlineEngine {
     skipped_details: string[];
     constructor(doc: DocumentObject, author?: string);
     private _check_punctuation_warning;
+    /**
+     * Best-effort "did you mean" hint for a failed target. The common loop trap
+     * (observed in the field) is an anchored regex like `^\( x \)$` against a
+     * mid-document string: ^/$ bind to the whole full_text, so it never matches
+     * even though the literal `( x )` is present. We strip regex anchoring/escapes
+     * and probe full_text for a literal occurrence; if found, we tell the model
+     * the exact literal that WOULD match so it drops the anchors instead of
+     * escalating the regex further.
+     */
+    private _nearest_match_hint;
     private _build_edit_context_previews;
     private _scan_existing_ids;
     private _get_heading_path_and_page;
     accept_all_revisions(): void;
+    /**
+     * Revert every tracked change, returning the document to the state it had
+     * before any revision was proposed. The exact inverse of
+     * accept_all_revisions:
+     *
+     *   - <w:ins>  -> removed together with all of its content (the proposed
+     *                 insertion never existed); an inserted row (<w:ins> in
+     *                 <w:trPr>) drops the whole row.
+     *   - <w:del>  -> unwrapped, restoring the original text (<w:delText> becomes
+     *                 <w:t> again); a row-deletion mark in <w:trPr> is removed so
+     *                 the row survives.
+     *   - paragraph-mark <w:del> in pPr/rPr -> removed, undoing a proposed merge.
+     *
+     * Comments are annotations, not revisions, so standalone comments are left in
+     * place; only anchors stranded inside a rejected insertion are cleaned up.
+     *
+     * Insertions are reverted before deletions are restored so a deletion nested
+     * inside a foreign author's insertion is removed wholesale with the insertion
+     * — the contingent text disappears rather than being promoted to committed
+     * body text.
+     *
+     * Known limitation: tracked paragraph STRUCTURE changes (a split recorded as a
+     * pilcrow <w:ins>, or a merge recorded as a pilcrow <w:del>) are reverted only
+     * to the extent of dropping/keeping the mark; the original paragraph boundary
+     * is not reconstructed, because the merge protocol coalesces paragraphs
+     * destructively at edit time. Reverting run-level insertions/deletions (the
+     * common case) is exact. This limitation is shared with the Python engine.
+     */
+    reject_all_revisions(): void;
     private _getNextId;
     private _create_track_change_tag;
     private _set_text_content;
@@ -268,7 +307,7 @@ declare class RedlineEngine {
     private _anchor_reply_comment;
     private _clean_wrapping_comments;
     private _delete_comments_in_element;
-    validate_edits(edits: any[]): string[];
+    validate_edits(edits: any[], index_offset?: number): string[];
     validate_review_actions(actions: any[]): string[];
     process_batch(changes: DocumentChange[], dry_run?: boolean): any;
     private _process_batch_internal;
@@ -276,6 +315,15 @@ declare class RedlineEngine {
     apply_review_actions(actions: any[]): [number, number];
     private _apply_table_edit;
     private _pre_resolve_heuristic_edit;
+    /**
+     * Split a <w:ins> so that everything up to and INCLUDING split_after stays in
+     * a left <w:ins>, new_elem is placed between, and the remainder moves to a
+     * right <w:ins> — all at the grandparent level. Used when revising another
+     * author's pending insertion: the <w:del> stays nested in their <w:ins> while
+     * our replacement <w:ins> lands as a sibling, so we never nest <w:ins> in
+     * <w:ins>.
+     */
+    private _insert_and_split_ins;
     private _apply_single_edit_indexed;
 }
 

package/dist/index.d.ts

@@ -186,10 +186,49 @@ declare class RedlineEngine {
     skipped_details: string[];
     constructor(doc: DocumentObject, author?: string);
     private _check_punctuation_warning;
+    /**
+     * Best-effort "did you mean" hint for a failed target. The common loop trap
+     * (observed in the field) is an anchored regex like `^\( x \)$` against a
+     * mid-document string: ^/$ bind to the whole full_text, so it never matches
+     * even though the literal `( x )` is present. We strip regex anchoring/escapes
+     * and probe full_text for a literal occurrence; if found, we tell the model
+     * the exact literal that WOULD match so it drops the anchors instead of
+     * escalating the regex further.
+     */
+    private _nearest_match_hint;
     private _build_edit_context_previews;
     private _scan_existing_ids;
     private _get_heading_path_and_page;
     accept_all_revisions(): void;
+    /**
+     * Revert every tracked change, returning the document to the state it had
+     * before any revision was proposed. The exact inverse of
+     * accept_all_revisions:
+     *
+     *   - <w:ins>  -> removed together with all of its content (the proposed
+     *                 insertion never existed); an inserted row (<w:ins> in
+     *                 <w:trPr>) drops the whole row.
+     *   - <w:del>  -> unwrapped, restoring the original text (<w:delText> becomes
+     *                 <w:t> again); a row-deletion mark in <w:trPr> is removed so
+     *                 the row survives.
+     *   - paragraph-mark <w:del> in pPr/rPr -> removed, undoing a proposed merge.
+     *
+     * Comments are annotations, not revisions, so standalone comments are left in
+     * place; only anchors stranded inside a rejected insertion are cleaned up.
+     *
+     * Insertions are reverted before deletions are restored so a deletion nested
+     * inside a foreign author's insertion is removed wholesale with the insertion
+     * — the contingent text disappears rather than being promoted to committed
+     * body text.
+     *
+     * Known limitation: tracked paragraph STRUCTURE changes (a split recorded as a
+     * pilcrow <w:ins>, or a merge recorded as a pilcrow <w:del>) are reverted only
+     * to the extent of dropping/keeping the mark; the original paragraph boundary
+     * is not reconstructed, because the merge protocol coalesces paragraphs
+     * destructively at edit time. Reverting run-level insertions/deletions (the
+     * common case) is exact. This limitation is shared with the Python engine.
+     */
+    reject_all_revisions(): void;
     private _getNextId;
     private _create_track_change_tag;
     private _set_text_content;
@@ -268,7 +307,7 @@ declare class RedlineEngine {
     private _anchor_reply_comment;
     private _clean_wrapping_comments;
     private _delete_comments_in_element;
-    validate_edits(edits: any[]): string[];
+    validate_edits(edits: any[], index_offset?: number): string[];
     validate_review_actions(actions: any[]): string[];
     process_batch(changes: DocumentChange[], dry_run?: boolean): any;
     private _process_batch_internal;
@@ -276,6 +315,15 @@ declare class RedlineEngine {
     apply_review_actions(actions: any[]): [number, number];
     private _apply_table_edit;
     private _pre_resolve_heuristic_edit;
+    /**
+     * Split a <w:ins> so that everything up to and INCLUDING split_after stays in
+     * a left <w:ins>, new_elem is placed between, and the remainder moves to a
+     * right <w:ins> — all at the grandparent level. Used when revising another
+     * author's pending insertion: the <w:del> stays nested in their <w:ins> while
+     * our replacement <w:ins> lands as a sibling, so we never nest <w:ins> in
+     * <w:ins>.
+     */
+    private _insert_and_split_ins;
     private _apply_single_edit_indexed;
 }