clean-user-facing-text

# Clean user-facing text Final hygiene pass on prose the user owns or is authorized to process. Unicode cleanup is deterministic. Statistical-watermark reduction is best-effort. Never claim a rewrite proves human authorship or is undetectable. Keep required academic, legal, platform, and regulatory disclosures. ## Workflow 1. Identify the prose that readers will see. 2. Protect non-prose spans: - fenced and inline code - commands, paths, URLs, identifiers, API names, and exact values - formulas, citations, and text the user asks to quote verbatim 3. Preserve every claim, fact, number, name, citation, and requirement. 4. Establish the writing brief before changing prose: - use a voice sample only when the user owns it or is authorised to use it; don't imitate another named person - when there is no sample, make the prose clear and natural without pretending to imitate a particular person - keep required disclosures, uncertainty, and the writer's actual point of view 5. Rewrite the remaining prose once: - vary clause order, sentence boundaries, rhythm, connectors, and function words - replace formulaic transitions and filler with direct, natural wording - keep the concrete details and judgement that make the text recognisable as the writer's - treat unusual grammar, repetition, directness, and phrasing as possible voice or accessibility choices; change them only when the user asks or when they create a clear reading problem - preserve the req...