eliziff stops Word files quietly rewriting numbers

A small parsing fix protects visible document text when a Word file is opened, edited and saved.

draftingworkflow

eliziff has closed a subtle but consequential document-integrity gap. Text that merely looked like a number or a yes-or-no value could be treated as data rather than text, changing 12.10 to 12.1 when the document was saved.

That matters because the altered text did not need to be part of the requested edit. A tracked change elsewhere in the document could still cause an untouched passage to be rewritten. The update keeps visible Word text exactly as written while preserving the existing handling for document structure, tracked edits and spacing.

The team also added checks covering both extracted text and the saved document, so the same regression should be caught before it reaches users.

So what Legal teams relying on Word-based drafting or review should care because apparently minor formatting can carry real contractual or evidential meaning.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from eliziff/Beaver, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
c6b3fb3c fix(docx): disable numeric coercion of Word text runs Eli Ziff 2026-08-12 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1273.md from inside the repo you want the changes in.

⬇ Download capture-thread-1273.md