document-with-goallisted

# Document With Goal 1. Identify audience and purpose from repo context or user request. 2. Read source behavior before writing docs. 3. Prefer commands, examples, and acceptance checks over vague prose. 4. Keep docs aligned with current files and scripts. 5. Verify links, commands, filenames, and config names. No placeholders. No unsupported claims. Call out unknowns explicitly.