One blank line between sections and a mailto link for the reporting address, as Codacy's markdownlint asks; the text is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
The code of conduct inherited from Catch2 was Contributor Covenant 1.4. It becomes version 3.0, the text every public Progmasoft repository now carries: reports go to support@progmasoft.com, read by the maintainers as the Community Moderators, and the enforcement ladder applies as the Covenant writes it. The file keeps the Covenant's CC-BY-SA-4.0 license. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
Number versions MAJOR.MINOR.PATCH in the version tool
NextPatch added one to the patch without a check, so a patch at std::numeric_limits<unsigned>::max() wrapped to 0 and --next would have moved the version back. It returns nothing there now; tests cover a three- and a four-number version at the limit. Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
Progmasoft repositories use Semantic Versioning since 2026-11-12, but //tools:version still knew the four-number counters: given 0.4.0 it wrote 0.4.0.0 everywhere, and --next stepped the fourth number. - A Version is three numbers; ParseVersion takes exactly three, without leading zeros, and FormatVersion writes three. - --next is the next patch release. It also follows a four-number version as the rule says: the fourth number goes and the patch rises, so 0.3.0.2 is followed by 0.3.1. - ReleaseNotesOf finds a section by the version it was published as. Its fallback for "D = 0" read the fourth element of what is now a three-element array; it is gone. - Tests for the new parsing, NextPatch and release-note lookup; docs/contributing.md and the tool's usage say what the tool does. Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
Keep per-test coverage with --coverage (roadmap step 4)
A function-local static std::mutex has an exit-time destructor, which the macOS build rejects with -Wexit-time-destructors. The lock is now allocated once and never destroyed, which also keeps it usable by a thread that starts a child while the process exits.
Reading the coverage profiles on several threads broke an assumption of ChildProcess::Start on POSIX: it changes the working directory of the whole process around posix_spawn. Two gcov runs started at once could both run in one test's directory, so on the GCC job the map of "Subtracts one" showed what "Adds one" reached. - ChildProcess::Start holds a lock while a child starts, on POSIX and Windows, so the directory change and the handles a child inherits never overlap with another start. - gcov gets the absolute path of the data file and no working directory, so no directory changes while profiles are read in parallel.
- gcov is run with --branch-probabilities; without it the JSON has no branches, so GCC runs had none in coverage.json and coverage.lcov. - PrepareCoverageDirectory also removes coverage.json, coverage.lcov and coverage.profdata of an earlier run, so a run that writes no reports leaves none to be read as its own. - WriteCoverageReports returns notes and failures apart. A profile the tools cannot read or a report that cannot be written counts as a missing report and fails a run whose tests passed; no profiles or missing tools stay notes. The paths are announced only for the reports written. - ProfiledAttempt takes the last attempt whose profile exists, so a final retry or repeat that crashed before writing one no longer hides the coverage of the attempt before it. - The per-test llvm-profdata/llvm-cov and gcov runs use as many threads as the run had workers; results keep the order of the tests. Tests: earlier reports removed and no failure without profiles; an attempt without a profile gives way to an earlier one; the fixture gains a branch taken one way, checked in the combined LCOV for both LLVM and gcov. Amalgamation regenerated.