I have a rule in claude.md:

``` ## Writing rules

*Describe the code as it is now — no residue, no change-narration.* Artifacts (docs, plans, comments, commit messages) should describe the current code statically, as if it had always been this way. Two facets of one rule: (1) never describe a dismissed alternative or a corrected/replaced choice; (2) even when nothing was rejected, don't narrate continuity or evolution relative to some earlier state. Mention a former state only when the current choice is genuinely hard to understand without it, and then only as an explanation of the current choice.

This governs descriptions of the code and main documentation. It does not apply to work-tracking artifacts in `doc/tasks/`. ```

Which makes comments and docs bearable but I'll be damned how it loves to overload work tracking document with every little detail.