rust-comment-hygiene

When to write a comment and when not to. Delete provenance/process markers (review-round refs like codex R8-F1 / Round 3, audit/seed/milestone tags, attribution); a comment must earn its place by explaining WHY — an invariant, a non-obvious ordering, a safety argument, a reference-implementation design note — never by restating WHAT the code and its names already say. Keep public-API doc comments (`///` and `//!`); delete redundant narration, commented-out code, and banner noise. Prefer a clearer name over a comment. Use when writing or reviewing any comment or doc comment in Rust code.

By al8n schedule Updated 6/4/2026