MIL-011 tasks 2 to 4: the default tools-ref is the current major

code-metrics.yml defaulted tools-ref to v1 and its guide said @v1, but
the workflow and its scripts exist only from v2.1.0. The default of the
five reusable workflows is now the current major, defined once in
MAJOR_TAG, and tests/test_tools_ref.py fails when a default differs from
it or names a tag without the script. Guides, README and wiki (en, da,
ms) call code-metrics.yml at @v2; ADR-0005, 0008, 0009 and 0010 carry
an amendment; RC-077 accepts the milestone's task 1 results.

Task: MIL-011#2

guides/code-metrics.md

@@ -34,7 +34,7 @@ jobs:
     needs: tests
     permissions:
       contents: write
-    uses: TirSystem/github-action/.gitea/workflows/code-metrics.yml@v1
+    uses: TirSystem/github-action/.gitea/workflows/code-metrics.yml@v2
     with:
       coverage-artifact: coverage
       coverage-report: coverage.xml
@@ -49,9 +49,9 @@ jobs:
 | `coverage-warn` | `60` | Coverage in percent below which the badge is red |
 | `coverage-good` | `80` | Coverage in percent from which the badge is green; in between it is yellow |
 | `badges-branch` | `badges` | Branch that holds the badge files; it is created when it does not exist |
-| `tools-ref` | `v1` | Tag or branch of `TirSystem/github-action` from which the scripts in `tools/` are fetched |
+| `tools-ref` | `v2` | Tag or branch of `TirSystem/github-action` from which the scripts in `tools/` are fetched |
 
-Reference the workflow at the major tag (`@v1`) or at an exact tag, never at
+Reference the workflow at the major tag (`@v2`) or at an exact tag, never at
 `main`. A call at an exact tag is pinned completely only when `tools-ref` names
 the same tag. See the upgrade guide. Start the workflow on pushes to your
 default branch only: the badge commit carries `[skip ci]` and is made with the

guides/quality-checks-cpp.md

@@ -31,7 +31,7 @@ jobs:
 | `compile-commands-dir` | empty | Directory, relative to the repository root, with a `compile_commands.json` that your pipeline built before the call; when set, clang-tidy uses it and ignores `std` |
 | `clang-format-version` | `23.1.3` | Exact version of the clang-format package |
 | `clang-tidy-version` | `22.1.8` | Exact version of the clang-tidy package |
-| `tools-ref` | `v1` | Tag or branch of `TirSystem/github-action` from which the script `tools/quality-checks-cpp.sh` is fetched |
+| `tools-ref` | `v2` | Tag or branch of `TirSystem/github-action` from which the script `tools/quality-checks-cpp.sh` is fetched |
 
 Reference the workflow at the major tag (`@v1`) or at an exact tag, never at
 `main`. A call at an exact tag is pinned completely only when `tools-ref` names

guides/quality-checks-csharp.md

@@ -30,7 +30,7 @@ jobs:
 | `working-directory` | `.` | Directory, relative to the repository root, whose files are checked |
 | `project` | empty | Solution or project file, relative to `working-directory`; empty uses the single `*.sln` or `*.slnx`, else the single `*.csproj`, that is tracked there |
 | `dotnet-sdk-version` | `10.0.401` | Exact version of the .NET SDK, 10 or later; a channel such as `10.0`, a range and a version below 10 are refused |
-| `tools-ref` | `v1` | Tag or branch of `TirSystem/github-action` from which the script `tools/quality-checks-csharp.sh` is fetched |
+| `tools-ref` | `v2` | Tag or branch of `TirSystem/github-action` from which the script `tools/quality-checks-csharp.sh` is fetched |
 
 Reference the workflow at the major tag (`@v1`) or at an exact tag, never at
 `main`. A call at an exact tag is pinned completely only when `tools-ref` names

guides/quality-checks.md

@@ -32,7 +32,7 @@ jobs:
 | `mypy-version` | `1.11.2` | Version of mypy |
 | `shellcheck-py-version` | `0.10.0.1` | Version of the shellcheck-py package (ShellCheck 0.10.0) |
 | `shfmt-py-version` | `3.11.0.2` | Version of the shfmt-py package (shfmt 3.11.0) |
-| `tools-ref` | `v1` | Tag or branch of `TirSystem/github-action` from which the script `tools/quality-checks.sh` is fetched |
+| `tools-ref` | `v2` | Tag or branch of `TirSystem/github-action` from which the script `tools/quality-checks.sh` is fetched |
 
 Reference the workflow at the major tag (`@v1`) or at an exact tag
 (`@v1.0.0`), never at `main` and never at the branch of a pull request: that

guides/upgrading.md

@@ -18,7 +18,7 @@ never receives it until you change the line yourself.
 
 The quality-checks workflows (`quality-checks.yml`, `quality-checks-cpp.yml` and
 `quality-checks-csharp.yml`) and the code-metrics workflow (`code-metrics.yml`)
-fetch their scripts at their input `tools-ref`, which defaults to `v1`. To pin one completely, call it at an exact tag and set
+fetch their scripts at their input `tools-ref`, which defaults to the current major tag (`v2`). To pin one completely, call it at an exact tag and set
 `tools-ref` to the same tag; otherwise the script follows the major tag.
 
 The scoped workflow **Sync GitHub mirror metadata** is delivered by the