writing-stylelisted

# Writing Style Universal writing rules for all generated content intended for human readers: PR descriptions, review comments, ticket descriptions, ADRs, Confluence pages, Slack messages, Jira tickets. These rules are MUST-level unless marked SHOULD. > **IRON RULE:** MUST NEVER use em dashes or en dashes in any output, and MUST write in simple, plain English (common words, short sentences). This applies to every file, comment, commit message, and generated text. Use commas, colons, or periods instead of dashes. Both dash types are strong AI tells; fancy vocabulary and long sentences are too. Use straight quotes (`"`, `'`), never curly/smart quotes (`"`, `"`, `'`, `'`); same ASCII-only reasoning as the dash rule. > **IRON RULE:** MUST NEVER write a code or doc comment unless it is one of: a doc block at a module, library, or public-helper-function boundary; a warning that the operation is expensive; a warning that the operation is destructive or dangerous; an explanation of why the code does something that looks odd; a deprecation notice; context for a return type or value the signature doesn't make clear; or, at a class/type level only, context for a service class (which service this is) or a DTO (what the shape means). MUST NEVER restate what the code already shows. Say it in one sentence by default, a second only for a genuinely non-obvious mechanism; wrap a long line instead of writing one unwrapped line, don't pad a short comment into extra lines. Write for the code'