* docs(claude): a PR has to pass the Sonar quality gate, not fix every remark
The section on SonarCloud asked for every remark on the changed code to
be fixed, code smells included. It now asks for the quality gate: new
code rated A for reliability, security and maintainability, duplication
at most 3%, hotspots reviewed. A remark that doesn't fail the gate needn't
be fixed, and large restructurings that only answer one stay out of the
PR. The rules that keep coming up stay listed, as the way to keep the
gate passing.
* docs(claude): what the gate's ratings mean for bugs, smells and hotspots
Every bug or vulnerability on new code drops its rating below A and
fails the gate, code smells only count together through the
maintainability rating, and a hotspot is reviewed in SonarCloud rather
than by rewriting the code.
---------
Co-authored-by: maj00r <maj00r@host>
* docs: CLAUDE.md with the team's notes for Claude Code
The rules Claude Code sessions kept relearning, shared with the team:
- the code builds and behaves the same with GCC 13 (Linux CI and the
Sonar build) as with MSVC, with the MSVC leniencies to watch for;
- every SonarCloud remark on the changed code gets fixed without
changing behaviour, with the recipes for the rules that keep coming
up;
- building, the unit tests, scripted editor runs, the game data and
the profile folders, and GPU hangs;
- the game data in the asset SVN and backward compatibility: existing
files keep being read as before, new entries are optional, code
falls back without new assets and a change that uses them says so
in its commit message, what the editor saves stays readable by the
current release, new features can be turned off in eu07.ini and
don't change the look of existing data abruptly; StarterNG is the
official starter.
* docs: CLAUDE.md on the move to OpenGL 4.6 and Vulkan
betterRenderer/ is to be removed and the OpenGL 3.3 and legacy
renderers are being replaced by feat/gl46-migration (PR #216, a draft
with milestone 27.04). Work on that code and on the shaders is kept to
fixes and to what a feature on master needs to be drawn, with the PR
saying where the branch has the counterpart.
---------
Co-authored-by: maj00r <maj00r@host>