github.com/classicq/classicq

## Code style

Comments are sparse or absent. Match classicQ's existing one-line
`// short note` style. No multi-paragraph block essays explaining
rationale, alternatives considered, or development phases.

When in doubt, delete the comment. Source code prioritizes clarity
of code itself over explanation. Development notes (decisions,
debugging state, lessons learned) belong in `notes/` (gitignored),
not in source comments.

No em dashes (—) or en dashes (–). Use a regular hyphen instead.