Document Editing

The system SHALL set both original_attachment_id AND ticket_id on outgoing document attachments.

The system SHALL retrieve the most recent previously-sent clean draft using original_attachment_id linkage.

The system SHALL generate incremental redlines showing only changes made since the previous AI-generated draft.

The system SHALL continue generating cumulative redlines showing all changes from the original document.

The system SHALL generate both cumulative and incremental redline PDFs when a previous draft exists.

The system SHALL generate edit snippets in the cover note based on incremental changes (since last sent draft), not cumulative changes.

The system SHALL automatically apply bold formatting to explicit definition terms when inserting new definitions, using the document's existing definition style as a role model.

When document edits are finalized, the system SHALL generate HTML snippets showing the changes made to the document. Snippets display deleted text with red strikethrough and inserted text with blue underline.

The document editing workflow SHALL include a "Snippets of Changes Made" section in the cover email body, showing visual representation of text changes.

The system SHALL support an optional citation field on edit tools (smart_edit, smart_insert) to track the source of each edit for traceability.

The system SHALL define an EditCitation model to capture edit provenance.

The smart_edit_word_document tool SHALL accept an optional rationale_to_share_with_opposing_counsel parameter that, when provided, inserts a comment on the edited paragraph.

The smart_insert_paragraph tool SHALL accept an optional rationale_to_share_with_opposing_counsel parameter that, when provided, inserts a comment on the newly inserted paragraph.

The system MUST provide an insert_multiple_paragraphs tool that allows inserting multiple paragraphs in a single function call with automatic $LAST_INSERT chaining.

When the AI performs a DELETE operation (replacing text with empty string) that would remove an entire list item's content, and that list item is not the last item in its list, the system SHALL replace the deletion with [Intentionally omitted.] instead of actually deleting the content.

This preserves list numbering and prevents downstream section references from becoming stale.

The system SHALL provide a delete_paragraph tool that removes a paragraph from a Word document by its structural para-N identifier, without requiring text-based string matching.

The tool SHALL:
- Accept a file_path parameter identifying the document attachment
- Accept a paragraph_id parameter in para-N format (e.g., para-15)
- Accept an optional rationale_to_share_with_opposing_counsel parameter
- Use get_paragraph_by_id() to locate the target paragraph
- Remove the paragraph via Aspose DOM operations
- Use run_document_modification() for file lifecycle management

When a rationale is provided, the system SHALL insert a Word comment on the paragraph immediately following the deleted paragraph (or preceding, if the deleted paragraph was last).