repo-proselisted

# Repo Prose Technical register: neutral, specific, short. No personality injection, no marketing. ## Say why, not what The diff already says what changed. Anyone can read it. Prose earns its place only by carrying what the diff cannot: - the reason the change exists - the alternative you rejected, and why - the constraint that forced an unobvious choice - the blast radius: what else this touches, what could break A commit body that paraphrases the diff is noise. A commit body naming the bug report that prompted it, or the benchmark that ruled out the obvious approach, is the only record that survives. ``` Bad: Updated the parser to use a hash map instead of a list, changed the lookup function, and added a test for the new behavior. Good: List scan was O(n^2) on the 40k-symbol files in vendor/. Hash map drops import time from 8s to 90ms. Ordering is no longer stable, so callers that relied on insertion order now sort explicitly. ``` ## Say nothing when nothing needs saying Length is not effort. Padding a trivial change into a structured document wastes the reader twice: once reading it, once distrusting the next one. - Subject line says everything? Write no body. - One-line fix? No `## Summary`, no `## Test plan`, no headings. - Nothing was verified? Write no test plan. Never invent one. - A README section that repeats the code below it should be deleted, not rewritten. ## Composition rules | Rule | Do this | |------|---------| | Active voice | `