signature-ready-checklisted

# Signature-ready check Read a PDF or DOCX and report everything that would embarrass the sender if it went out as-is. This runs entirely locally and calls no Propper tools, so it works with or without an account. ## Steps ### 1. Read the document Extract the full text, keeping page numbers. Use whatever tooling the environment has: `pdftotext -layout`, `pdfplumber`, `pypdf` for PDF; `python-docx` or unzipping `word/document.xml` for DOCX. Read every page, including exhibits and schedules. Never report a document clean on a partial read. If extraction fails on some pages, say which pages were unreadable. ### 2. Run the seven checks **Blanks and placeholders.** Runs of underscores, `[ ]`, `[BRACKETED TEXT]`, `TBD`, `TBC`, `XXX`, `N/A` where a value is expected, `{{merge_field}}`, `<<FIELD>>`, `«Field»`, `Lorem ipsum`, `insert`, `to be determined`. Report each with its page and the surrounding sentence. Distinguish a blank a signer is meant to fill at signing from a blank the sender forgot. A signature line is the former. `Effective Date: ________` at the top of the document is usually the latter. **Entity names.** Collect every party name in the document, including the preamble, the definitions, the body and the signature blocks. Report any variation: `Acme, Inc.` versus `Acme Inc` versus `ACME Incorporated`, a defined term used before it is defined, a defined term that is never used, and a party named in a signature block who appears nowhere else. Entity-suffix misma