feat: enforce default no comments

[ulemons]

Summary

enforce default no comments

Type of change

• Bug fix
• New feature
• Refactor / cleanup
• Performance improvement
• Chore / dependency update
• Documentation

[cursor]

PR Summary

Low Risk
Documentation-only change to AI/contributor guidelines; no runtime or application code is modified.

Overview
Tightens contributor guidance in CLAUDE.md from a short “default to no comments” note to an explicit no-comments policy with narrow exceptions.

The Code quality section now requires self-explanatory code (naming and extraction over explanation), lists when comments are allowed (external workarounds, non-obvious invariants, performance constraints, unavoidable legacy complexity, ticketed TODO(CM-XXX)), and forbids routine comments (what the code does, section headers, obvious JSDoc, change notes). Allowed comments stay capped at two lines.

^{Reviewed by Cursor Bugbot for commit 04f3d10. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[Copilot]

Pull request overview

Strengthens project guidance to discourage explanatory code comments and define narrow exceptions.

Changes:

• Requires self-explanatory code.
• Defines allowed comment categories and a two-line limit.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[skwowet]

LTGM

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

CLAUDE.md:76

• The exhaustive exception list omits mandatory copyright/SPDX license headers, even though this repository treats missing license headers as a review violation. As written, assistants may avoid adding or remove required headers. Explicitly exempt required license headers.

- A comment is allowed ONLY if one of these is true, and the reason cannot be
  expressed in code:
  - workaround for an external bug/API quirk (link it)