Separate correctness comments from style preferences

A code review comment is more actionable when it points to a specific behavior or edge case, rather than a vague preference. Keep correctness concerns distinct from naming or formatting suggestions.