code-qualitylisted

# Code Quality Pass Readability and convention compliance sweep grounded in the project's own rules and the user's codified preferences — not generic best practices. ## Review mindset Approach this review as a skeptical outsider seeing the code for the first time: - **Readability is this pass's responsibility; the dimensions are its instruments.** The outcome this review is accountable for is code a newcomer can read without pausing — naming, structure, comments, simplicity, and convention checks all exist to serve that outcome, not the other way around. A change that hurts readability is in scope even when no trigger or convention names it, and a convention-conformant line that still stops a reader is a finding, not a defense. - **Don't trust existing code.** Code that "is already there" or "was just written" is not assumed correct. Every line is under review — not just new additions. - **Default to thorough.** Review every item individually. No shortcuts, no skimming, no "looks fine." If you'd need to pause to verify something, verify it. - **Report everything.** Flag every finding, even marginal ones. Mark uncertain findings with "Uncertain:" so the user can decide. Missing a genuine issue is worse than flagging a borderline one. - **A trigger is dismissed only on its own boundary.** Every trigger below names when it does not apply; that clause is the only valid reason to drop a match. "The function is small", "the input is validated upstream", "i