polish-open-source-proselisted

# Polish Open-Source Prose Improve project prose without treating a blacklist or detector score as a style guide. Preserve the author's meaning and make every edit earn its place. ## Select the task - For an **audit**, identify exact passages, explain the concrete problem, assign a severity, and propose the smallest useful revision. Do not claim that a pattern proves AI authorship. - For a **rewrite**, edit only the requested files or passages. Keep the existing voice unless the user asks for a new one. - For a **draft**, inspect the repository for facts and established terminology before writing. Mark missing facts instead of inventing them. - For a **repository sweep**, prioritize entry-point prose: README, docs index, contribution guide, package description, landing page, and current release notes. Exclude archives, vendored text, generated files, fixtures, and translations unless the user includes them. - For a **provenance question**, separate editorial quality from proof of origin. Read [references/provenance.md](references/provenance.md) before recommending a watermark, signature, or attestation. ## Load only relevant guidance - Read [references/patterns-en.md](references/patterns-en.md) for English prose. - Read [references/patterns-zh.md](references/patterns-zh.md) for Chinese prose. - For `zh-Hant-TW` or prose aimed at readers in Taiwan, also read [references/locales/zh-Hant-TW.md](references/locales/zh-Hant-TW.md). - When adding another loc