Resolve the pending commit link in MIL-007

Use current tool versions only for MIL-007: .NET SDK 10 or later
2026-10-11 12:31:25 +08:00 · 2026-10-11 12:31:24 +08:00
28 changed files with 47 additions and 2150 deletions
@@ -23,13 +23,12 @@ jobs:
    permissions:
      contents: read
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
      - name: Check out the repository
-        uses: actions/checkout@v4.2.2
+        uses: actions/checkout@v4
      - name: Fetch the shared script
-        uses: actions/checkout@v4.2.2
+        uses: actions/checkout@v4
        with:
          repository: TirSystem/github-action
          ref: v1
@@ -16,10 +16,9 @@ jobs:
    permissions:
      contents: read
    runs-on: ubuntu-latest
    timeout-minutes: 5
    steps:
      - name: Fetch the shared script
-        uses: actions/checkout@v4.2.2
+        uses: actions/checkout@v4
        with:
          repository: TirSystem/github-action
          ref: v1
@@ -1,72 +0,0 @@
 name: Quality checks C++
 # Reusable workflow (ADR-0008). A repository calls it with
 #
 #   jobs:
 #     quality:
 #       uses: TirSystem/github-action/.gitea/workflows/quality-checks-cpp.yml@v1
 #
 # It checks the C and C++ files of the repository with clang-format and
 # clang-tidy at exact versions, changes no file and needs no secret. The
 # repository needs a .clang-format; a .clang-tidy and a compile database
 # (compile-commands-dir) are optional.
 on:
  workflow_call:
    inputs:
      working-directory:
        description: "Directory, relative to the repository root, whose files are checked"
        type: string
        default: "."
      std:
        description: "C++ standard for clang-tidy when no compile database is given, such as c++20"
        type: string
        default: "c++20"
      compile-commands-dir:
        description: "Directory with a compile_commands.json built by the caller before the call; empty uses the std input"
        type: string
        default: ""
      clang-format-version:
        description: "Exact version of the clang-format package"
        type: string
        default: "23.1.3"
      clang-tidy-version:
        description: "Exact version of the clang-tidy package"
        type: string
        default: "22.1.8"
      tools-ref:
        description: "Tag or branch of TirSystem/github-action whose tools/quality-checks-cpp.sh is run; pin it to the exact tag together with the workflow"
        type: string
        default: "v1"
 jobs:
  quality-checks-cpp:
    permissions:
      contents: read
    runs-on: ubuntu-latest
    timeout-minutes: 15
    env:
      WORKING_DIRECTORY: ${{ inputs.working-directory }}
      STD: ${{ inputs.std }}
      COMPILE_COMMANDS_DIR: ${{ inputs.compile-commands-dir }}
      CLANG_FORMAT_VERSION: ${{ inputs.clang-format-version }}
      CLANG_TIDY_VERSION: ${{ inputs.clang-tidy-version }}
      QC_VENV: /tmp/quality-tools
    steps:
      - name: Check out the repository
        uses: actions/checkout@v4.2.2
      - name: Fetch the shared script
        uses: actions/checkout@v4.2.2
        with:
          repository: TirSystem/github-action
          ref: ${{ inputs.tools-ref }}
          path: shared-scripts
      - name: Validate the inputs
        run: bash shared-scripts/tools/quality-checks-cpp.sh validate
      - name: Install the tools
        run: bash shared-scripts/tools/quality-checks-cpp.sh install
      - name: Run the checks
        run: bash shared-scripts/tools/quality-checks-cpp.sh run
@@ -1,61 +0,0 @@
 name: Quality checks C#
 # Reusable workflow (ADR-0008). A repository calls it with
 #
 #   jobs:
 #     quality:
 #       uses: TirSystem/github-action/.gitea/workflows/quality-checks-csharp.yml@v1
 #
 # It checks the C# solution or project of the repository with `dotnet format`
 # and `dotnet build` (warnings as errors) on an exact .NET SDK 10 or later,
 # changes no file and needs no secret. The package restore needs the network.
 on:
  workflow_call:
    inputs:
      working-directory:
        description: "Directory, relative to the repository root, whose files are checked"
        type: string
        default: "."
      project:
        description: "Solution or project file, relative to working-directory; empty uses the single .sln, .slnx or .csproj found"
        type: string
        default: ""
      dotnet-sdk-version:
        description: "Exact .NET SDK version, 10 or later (no channel, no range)"
        type: string
        default: "10.0.401"
      tools-ref:
        description: "Tag or branch of TirSystem/github-action whose tools/quality-checks-csharp.sh is run; pin it to the exact tag together with the workflow"
        type: string
        default: "v1"
 jobs:
  quality-checks-csharp:
    permissions:
      contents: read
    runs-on: ubuntu-latest
    timeout-minutes: 15
    env:
      WORKING_DIRECTORY: ${{ inputs.working-directory }}
      PROJECT: ${{ inputs.project }}
      DOTNET_SDK_VERSION: ${{ inputs.dotnet-sdk-version }}
      DOTNET_ROOT: /tmp/dotnet
    steps:
      - name: Check out the repository
        uses: actions/checkout@v4.2.2
      - name: Fetch the shared script
        uses: actions/checkout@v4.2.2
        with:
          repository: TirSystem/github-action
          ref: ${{ inputs.tools-ref }}
          path: shared-scripts
      - name: Validate the inputs
        run: bash shared-scripts/tools/quality-checks-csharp.sh validate
      - name: Install the .NET SDK
        run: bash shared-scripts/tools/quality-checks-csharp.sh install
      - name: Run the checks
        run: bash shared-scripts/tools/quality-checks-csharp.sh run
@@ -45,7 +45,6 @@ jobs:
    permissions:
      contents: read
    runs-on: ubuntu-latest
    timeout-minutes: 15
    env:
      LANGUAGES: ${{ inputs.languages }}
      WORKING_DIRECTORY: ${{ inputs.working-directory }}
@@ -56,10 +55,10 @@ jobs:
      QC_VENV: /tmp/quality-tools
    steps:
      - name: Check out the repository
-        uses: actions/checkout@v4.2.2
+        uses: actions/checkout@v4
      - name: Fetch the shared script
-        uses: actions/checkout@v4.2.2
+        uses: actions/checkout@v4
        with:
          repository: TirSystem/github-action
          ref: ${{ inputs.tools-ref }}
@@ -26,10 +26,9 @@ jobs:
    permissions:
      contents: write
    runs-on: ubuntu-latest
    timeout-minutes: 15
    steps:
      - name: Check out the repository
-        uses: actions/checkout@v4.2.2
+        uses: actions/checkout@v4
      - name: Check and publish the release
        env:
@@ -1,78 +0,0 @@
 # Publish accepted milestones to the git host.
 #
 # On a push to main that changes docs/milestones/ or docs/sqa/reviews/, this
 # workflow runs `sync-project.sh --accepted-only --apply`: every milestone whose
 # latest Version History row is Accepted and whose latest review record is a Go
 # is created or updated as a Milestone with its tasks as Issues. A Proposed
 # milestone, or one without a Go review, is skipped. Nothing is closed or
 # deleted. Each run updates the issues of every accepted milestone (the sync is
 # idempotent, but the host records the edit).
 #
 # INSTALLING THIS FILE IS THE STANDING AUTHORIZATION TO PUBLISH. This project
 # installed it on 2026-10-11 at the request of S01.
 #
 # Secret: TOKEN_FOR_GITEA, the bare Gitea token of the organization (no JSON).
 # It needs read and write on issues and milestones, and read on the framework
 # repository, which is checked out as a submodule. Gitea does not accept secret
 # names that start with GITEA_ or GITHUB_.
 #
 # Run it once by hand from the Actions page with dry_run left on: it prints
 # the plan and creates nothing. Turn dry_run off only for a real run.
 # A runner must be registered for the repository (or its organisation).
 name: Publish accepted milestones
 on:
  push:
    branches: [main]
    paths:
      - "docs/milestones/**"
      - "docs/sqa/reviews/**"
  workflow_dispatch:
    inputs:
      dry_run:
        description: "Preview only: print the plan and create nothing"
        type: boolean
        default: true
 # Two merges in a row queue instead of racing.
 concurrency:
  group: publish-accepted-milestones
  cancel-in-progress: false
 jobs:
  publish:
    permissions:
      contents: read
    runs-on: ubuntu-latest
    timeout-minutes: 15
    steps:
      - name: Check out the project
        uses: actions/checkout@v4.2.2
        with:
          token: ${{ secrets.TOKEN_FOR_GITEA }}
      # .gitmodules uses ssh:// URLs and the runner has no SSH key, so the
      # submodules (framework, and framework/qc inside it) are fetched over HTTPS
      # with the same token. The token goes through the environment, not a
      # command line.
      - name: Check out the framework submodules over HTTPS
        env:
          GIT_CONFIG_COUNT: "2"
          GIT_CONFIG_KEY_0: "url.https://git.tirsystem.com/.insteadOf"
          GIT_CONFIG_VALUE_0: "ssh://git@git.tirsystem.com:10022/"
          GIT_CONFIG_KEY_1: "http.extraheader"
          GIT_CONFIG_VALUE_1: "Authorization: token ${{ secrets.TOKEN_FOR_GITEA }}"
        run: |
          set -euo pipefail
          git submodule update --init --recursive --depth=1
      - name: Make sure curl and jq are available
        run: bash framework/scripts/ci-publish-milestones.sh ensure-tools
      - name: Publish accepted milestones
        env:
          GITEA_TOKEN: ${{ secrets.TOKEN_FOR_GITEA }}
          # Empty on a push (a real run); "true" or "false" on a manual run.
          DRY_RUN: ${{ inputs.dry_run }}
        run: bash framework/scripts/ci-publish-milestones.sh publish
@@ -11,10 +11,9 @@ jobs:
    permissions:
      contents: read
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
      - name: Check out the repository
-        uses: actions/checkout@v4.2.2
+        uses: actions/checkout@v4
      - name: Create a virtual environment and install test dependencies
        run: |
@@ -15,49 +15,6 @@ framework.
 the working tree first; edit, summarise and stop. The commit/PR rules below
 apply once a commit has been asked for.
 ## Related repositories
 This project is one of four repositories that change together. Each has one
 job; a change goes to the repository that owns it, not to the one that happens
 to be open.
 | Repository | Owns | Consumed by | Pinned or released as |
 | --- | --- | --- | --- |
 | `TirSystem/SQA-QC-Checklists` | the QC checklists (`qc/artifacts/`, `qc/code/`) | `sqa-qc-framework` | a commit, pinned as the `qc/` submodule |
 | `TirSystem/sqa-qc-framework` | the skills, process documents, catalog, templates (`templates/ci/`) and scripts | every project, as the `framework/` submodule | a release tag (`v0.5.2`, ...) |
 | `TirSystem/github-action` | the shared workflows (`quality-checks`, `release`), the scoped workflows (`publish-wiki`, `sync-github-metadata`) and the scripts they call (`tools/`) | every repository of the organisation, by `uses:` and `ref:` | a release tag and a moving major tag (`v1`), made by its release workflow |
 | `TirSystem/sqa-and-qc` | the SQA and AI project management: project artifacts, review records, the traceability matrix | itself | the pull request that merges it |
 Where a thing lives:
 - A QC checklist, a convention or a template is changed in its owner above and
  reaches this project by moving the pin. The review record of a checklist is
  written in the project that reviews it (`docs/sqa/reviews/`), not in the
  checklist repository.
 - A workflow that other repositories call is changed in `github-action` and
  released there. A workflow a project copies from `templates/ci/` is changed
  in the framework; the project updates its copy after the pin moves.
 - A script a workflow needs is a file (`tools/` of `github-action`, or
  `scripts/` of the framework for the templates), never a long `run:` block
  (`QC-WF-001` criterion 20).
 - The `framework/` pin here is independent of the one in `sqa-and-qc`; the two
  may differ, and neither is moved to follow the other without a reason in
  the pull request.
 A change that spans repositories:
 1. One pull request per repository, in dependency order: checklists, then
   framework, then `github-action` and the projects. A pull request names the
   ones it depends on in its description.
 2. A downstream repository moves a pin only to a merged commit or tag of the
   upstream, never to an unmerged branch.
 3. Nothing is released or tagged until its dependencies are merged; a release
   is a separate, deliberate step (the release workflow defaults to a dry run).
 4. A related repository is added to the session as a working directory only
   when the task needs it. In autonomous mode work in a related repository is
   inside the accepted plan only if the plan names it; otherwise the run stops
   and reports.
 ## Workflow order
 Business Case, Stakeholder Analysis, Project Plan, milestones, tasks synced as
@@ -20,29 +20,6 @@ Each release lists its changes in these groups, in this order:
 ## [Unreleased]
 ### Added
 - Reusable workflow `quality-checks-cpp.yml` (ADR-0008): `clang-format --dry-run
  -Werror` and `clang-tidy` on the tracked C and C++ files, at exact versions
  (inputs `clang-format-version`, `clang-tidy-version`), with the inputs
  `working-directory`, `std`, `compile-commands-dir` and `tools-ref`. The
  repository needs a `.clang-format`.
 - Reusable workflow `quality-checks-csharp.yml` (ADR-0008): `dotnet format
  --verify-no-changes` and `dotnet build -warnaserror` on an exact .NET SDK 10
  or later (input `dotnet-sdk-version`, default `10.0.401`), with the inputs
  `working-directory`, `project` and `tools-ref`.
 ### Changed
 - Every job has a `timeout-minutes` (5 to 15), so a hung step no longer holds a
  runner for the host's default limit.
 - `actions/checkout` is referenced by the exact tag `v4.2.2` instead of the
  moving tag `v4`. No change for callers.
 - The framework pin moves from `v0.5.2` to `v0.6.0`, and the two long `run:`
  blocks of this repository's own `sync-milestones.yml` call
  `framework/scripts/ci-publish-milestones.sh`. No change for callers of the
  shared workflows.
 ## [1.1.0] - 2026-10-11
 ### Added
@@ -17,21 +17,18 @@ A collection of reusable Gitea Actions workflows for DevOps professionals and so
 This repository is the central collection of reusable automation for TirSystem repositories. The primary repository lives at `git.tirsystem.com` (Gitea) and is push-mirrored to GitHub.
-It contains eight workflows: metadata sync to the GitHub mirror, wiki publishing, shared quality checks for Python and shell, for C and C++ and for C#, a release workflow, the publishing of accepted milestones and the repository's own validation. They are listed with their purpose and a diagram under [Workflows](#-workflows).
+It contains five workflows: metadata sync to the GitHub mirror, wiki publishing, shared quality checks, a release workflow and the repository's own validation. They are listed with their purpose and a diagram under [Workflows](#-workflows).
 ## 🔧 Workflows
-Eight workflows live in this repository. A **scoped** workflow is delivered by the instance to every repository of the TirSystem organizations and needs nothing in the repository; a **reusable** workflow is called by a repository with `uses:`; the others run only here. The diagrams are PlantUML source.
+Five workflows live in this repository. A **scoped** workflow is delivered by the instance to every repository of the TirSystem organizations and needs nothing in the repository; a **reusable** workflow is called by a repository with `uses:`; the others run only here. The diagrams are PlantUML source.
 | Workflow | File | Kind | Starts on | Purpose |
 | --- | --- | --- | --- | --- |
 | Sync GitHub mirror metadata | [`sync-github-metadata.yml`](.gitea/scoped_workflows/sync-github-metadata.yml) | Scoped | push to `main`, manual, daily 03:17 UTC | Copies the description and topics of a Gitea repository to its GitHub push mirror |
 | Publish wiki | [`publish-wiki.yml`](.gitea/scoped_workflows/publish-wiki.yml) | Scoped, opt-in with `wiki/.publish` | push to `main` that changes `wiki/**`, manual | Publishes the pages in `wiki/` to the repository wiki |
 | Quality checks | [`quality-checks.yml`](.gitea/workflows/quality-checks.yml) | Reusable (`workflow_call`) | a call from another repository | Runs ruff, mypy, shellcheck and shfmt on the tracked files and changes nothing |
 | Quality checks C++ | [`quality-checks-cpp.yml`](.gitea/workflows/quality-checks-cpp.yml) | Reusable (`workflow_call`) | a call from another repository | Runs clang-format and clang-tidy at exact versions on the tracked C and C++ files and changes nothing |
 | Quality checks C# | [`quality-checks-csharp.yml`](.gitea/workflows/quality-checks-csharp.yml) | Reusable (`workflow_call`) | a call from another repository | Runs `dotnet format` and `dotnet build` on an exact .NET SDK 10 or later and changes nothing |
 | Release | [`release.yml`](.gitea/workflows/release.yml) | This repository only | manual | Creates the version tag, the release page and the major tag after the checks |
 | Publish accepted milestones | [`sync-milestones.yml`](.gitea/workflows/sync-milestones.yml) | This repository only | push to `main` that changes `docs/milestones/**` or `docs/sqa/reviews/**`, manual (dry run by default) | Creates or updates the Gitea milestone and issues of every milestone that is Accepted with a Go review |
 | Validate workflows | [`validate-workflows.yml`](.gitea/workflows/validate-workflows.yml) | This repository only | pull request, push to `main`, manual | Parses every workflow and runs the offline tests |
 ### 🔄 Sync GitHub metadata
@@ -190,96 +187,6 @@ deactivate Workflow
@enduml
 ```
 ### 🧱 Quality checks C++
 A reusable workflow for C and C++, called with `uses: TirSystem/github-action/.gitea/workflows/quality-checks-cpp.yml@v1` (ADR-0008). The repository needs a `.clang-format`; a `.clang-tidy` and a compile database are optional.
 #### 🔀 Workflow
 ```plantuml
@startuml
 title Shared quality checks for C and C++ (reusable workflow)
 autonumber
 actor "Calling repository\nuses: ...quality-checks-cpp.yml@v1" as Caller
 participant "Gitea Actions\nquality-checks-cpp" as Workflow
 participant "PyPI" as PyPI
 Caller -> Workflow: workflow_call with working-directory, std,\ncompile-commands-dir and tool versions
 activate Workflow
 Workflow -> Workflow: Check out the caller and the shared script
 Workflow -> Workflow: Validate the inputs
 alt an input is invalid or a version is not exact
  Workflow --> Caller: Fail with [configuration]
 end
 Workflow -> PyPI: Install clang-format and clang-tidy at the exact versions
 PyPI --> Workflow: Tools installed
 alt no C or C++ file is tracked
  Workflow --> Caller: Notice: nothing was checked, pass
 else no .clang-format, or compile-commands-dir\nwithout compile_commands.json
  Workflow --> Caller: Fail with [configuration]
 else
  Workflow -> Workflow: clang-format --dry-run -Werror on all files
  Workflow -> Workflow: clang-tidy on the C++ files (-std=std)\nand on the C files (or with the compile database)
  alt any tool failed
    Workflow --> Caller: Fail with tool, file and line in the log
  else
    Workflow --> Caller: All selected checks passed
  end
 end
 deactivate Workflow
@enduml
 ```
 ### 🟣 Quality checks C#
 A reusable workflow for C#, called with `uses: TirSystem/github-action/.gitea/workflows/quality-checks-csharp.yml@v1` (ADR-0008). It installs the exact .NET SDK given by `dotnet-sdk-version` (10 or later) and needs the network for the package restore.
 #### 🔀 Workflow
 ```plantuml
@startuml
 title Shared quality checks for C# (reusable workflow)
 autonumber
 actor "Calling repository\nuses: ...quality-checks-csharp.yml@v1" as Caller
 participant "Gitea Actions\nquality-checks-csharp" as Workflow
 participant "dot.net\n(dotnet-install.sh)" as DotNet
 Caller -> Workflow: workflow_call with working-directory,\nproject and dotnet-sdk-version
 activate Workflow
 Workflow -> Workflow: Check out the caller and the shared script
 Workflow -> Workflow: Validate the inputs
 alt an input is invalid or the SDK is not an exact\nstable version 10 or later
  Workflow --> Caller: Fail with [configuration]
 end
 Workflow -> DotNet: Install the exact .NET SDK version
 DotNet --> Workflow: SDK installed
 alt no C# file is tracked
  Workflow --> Caller: Notice: nothing was checked, pass
 else no solution or project, or several without the project input
  Workflow --> Caller: Fail with [configuration] that names them
 else
  Workflow -> Workflow: dotnet format --verify-no-changes
  Workflow -> Workflow: dotnet build -warnaserror\n(package restore needs the network)
  alt any tool failed
    Workflow --> Caller: Fail with tool, file and line in the log
  else
    Workflow --> Caller: All selected checks passed
  end
 end
 deactivate Workflow
@enduml
 ```
 ### 🏷️ Release
 Started by hand by a maintainer; with `dry_run` `true` (the default) it only checks (see the [release process](guides/release-process.md)).
@@ -329,54 +236,6 @@ deactivate Workflow
@enduml
 ```
 ### 📌 Publish accepted milestones
 Standing authorization to publish: on a push to `main` that changes the milestones or their reviews, every milestone whose latest Version History row is Accepted and whose latest review is a Go is created or updated on Gitea with its tasks as issues. Nothing is closed or deleted. A manual run is a dry run unless `dry_run` is switched off. It uses the secret `TOKEN_FOR_GITEA` and the `--accepted-only` rule of the mounted framework (v0.5.0 or later).
 #### 🔀 Workflow
 ```plantuml
@startuml
 title Publish accepted milestones (this repository)
 autonumber
 actor "Push to main that changes\ndocs/milestones/** or docs/sqa/reviews/**,\nor manual trigger" as Trigger
 participant "Gitea Actions\nsync-milestones" as Workflow
 participant "framework/scripts/\nsync-project.sh" as Script
 participant "Gitea REST API" as Gitea
 Trigger -> Workflow: Start workflow
 activate Workflow
 Workflow -> Workflow: Check out the project and the framework\nsubmodules over HTTPS with TOKEN_FOR_GITEA
 Workflow -> Script: --accepted-only (dry run)\nor --accepted-only --apply
 activate Script
 loop for each docs/milestones/mil-*.md
  alt latest Version History row is not Accepted,\nor the latest review record is not a Go
    Script -> Script: Skip with the reason on stderr
  else
    alt dry run
      Script -> Script: Print the plan, no network call
    else
      Script -> Gitea: Create or update the Milestone\nand one Issue per task row
      Gitea --> Script: Milestone and issue numbers
    end
  end
 end
 note right of Script
 Nothing is closed or deleted.
 Each real run edits the issues
 of every accepted milestone.
 end note
 Script --> Workflow: Done, or "nothing to publish"
 deactivate Script
 Workflow --> Trigger: Workflow result
 deactivate Workflow
@enduml
 ```
 ### 🧪 Validate workflows
 The repository's own validation: the offline tests that gate every pull request.
@@ -1,145 +0,0 @@
 # ADR-0008: Quality-check contract for C++ and C#
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | ADR-0008 |
 | CrossReference | [MIL-007], [UC-005], [US-001], [ADR-0005], [ADR-0006] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-11 | Deprecated | Jens Tirsvad Nielsen | S01 | Initial version | [11cba35] |
 | 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | Reviewed (RC-054): abbreviations expanded at first use and the security impact of downloading tools named | [9e7aedd] |
 Allowed Status values: `Proposed`, `Accepted`, `Rejected`, `Deprecated`, `Superseded by ADR-NNNN`.
 ---
 ## Context
 ADR-0005 defines the contract of the shared quality-check workflow for Python
 and shell: inputs with working defaults, a pinned version per tool, every tool
 runs, a failure names tool, file and line, and a language without files
 passes with a notice. MIL-007 adds C++ and C#. Two requirements came from S01
 on 2026-10-11 and bound the decision:
 - C++ and C# are separate workflows, not an extension of `quality-checks.yml`.
 - Old tools are not run: the .NET SDK is version 10 or later, and a tool that
  is only available as an old version is not used.
 Facts (MIL-007 task 2, runs 692 and 699 on `ubuntu-latest`, Ubuntu 24.04,
 root, `gcc`/`g++` 13.3 present):
 - `clang-format` 23.1.3 and `clang-tidy` 22.1.8 install from the Python Package
  Index (PyPI) in a few seconds with an exact version.
 - `cppcheck` is only available as an old version (apt 2.13.0; the latest
  release is 2.22.0; the PyPI package of that name is another project).
 - The .NET software development kit (SDK) 10.0.401 installs with the official
  `dotnet-install.sh` in about 20 s with an exact `--version`; apt gives an older band (10.0.112).
 - A `clang-tidy` run needs flags or a compile database, and a C# format check
  and build need the project's package restore, which needs the network.
 Options:
 1. **One combined workflow for C++ and C#.** One page and one place to call,
   but two unrelated toolchains in one job, and an input set that mixes both.
 2. **One workflow per language** (`quality-checks-cpp.yml`,
   `quality-checks-csharp.yml`), each with its own inputs and tools.
 3. **Extend `quality-checks.yml`** with two more values of `languages`.
   Rejected by S01 (separate workflows) and it would make the contract of
   ADR-0005 grow with every language.
 For `cppcheck`: (a) keep the apt version, (b) build a current release from
 source in every run, (c) drop it. For the SDK: (a) a channel such as `10.0`,
 (b) an exact version.
 ## Decision
 C++ and C# are checked by two separate reusable workflows,
 `quality-checks-cpp.yml` and `quality-checks-csharp.yml`, each running a script
 file of this repository (`tools/quality-checks-cpp.sh`,
 `tools/quality-checks-csharp.sh`) that it fetches at its input `tools-ref`
 (default `v1`), with the contract of ADR-0005 for pass, fail, logs and
 skipped languages; `cppcheck` is not used, and the .NET SDK is installed at an
 exact version of 10 or later.
 The rules that follow from it:
 - **C++ (and C):** `clang-format --dry-run -Werror` and `clang-tidy` on the
  tracked `*.c`, `*.cc`, `*.cpp`, `*.cxx`, `*.h`, `*.hh`, `*.hpp` files under
  `working-directory`, both from PyPI at the exact versions of the inputs
  `clang-format-version` (default `23.1.3`) and `clang-tidy-version` (default
  `22.1.8`). Inputs: `working-directory` (default `.`), `std` (default
  `c++20`), `compile-commands-dir` (default empty: the flags `-std=<std>` are
  used; set it to the directory of a `compile_commands.json` the caller built
  before the call), `tools-ref`. A `.clang-format` and a `.clang-tidy` of the
  project configure the tools; a missing `.clang-format` is a
  `[configuration]` failure.
 - **C#:** `dotnet format --verify-no-changes` and `dotnet build
  -warnaserror` with the analyzers the project enables in `.editorconfig`,
  on the solution or project found under `working-directory`. Inputs:
  `working-directory` (default `.`), `project` (default empty: the single
  `*.sln`, `*.slnx` or `*.csproj` found; none or several is a
  `[configuration]` failure that names them), `dotnet-sdk-version` (default
  an exact `10.0.x`, installed with `dotnet-install.sh --version`),
  `tools-ref`.
 - **No `cppcheck`:** `clang-tidy` does the static analysis with a current
  release; a future version of the contract may add a static analyzer when a
  current release is a package.
 - **Exact pins:** every tool input is an exact version, never a channel or a
  range; raising a default is a breaking change under ADR-0006.
 - **Names:** the wiki pages are `QualityChecksCpp` and `QualityChecksCSharp`
  with the usual `.da` and `.ms` translations; the guides are
  `guides/quality-checks-cpp.md` and `guides/quality-checks-csharp.md`.
 - **C is included with C++:** the same tools check both and the files are
  told apart by extension; `QC-CL-001` and `QC-CPP-001` stay the review
  checklists of the code itself.
 ## Consequences
 **Positive:**
 - Each workflow has inputs that fit its language, and a consumer of one never
  sees the inputs of the other.
 - Only current tools run; a run is reproducible because every version is exact.
 - The scripts are files that are linted and tested with stub tools, as for
  `quality-checks.yml`.
 **Negative:**
 - Two workflows, two guides and two wiki pages to keep; a repository with both
  languages calls both.
 - Without `cppcheck` the C++ checks are `clang-tidy` and the compiler only; a
  defect class that `cppcheck` finds may go unchecked.
 - A C# check needs the network for the package restore, and a C++ check needs
  the caller to build a compile database for precise results; both are the
  caller's responsibility and are said in the guides.
 - Raising the exact default of a tool, including the SDK, is a breaking
  change and costs a major version (ADR-0006).
 - A caller pinned to an exact tag is pinned completely only when `tools-ref`
  names the same tag (as for `quality-checks.yml`).
 - Security: each run downloads and executes code from outside the repository
  (wheels from PyPI and the `dotnet-install.sh` script from `dot.net`, and for
  C# the NuGet packages of the project). Exact versions limit what can change
  but are not verified against a hash, so a compromised package index or
  download host would reach the run. The jobs get `contents: read` and no
  secret, which limits what such code can do.
 ## Affected Artifacts
 - [MIL-007] — decides its criterion 2 and unlocks tasks 4 and 5.
 - [UC-005] — the use case these workflows serve.
 - [US-001] — US-001.16 and US-001.17 state their acceptance criteria.
 - [ADR-0005] — the contract that this decision extends, unchanged.
 - [ADR-0006] — raising a default tool version is breaking.
 ---
 [MIL-007]: ../milestones/mil-007-cpp-csharp-quality-checks.md
 [UC-005]: ../uc-005/uc.md
 [US-001]: ../user-stories.md
 [ADR-0005]: ./adr-0005-quality-check-contract.md
 [ADR-0006]: ./adr-0006-release-process-and-version-pinning.md
 [11cba35]: https://git.tirsystem.com/TirSystem/github-action/commit/11cba358b83cb7b6624f6b0956ae7b0c112d3692
 [9e7aedd]: https://git.tirsystem.com/TirSystem/github-action/commit/9e7aeddb11c2b41ac893d9f7893d663a53fbe470
@@ -11,9 +11,9 @@ each document lives in *this* project and the next version to use.
 | SA | Stakeholder Analysis | docs/stakeholder-analysis.md | 002 |
 | PP | Project Plan | docs/project-plan.md | 002 |
 | MIL | Milestone / Gateway | docs/milestones/*.md | 008 |
-| RC | SQA Review Record | docs/sqa/reviews/rc-*.md | 058 |
+| RC | SQA Review Record | docs/sqa/reviews/rc-*.md | 054 |
 | TM | Traceability Matrix | docs/sqa/traceability-matrix.md | 002 |
-| ADR | Architecture Decision Record | docs/adr/adr-NNNN-*.md | 0009 |
+| ADR | Architecture Decision Record | docs/adr/adr-NNNN-*.md | 0008 |
 | UCD | Use Case Diagram | docs/use-case-diagram.md | 002 |
 | US | User Story | docs/user-stories.md | 002 |
 | UC | Use Case | docs/uc-NNN/uc.md | 008 |
@@ -4,13 +4,13 @@
 | Key | Value |
 | --- | --- |
 | ID | MIL-007 |
-| CrossReference | [BC-001], [US-001], [UC-005], [MIL-003], [MIL-004], [ADR-0005], [ADR-0006], [ADR-0008] |
+| CrossReference | [BC-001], [US-001], [UC-005], [MIL-003], [MIL-004], [ADR-0005], [ADR-0006] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
-| 2026-10-11 | Deprecated | Jens Tirsvad Nielsen | S01 | Current tool versions only, .NET SDK 10 or later: results of run 699 replace the SDK 8 result; tasks 3 and criterion 1 amended | [7bcc67a] |
+| 2026-10-11 | Deprecated | Jens Tirsvad Nielsen | S01 | Added the verification results of task 2 (runner tools) | [32b5ab6] |
-| 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | Amendment reviewed (RC-055) and accepted: current tool versions, .NET SDK 10 or later, results of run 699, the contract of ADR-0008 in task 3 | [faf13b2] |
+| 2026-10-11 | Proposed | Jens Tirsvad Nielsen | S01 | Current tool versions only, .NET SDK 10 or later: results of run 699 replace the SDK 8 result; tasks 3 and criterion 1 amended | [7bcc67a] |
 ---
@@ -71,11 +71,11 @@ is only available as an old version is not used.
 | # | Task | Summary | Needs its own Use Case/User Story? | Reference |
 | --- | --- | --- | --- | --- |
-| 1 | Write the use case and stories for C++ and C# checks | Extend UC-005 (Run Project Quality Checks) so that its Brief names C++ and C#, and add stories to US-001 for a C++ project and a C# project, each with a pass and a fail acceptance criterion. Review them with the checklists of the `artifact` skill. | Yes | UC-005, US-001.09, US-001.10, US-001.16, US-001.17 |
+| 1 | Write the use case and stories for C++ and C# checks | Extend UC-005 (Run Project Quality Checks) so that its Brief names C++ and C#, and add stories to US-001 for a C++ project and a C# project, each with a pass and a fail acceptance criterion. Review them with the checklists of the `artifact` skill. | Yes | UC-005, US-001.09, US-001.10 |
 | 2 | Verify what the runner provides | On a throwaway branch, run a job on `ubuntu-latest` that prints which of `clang-format`, `clang-tidy`, `cppcheck` and the .NET SDK (`dotnet --version`) exist, and whether each can be installed in the run (for example from PyPI, apt or the dotnet install script) and how long that takes. Record the result in the milestone like MIL-003 task 1. | No | |
-| 3 | Decide the contract | Decided in ADR-0008 (accepted on 2026-10-11, RC-054): two separate reusable workflows, `quality-checks-cpp.yml` for C and C++ and `quality-checks-csharp.yml`, each running a script file fetched at `tools-ref`; C++: `clang-format --dry-run -Werror` and `clang-tidy` at exact current versions, no `cppcheck`; C#: `dotnet format --verify-no-changes` and a build with analyzers and warnings as errors, with the .NET SDK installed at an exact `10.0.x`; the inputs, the names of the workflows, guides and wiki pages and the consequences are in the ADR. | No | ADR-0008 |
+| 3 | Decide the contract | Record an ADR that decides: one workflow for both languages or one per language; the tools and pinned versions, current releases only and .NET SDK 10 or later (C++: `clang-format --dry-run -Werror`, `clang-tidy` and compiler warnings; `cppcheck` only if a current release can be had; C#: `dotnet format --verify-no-changes`, a build with analyzers and warnings as errors); the inputs (languages or paths, working directory, build command or compile database); what a build-dependent check needs from the caller; whether C is included with C++; and the names of the workflows and wiki pages (they follow `QualityChecksPythonShell`). Must be accepted before tasks 4 and 5. | No | ADR-0005 (refined) |
-| 4 | Implement the C++ workflow | Add the reusable workflow `quality-checks-cpp.yml` and its script file `tools/quality-checks-cpp.sh` as ADR-0008 decides, exact tool versions, least-privilege permissions and offline tests with stub tools, as `quality-checks.yml` does. | No | |
+| 4 | Implement the C++ workflow | Add the reusable workflow and its script file `tools/quality-checks-cpp.sh` (or as the ADR decides), pinned tool versions, least-privilege permissions and offline tests with stub tools, as `quality-checks.yml` does. | No | |
-| 5 | Implement the C# workflow | The same for C#: `quality-checks-csharp.yml`, `tools/quality-checks-csharp.sh` and tests, as ADR-0008 decides. | No | |
+| 5 | Implement the C# workflow | The same for C#, with its script file and tests. | No | |
 | 6 | Write the guides and the wiki pages | One guide per workflow in `guides/` for reading its results, the wiki pages in English, Danish and Bahasa Malaysia, the Home workflow list and diagrams (a test requires every workflow to be listed), and an update of the upgrade guide. | No | |
 | 7 | Adopt each workflow in one other repository | Onboard a real C++ project and a real C# project, or a throwaway repository when none exists, and fix the gaps in the guides that appear. Verify a seeded failure. | No | |
 | 8 | Release | Add the changelog entry (a new workflow is a minor change, ADR-0006) and run the Release workflow; record the results in this milestone and review it. | No | |
@@ -102,9 +102,9 @@ is a .NET SDK of version 10 or later, and old tools are not run. A second run
 clang tools come from PyPI in a few seconds with an exact version, as
 `quality-checks.yml` already does for its tools, and the .NET SDK 10 comes from
 the official script in 20 s, with no change to the runner. `cppcheck` is the
-exception: only an old version is a package. ADR-0008 drops it, because
+exception: only an old version is a package, so the contract either drops it
-`clang-tidy` does the static analysis and a current `cppcheck` would have to
+(`clang-tidy` does the static analysis) or builds a current release from
-be built from source, which costs minutes per run.
+source, which costs minutes per run.
 Not covered by this task: running a tool against a real C++ project (a
 `clang-tidy` run needs a compile database or flags) or a real C# solution
 (`dotnet format` and a build need the project's restore of packages from the
@@ -121,6 +121,5 @@ network), a private runner with no internet, and an image that differs from
 [MIL-004]: ./mil-004-versioned-release.md
 [ADR-0005]: ../adr/adr-0005-quality-check-contract.md
 [ADR-0006]: ../adr/adr-0006-release-process-and-version-pinning.md
-[ADR-0008]: ../adr/adr-0008-cpp-csharp-quality-check-contract.md
+[32b5ab6]: https://git.tirsystem.com/TirSystem/github-action/commit/32b5ab62ab5a82638b71b8fcfb43a819e92ab346
 [7bcc67a]: https://git.tirsystem.com/TirSystem/github-action/commit/7bcc67a065ac5f67b4e13ebf243a4bbbe2af47d9
 [faf13b2]: https://git.tirsystem.com/TirSystem/github-action/commit/faf13b2c2a4901c0171977de1ffc2841023f537a
@@ -1,52 +0,0 @@
 # Review Record: ADR-0008
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | RC-054 |
 | CrossReference | [ADR-0008], [QC-ADR-001] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | Initial version | [9e7aedd] |
 ---
 ## Artifact Under Review
 - Instance reviewed: [ADR-0008]
 - Checklist used: [QC-ADR-001]
 ## Checklist Results
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | The ID (`ADR-NNNN`, 4-digit) matches the filename number and is unique and sequential | Pass | ADR-0008 in `adr-0008-cpp-csharp-quality-check-contract.md`, after ADR-0007. |
 | 2 | Context states the problem, the forces (cost, risk, constraints) and the options evaluated | Pass | States the two requirements from S01, the facts from runs 692 and 699, and the options. |
 | 3 | At least two options were considered, or the absence of alternatives is justified | Pass | Three options for the workflows, three for `cppcheck`, two for the SDK pin. |
 | 4 | Decision is stated in one or two unhedged sentences and matches one of the evaluated options | Pass | One sentence naming option 2, dropping `cppcheck` (c) and an exact SDK version (b). |
 | 5 | Consequences list both Positive and Negative outcomes | Pass | Three positive and six negative (after the fix of criterion 6). |
 | 6 | Quality-attribute impacts (performance, security, portability, etc.) are named where the decision affects them | Pass | Finding fixed during this review: the security impact of downloading and running tools and packages in every run was not named (ADR-0005 names it for PyPI); it is now a negative consequence, with the limit that the jobs have `contents: read` and no secret. |
 | 7 | Affected Artifacts are listed as links, and each is also in CrossReference | Pass | MIL-007, UC-005, US-001, ADR-0005 and ADR-0006 are linked and cited. |
 | 8 | Status changes are recorded as new Version History rows with a Change summary and Commit link; retained rows are never rewritten | Pass | The Proposed row keeps its status as Deprecated and the Accepted row is added. |
 | 9 | A superseded or deprecated ADR names its successor, and the successor links back | N-A | Nothing is superseded; ADR-0005 is extended and unchanged. |
 | 10 | Written in business or technical language of the domain, with no unexplained abbreviations | Pass | Finding fixed during this review: PyPI and SDK were used without being expanded; both are introduced at first use. |
 | 11 | Status is one of `Proposed`, `Accepted`, `Rejected`, `Deprecated` or `Superseded by ADR-NNNN`, and every Version History row uses only these | Pass | Deprecated and Accepted. |
 ## Overall Verdict
 Go - all applicable criteria pass; the two findings (criteria 6 and 10) were fixed during the review. It unlocks tasks 4 and 5 of MIL-007 (#98 and #99) under the plan-first gate, once MIL-007 itself is Accepted again (its amendment after RC-052 is still Proposed). S01 gave the Go in chat on 2026-10-11, standing in for the other reviewers as ADR-0002 records; there is no independent reader.
 ## Action Items
 | Action | Owner | Due |
 | --- | --- | --- |
 | Review and accept the amendment of MIL-007 (current tool versions, .NET SDK 10 or later, results of run 699) so that its latest row is Accepted | S01 | before #98 and #99 |
 | Choose the exact default of `dotnet-sdk-version` (an `10.0.x` band) when the C# workflow is built, and check it is still the current stable release | S05 | task 5 |
 ---
 [ADR-0008]: ../../adr/adr-0008-cpp-csharp-quality-check-contract.md
 [QC-ADR-001]: ../../../framework/qc/qc-adr.md
 [9e7aedd]: https://git.tirsystem.com/TirSystem/github-action/commit/9e7aeddb11c2b41ac893d9f7893d663a53fbe470
@@ -1,46 +0,0 @@
 # Review Record: MIL-007 (amendment)
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | RC-055 |
 | CrossReference | [MIL-007], [QC-MIL-001] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | Initial version | [faf13b2] |
 ---
 ## Artifact Under Review
 - Instance reviewed: [MIL-007] after the amendments since RC-052: current tool versions only (.NET SDK 10 or later), the results of runs 692 and 699, and the contract of ADR-0008
 - Checklist used: [QC-MIL-001]
 ## Checklist Results
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | A concrete deliverable is defined for every gate | Pass | Unchanged, and the deliverable now states the version requirement: current tools only, .NET SDK 10 or later. |
 | 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Finding fixed during this review: criterion 1 was amended but task 3 still carried the options of the draft (`cppcheck` conditional, one workflow or two). Task 3 now states the decided contract and points to ADR-0008, so criterion 2 is checkable as it stands: the ADR is accepted. |
 | 3 | Dependencies on other milestones are explicitly mapped | Pass | Unchanged: MIL-003 and MIL-004, both closed. |
 | 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | O4, US-001.09 and .10, and now the stories US-001.16 and .17 of task 1; ADR-0008 is in CrossReference. |
 | 5 | Milestone owner and approving reviewer are identified | Pass | Owner S05, approving reviewer S01. |
 | 6 | Milestone has a defined target date consistent with project constraints | Pass | 2027-01-16, unchanged and confirmed on 2026-10-11. |
 ## Overall Verdict
 Go - all six criteria pass; the one finding (criterion 2) was fixed during the review, together with two stale phrases (the verification results still offered a build of `cppcheck`, and tasks 4 and 5 said "as the ADR decides"). It restores the status Accepted of MIL-007, which the publishing action and the plan-first gate require, and it does not accept UC-005 and US-001.16 and .17 (task 1, #95), which still need their own review. S01 gave the Go in chat on 2026-10-11, standing in for the other reviewers as ADR-0002 records; there is no independent reader.
 ## Action Items
 | Action | Owner | Due |
 | --- | --- | --- |
 | Review and accept the extension of UC-005 and the stories US-001.16 and US-001.17 (#95) | S01 | before #98 and #99 |
 ---
 [MIL-007]: ../../milestones/mil-007-cpp-csharp-quality-checks.md
 [QC-MIL-001]: ../../../framework/qc/qc-milestones-gateways.md
 [faf13b2]: https://git.tirsystem.com/TirSystem/github-action/commit/faf13b2c2a4901c0171977de1ffc2841023f537a
@@ -1,52 +0,0 @@
 # Review Record: UC-005 (C++ and C#)
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | RC-056 |
 | CrossReference | [UC-005], [QC-UC-001] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | Initial version | [1bc56f8] |
 ---
 ## Artifact Under Review
 - Instance reviewed: [UC-005] after the extension of its Brief to C++ and C# (MIL-007 task 1)
 - Checklist used: [QC-UC-001] (Brief format)
 ## Checklist Results
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | Consists of a single, concise paragraph summarizing only the primary success scenario | Pass | Finding fixed during this review: the extension had added a sentence about a language that needs a build or a project file and says what is missing, which is a failure flow. It is removed from the Brief; the stories US-001.16 and .17 carry it as an acceptance criterion. |
 | 2 | Written as an informal multi-paragraph narrative; may mention some alternate flows without formal structure | N-A | Format is Brief. |
 | 3 | All standard sections are present: actors, preconditions, postconditions, main success scenario, alternative/exception flows | N-A | Format is Brief; actor, stakeholders, pre- and postconditions and the paragraph are present. |
 | 4 | Preconditions and postconditions are explicitly defined | Pass | The precondition now lists the four languages (Python, shell, C++, C#); the postcondition is unchanged. |
 | 5 | Primary actor is explicitly stated | Pass | Software Engineer. |
 | 6 | Stakeholders and their interests are stated | Pass | S02 and S05, unchanged. |
 | 7 | Main success scenario is written as clear, numbered steps | N-A | Format is Brief. |
 | 8 | Alternative/exception flows correctly reference `<<include>>`/`<<extend>>` use cases where relevant, per UML 2.5.1 | N-A | None in a Brief. |
 | 9 | Explicit business rules are captured per step where applicable, rather than embedded loosely in narrative text | N-A | No steps in a Brief. |
 | 10 | Naming of actors and use case title is consistent with the corresponding Use Case Diagram and User Stories | Pass | Title and actor equal UCD-001; the Stories line lists US-001.09, .10, .16 and .17, which exist. |
 | 11 | Scope/level (e.g. summary, user-goal, subfunction) is explicitly stated | Pass | Scope and user-goal level, unchanged. |
 | 12 | Use case is written from the actor's goal perspective, free of UI or implementation detail | Pass | Goal wording; the tool names are not in the Brief for C++ and C#. |
 ## Overall Verdict
 Go - all applicable criteria pass; the one finding (criterion 1) was fixed during the review. S01 gave the Go in chat on 2026-10-11, standing in for the other reviewers as ADR-0002 records; there is no independent reader.
 ## Action Items
 | Action | Owner | Due |
 | --- | --- | --- |
 | Update the description of this use case in the Use Case Diagram table of UCD-001 ("Lint, format and type checks run on every change ...") to cover C++ and C# at its next review | S01 | next review of UCD-001 |
 ---
 [UC-005]: ../../uc-005/uc.md
 [QC-UC-001]: ../../../framework/qc/qc-use-case.md
 [1bc56f8]: https://git.tirsystem.com/TirSystem/github-action/commit/1bc56f8b771531f221f218fc00b147ecc73c051e
@@ -1,47 +0,0 @@
 # Review Record: US-001 (US-001.16 and US-001.17)
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | RC-057 |
 | CrossReference | [US-001], [QC-US-001] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | Initial version | [1bc56f8] |
 ---
 ## Artifact Under Review
 - Instance reviewed: [US-001], the new stories US-001.16 (a C++ project gets the same checks) and US-001.17 (a C# project gets the same checks) and the document's Purpose and Scope
 - Checklist used: [QC-US-001]
 ## Checklist Results
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | Follows INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) | Pass | The two stories are independent of each other and of US-001.09 and .10, each states one goal, and the INVEST check names all seventeen stories. |
 | 2 | Written in "As a / I want / So that" form | Pass | Both. |
 | 3 | Clear, testable acceptance criteria are included | Pass | Three Given/When/Then criteria each: a pass or fail status, a finding with tool and `path:line`, and a `[configuration]` failure that names what is missing instead of passing; each is checked with a run. |
 | 4 | Traceable to a use case or epic | Pass | [UC-005] and [MIL-007], and the Stories line of UC-005 lists both. |
 | 5 | Story is sized to fit within a single iteration | Pass | One language each. |
 | 6 | Story statement avoids technical implementation detail | Pass | No tool is named in the statements. The acceptance criteria name the category `[configuration]`, as US-001.07 does. |
 | 7 | Role named in the story matches an actor defined in the Use Case Diagram | Pass | Software Engineer. |
 ## Overall Verdict
 Go - all seven criteria pass. One stale sentence in the Purpose and Scope (it said that stories for quality checks and releases were not written yet) was corrected during the review, as it is false since US-001.09. With RC-056 this completes task 1 of MIL-007 (#95) and, with ADR-0008 and the accepted amendment of MIL-007, meets the plan-first gate for tasks 4 and 5 (#98 and #99). S01 gave the Go in chat on 2026-10-11, standing in for the other reviewers as ADR-0002 records; there is no independent reader.
 ## Action Items
 | Action | Owner | Due |
 | --- | --- | --- |
 | None | - | - |
 ---
 [US-001]: ../../user-stories.md
 [QC-US-001]: ../../../framework/qc/qc-user-story.md
 [1bc56f8]: https://git.tirsystem.com/TirSystem/github-action/commit/1bc56f8b771531f221f218fc00b147ecc73c051e
@@ -4,13 +4,13 @@
 | Key | Value |
 | --- | --- |
 | ID | TM-001 |
-| CrossReference | [BC-001], [SA-001], [PP-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004], [MIL-005], [MIL-006], [MIL-007], [RC-001], [RC-002], [RC-003], [RC-004], [RC-005], [RC-006], [RC-007], [RC-008], [RC-009], [RC-010], [RC-011], [RC-012], [RC-013], [RC-014], [RC-015], [RC-016], [RC-017], [RC-018], [RC-019], [RC-020], [RC-021], [RC-022], [RC-023], [RC-024], [RC-025], [RC-026], [RC-027], [RC-028], [RC-029], [RC-030], [RC-031], [RC-032], [RC-033], [RC-034], [RC-035], [RC-036], [RC-037], [RC-038], [RC-039], [RC-040], [RC-041], [RC-042], [RC-043], [RC-044], [RC-045], [RC-046], [RC-047], [RC-048], [RC-049], [RC-050], [RC-051], [RC-052], [RC-053], [RC-054], [RC-055], [RC-056], [RC-057], [ADR-0007], [ADR-0008], [UC-007], [UC-006], [ADR-0006], [UC-005], [ADR-0005], [UCD-001], [US-001], [UC-001], [UC-002], [UC-003], [UC-004], [ADR-0001], [ADR-0002], [ADR-0003], [ADR-0004] |
+| CrossReference | [BC-001], [SA-001], [PP-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004], [MIL-005], [MIL-006], [MIL-007], [RC-001], [RC-002], [RC-003], [RC-004], [RC-005], [RC-006], [RC-007], [RC-008], [RC-009], [RC-010], [RC-011], [RC-012], [RC-013], [RC-014], [RC-015], [RC-016], [RC-017], [RC-018], [RC-019], [RC-020], [RC-021], [RC-022], [RC-023], [RC-024], [RC-025], [RC-026], [RC-027], [RC-028], [RC-029], [RC-030], [RC-031], [RC-032], [RC-033], [RC-034], [RC-035], [RC-036], [RC-037], [RC-038], [RC-039], [RC-040], [RC-041], [RC-042], [RC-043], [RC-044], [RC-045], [RC-046], [RC-047], [RC-048], [RC-049], [RC-050], [RC-051], [RC-052], [RC-053], [ADR-0007], [UC-007], [UC-006], [ADR-0006], [UC-005], [ADR-0005], [UCD-001], [US-001], [UC-001], [UC-002], [UC-003], [UC-004], [ADR-0001], [ADR-0002], [ADR-0003], [ADR-0004] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
-| 2026-10-11 | Deprecated | Jens Tirsvad Nielsen | S01 | Added RC-055 (MIL-007 amendment) | [faf13b2] |
+| 2026-10-11 | Deprecated | Jens Tirsvad Nielsen | S01 | Added RC-051 (ADR-0005 tools-ref) | [670f0ac] |
-| 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | Added RC-056 and RC-057 (UC-005 and US-001 for C++ and C#) | [1bc56f8] |
+| 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | Added MIL-007, RC-052 and RC-053 | [e3ad1fa] |
 ---
@@ -39,7 +39,7 @@ updated whenever an artifact instance is created or reviewed.
 | [RC-006] | RC | [MIL-003] | - | - |
 | [MIL-005] | MIL | [BC-001], [PP-001], [MIL-002] | [MIL-006] | [RC-010], [RC-011], [RC-030], [RC-050] |
 | [MIL-006] | MIL | [BC-001], [PP-001], [MIL-002], [MIL-005] | - | [RC-016], [RC-031], [RC-049] |
-| [MIL-007] | MIL | [BC-001], [PP-001], [MIL-003], [MIL-004], [ADR-0008] | - | [RC-052], [RC-055] |
+| [MIL-007] | MIL | [BC-001], [PP-001], [MIL-003], [MIL-004] | - | [RC-052] |
 | [RC-007] | RC | [MIL-004] | - | - |
 | [RC-008] | RC | [BC-001] | - | - |
 | [RC-009] | RC | [PP-001] | - | - |
@@ -57,17 +57,16 @@ updated whenever an artifact instance is created or reviewed.
 | [RC-017] | RC | [PP-001] | - | - |
 | [RC-018] | RC | [ADR-0004] | - | - |
 | [UCD-001] | UCD | [SA-001], [BC-001] | [US-001], [UC-001], [UC-002], [UC-003], [UC-004], [UC-005], [UC-006], [UC-007] | [RC-019], [RC-035], [RC-040], [RC-045] |
-| [US-001] | US | [UCD-001], [BC-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004], [MIL-007] | [UC-001], [UC-002], [UC-003], [UC-004], [UC-005], [UC-006], [UC-007] | [RC-020], [RC-036], [RC-041], [RC-046], [RC-057] |
+| [US-001] | US | [UCD-001], [BC-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004] | [UC-001], [UC-002], [UC-003], [UC-004], [UC-005], [UC-006], [UC-007] | [RC-020], [RC-036], [RC-041], [RC-046] |
 | [UC-001] | UC | [UCD-001], [US-001], [SA-001] | - | [RC-021] |
 | [UC-002] | UC | [UCD-001], [US-001], [SA-001] | - | [RC-022] |
 | [UC-003] | UC | [UCD-001], [US-001], [SA-001] | - | [RC-023] |
 | [UC-004] | UC | [UCD-001], [US-001], [SA-001] | - | [RC-024] |
-| [UC-005] | UC | [UCD-001], [US-001], [SA-001] | [ADR-0005] | [RC-037], [RC-056] |
+| [UC-005] | UC | [UCD-001], [US-001], [SA-001] | [ADR-0005] | [RC-037] |
 | [ADR-0005] | ADR | [MIL-003], [UC-005], [US-001], [ADR-0004] | - | [RC-038], [RC-051] |
 | [UC-006] | UC | [UCD-001], [US-001], [SA-001] | [ADR-0006] | [RC-042] |
 | [ADR-0006] | ADR | [MIL-004], [UC-006], [US-001], [ADR-0004], [ADR-0005] | - | [RC-043] |
 | [ADR-0007] | ADR | [MIL-004], [UC-006], [ADR-0006] | - | [RC-047] |
 | [ADR-0008] | ADR | [MIL-007], [UC-005], [US-001], [ADR-0005], [ADR-0006] | - | [RC-054] |
 | [UC-007] | UC | [UCD-001], [US-001], [SA-001] | - | [RC-044] |
 | [RC-019] | RC | [UCD-001] | - | - |
 | [RC-020] | RC | [US-001] | - | - |
@@ -104,10 +103,6 @@ updated whenever an artifact instance is created or reviewed.
 | [RC-051] | RC | [ADR-0005] | - | - |
 | [RC-052] | RC | [MIL-007] | - | - |
 | [RC-053] | RC | [PP-001] | - | - |
 | [RC-054] | RC | [ADR-0008] | - | - |
 | [RC-055] | RC | [MIL-007] | - | - |
 | [RC-056] | RC | [UC-005] | - | - |
 | [RC-057] | RC | [US-001] | - | - |
 ## Coverage Notes
@@ -191,16 +186,11 @@ updated whenever an artifact instance is created or reviewed.
 [RC-051]: ./reviews/rc-051-adr-0005-tools-ref.md
 [RC-052]: ./reviews/rc-052-mil-007.md
 [RC-053]: ./reviews/rc-053-pp-001-mil-007.md
 [RC-054]: ./reviews/rc-054-adr-0008.md
 [RC-055]: ./reviews/rc-055-mil-007-amendment.md
 [RC-056]: ./reviews/rc-056-uc-005-cpp-csharp.md
 [RC-057]: ./reviews/rc-057-us-001-cpp-csharp.md
 [ADR-0008]: ../adr/adr-0008-cpp-csharp-quality-check-contract.md
 [ADR-0007]: ../adr/adr-0007-release-publish-destination.md
 [UC-007]: ../uc-007/uc.md
 [UC-006]: ../uc-006/uc.md
 [ADR-0006]: ../adr/adr-0006-release-process-and-version-pinning.md
 [UC-005]: ../uc-005/uc.md
 [ADR-0005]: ../adr/adr-0005-quality-check-contract.md
-[faf13b2]: https://git.tirsystem.com/TirSystem/github-action/commit/faf13b2c2a4901c0171977de1ffc2841023f537a
+[670f0ac]: https://git.tirsystem.com/TirSystem/github-action/commit/670f0ac469043bb166c84290c0dbf62b4908e3cc
-[1bc56f8]: https://git.tirsystem.com/TirSystem/github-action/commit/1bc56f8b771531f221f218fc00b147ecc73c051e
+[e3ad1fa]: https://git.tirsystem.com/TirSystem/github-action/commit/e3ad1fa7e7eef57a6793a479edb41ac6fd2db688
@@ -9,8 +9,8 @@
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
-| 2026-10-11 | Deprecated | Jens Tirsvad Nielsen | S01 | Brief extended to C++ and C# (MIL-007 task 1) | [32b5ab6] |
+| 2026-10-10 | Deprecated | Jens Tirsvad Nielsen | S01 | Initial version | [385d2fb] |
-| 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | Brief extended to C++ and C# reviewed (RC-056) and accepted; the failure sentence is left to the stories | [1bc56f8] |
+| 2026-10-11 | Proposed | Jens Tirsvad Nielsen | S01 | Brief extended to C++ and C# (MIL-007 task 1) | [32b5ab6] |
 ---
@@ -25,7 +25,7 @@
 ## Brief
-A Software Engineer opens a pull request in a repository that calls the shared quality-check workflow. The workflow installs the pinned tools, runs the checks for each selected language on the files of the repository (lint, format and types for Python; lint and format for shell; format and static checks for C++; format and analyzer checks for C#), and reports one status for the pull request. When every selected tool passes, the status is green.
+A Software Engineer opens a pull request in a repository that calls the shared quality-check workflow. The workflow installs the pinned tools, runs the checks for each selected language on the files of the repository (lint, format and types for Python; lint and format for shell; format and static checks for C++; format and analyzer checks for C#), and reports one status for the pull request. A language that needs a build or a project file says what is missing instead of passing. When every selected tool passes, the status is green.
 **Stakeholder interests**
@@ -43,5 +43,5 @@ A Software Engineer opens a pull request in a repository that calls the shared q
 [SA-001]: ../stakeholder-analysis.md
 [ADR-0005]: ../adr/adr-0005-quality-check-contract.md
 [MIL-007]: ../milestones/mil-007-cpp-csharp-quality-checks.md
 [385d2fb]: https://git.tirsystem.com/TirSystem/github-action/commit/385d2fb7cb9be1fdc8fd3503d0af624fa38eafc7
 [32b5ab6]: https://git.tirsystem.com/TirSystem/github-action/commit/32b5ab62ab5a82638b71b8fcfb43a819e92ab346
 [1bc56f8]: https://git.tirsystem.com/TirSystem/github-action/commit/1bc56f8b771531f221f218fc00b147ecc73c051e
@@ -9,8 +9,8 @@
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
-| 2026-10-11 | Deprecated | Jens Tirsvad Nielsen | S01 | Added US-001.16 and US-001.17 (C++ and C# checks, MIL-007 task 1) | [32b5ab6] |
+| 2026-10-10 | Deprecated | Jens Tirsvad Nielsen | S01 | Added US-001.14 and US-001.15 (UC-007); US-001.13 traced to UC-007 (RC-046) | [4cf52af] |
-| 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | US-001.16 and US-001.17 reviewed (RC-057) and accepted; the Purpose and Scope names the later stories | [1bc56f8] |
+| 2026-10-11 | Proposed | Jens Tirsvad Nielsen | S01 | Added US-001.16 and US-001.17 (C++ and C# checks, MIL-007 task 1) | [32b5ab6] |
 ---
@@ -19,9 +19,7 @@
 These stories cover the P1 use cases of the Project Plan that MIL-002 delivers
 (O1 to O3 of [BC-001]): keeping the mirror metadata correct, configuring
 credentials, onboarding a repository and diagnosing a failed run. Roles are the
-actors of [UCD-001]. Later stories cover quality checks (US-001.09, US-001.10 and, for
+actors of [UCD-001]. Stories for quality checks and releases (MIL-004) and for the wiki (MIL-005, MIL-006) are not written yet.
 C++ and C#, US-001.16 and US-001.17), releases and updates (US-001.11 to
 US-001.15). Stories for the wiki (MIL-005, MIL-006) are not written yet.
 ## Story List
@@ -274,5 +272,5 @@ behaviour is tested rather than built.
 [UC-005]: ./uc-005/uc.md
 [UC-006]: ./uc-006/uc.md
 [UC-007]: ./uc-007/uc.md
 [4cf52af]: https://git.tirsystem.com/TirSystem/github-action/commit/4cf52afe00f546c6b20424fb8dfc12796ffd9296
 [32b5ab6]: https://git.tirsystem.com/TirSystem/github-action/commit/32b5ab62ab5a82638b71b8fcfb43a819e92ab346
 [1bc56f8]: https://git.tirsystem.com/TirSystem/github-action/commit/1bc56f8b771531f221f218fc00b147ecc73c051e
@@ -1,634 +0,0 @@
 """Offline tests for the reusable C++ and C# quality-check workflows (ADR-0008).
 The shell steps run with stub tools in a throwaway git repository, so no
 network, no clang and no .NET SDK are needed.
 """
 import os
 import shutil
 import subprocess
 from pathlib import Path
 from typing import Any
 import pytest
 import yaml
 from workflow_source import REPO_ROOT
 CPP_WORKFLOW = REPO_ROOT / ".gitea" / "workflows" / "quality-checks-cpp.yml"
 CSHARP_WORKFLOW = REPO_ROOT / ".gitea" / "workflows" / "quality-checks-csharp.yml"
 CPP_SCRIPT = REPO_ROOT / "tools" / "quality-checks-cpp.sh"
 CSHARP_SCRIPT = REPO_ROOT / "tools" / "quality-checks-csharp.sh"
 BASH = shutil.which("bash")
 pytestmark = pytest.mark.skipif(BASH is None, reason="bash is needed to run the workflow steps")
 # A script run: the finished process and the tool calls the stubs logged.
 Run = tuple[subprocess.CompletedProcess[str], list[str]]
 def load(path: Path) -> dict[str, Any]:  # parsed YAML has no fixed shape
    return yaml.safe_load(path.read_text(encoding="utf-8"))
 def inputs_of(path: Path) -> dict[str, Any]:
    return load(path)[True]["workflow_call"]["inputs"]  # PyYAML reads `on` as True
@pytest.mark.parametrize(
    "workflow, script, job",
    [
        (CPP_WORKFLOW, "quality-checks-cpp.sh", "quality-checks-cpp"),
        (CSHARP_WORKFLOW, "quality-checks-csharp.sh", "quality-checks-csharp"),
    ],
    ids=["cpp", "csharp"],
 )
 class TestDefinition:
    def test_has_least_privilege_and_needs_no_secret(self, workflow: Path, script: str, job: str) -> None:
        document = load(workflow)
        assert document["jobs"][job]["permissions"] == {"contents": "read"}
        assert "secrets" not in workflow.read_text(encoding="utf-8").replace("needs no secret", "")
    def test_embeds_no_script_and_runs_the_file_in_three_steps(
        self,
        workflow: Path,
        script: str,
        job: str,
    ) -> None:
        steps = load(workflow)["jobs"][job]["steps"]
        commands = [step["run"] for step in steps if "run" in step]
        assert commands == [f"bash shared-scripts/tools/{script} {c}" for c in ("validate", "install", "run")]
    def test_fetches_the_script_at_the_tools_ref_input(self, workflow: Path, script: str, job: str) -> None:
        steps = load(workflow)["jobs"][job]["steps"]
        fetch = next(step for step in steps if step.get("name") == "Fetch the shared script")
        assert fetch["with"] == {
            "repository": "TirSystem/github-action",
            "ref": "${{ inputs.tools-ref }}",
            "path": "shared-scripts",
        }
        assert inputs_of(workflow)["tools-ref"]["default"] == "v1"
    def test_inputs_reach_the_script_only_through_the_environment(
        self,
        workflow: Path,
        script: str,
        job: str,
    ) -> None:
        for step in load(workflow)["jobs"][job]["steps"]:
            assert "${{" not in step.get("run", "")
    def test_script_is_a_file_that_parses(self, workflow: Path, script: str, job: str) -> None:
        result = subprocess.run(
            [BASH, "-n", str(REPO_ROOT / "tools" / script)], text=True, capture_output=True
        )
        assert result.returncode == 0, result.stderr
    def test_unknown_command_is_refused(self, workflow: Path, script: str, job: str) -> None:
        result = subprocess.run(
            [BASH, str(REPO_ROOT / "tools" / script), "bogus"], text=True, capture_output=True
        )
        assert result.returncode == 2
 def test_cpp_inputs_and_exact_defaults() -> None:
    inputs = inputs_of(CPP_WORKFLOW)
    assert set(inputs) == {
        "working-directory",
        "std",
        "compile-commands-dir",
        "clang-format-version",
        "clang-tidy-version",
        "tools-ref",
    }
    assert inputs["std"]["default"] == "c++20"
    assert inputs["compile-commands-dir"]["default"] == ""
    assert inputs["clang-format-version"]["default"] == "23.1.3"
    assert inputs["clang-tidy-version"]["default"] == "22.1.8"
 def test_csharp_inputs_and_exact_sdk_default() -> None:
    inputs = inputs_of(CSHARP_WORKFLOW)
    assert set(inputs) == {"working-directory", "project", "dotnet-sdk-version", "tools-ref"}
    assert inputs["dotnet-sdk-version"]["default"] == "10.0.401"
 def test_cpp_script_and_workflow_do_not_mention_cppcheck() -> None:
    for path in (CPP_SCRIPT, CPP_WORKFLOW):
        assert "cppcheck" not in path.read_text(encoding="utf-8").lower(), path.name
 # ----------------------------------------------------------------- helpers
 def make_repo(tmp_path: Path) -> Path:
    root = tmp_path / "repo"
    root.mkdir()
    subprocess.run(["git", "init", "-q"], cwd=root, check=True)
    return root
 def add_files(root: Path, *relative: str) -> None:
    for name in relative:
        path = root / name
        path.parent.mkdir(parents=True, exist_ok=True)
        path.write_text("x\n", encoding="utf-8", newline="\n")
    subprocess.run(["git", "add", "-A"], cwd=root, check=True)
 def stub(directory: Path, name: str) -> Path:
    path = directory / name
    path.write_text(
        "#!/usr/bin/env bash\n"
        'name="$(basename "$0")"\n'
        '[ "$name" = dotnet ] && name="dotnet $1"\n'
        'echo "$name :: $*" >> "$STUB_LOG"\n'
        'case ",${STUB_FAIL}," in\n'
        '  *",$name,"*) echo "src/a.cpp:3:1: stub finding from $name"; exit 1 ;;\n'
        "esac\n"
        "exit 0\n",
        encoding="utf-8",
        newline="\n",
    )
    path.chmod(0o755)
    return path
 def run_script(script: Path, command: str, cwd: Path, tmp_path: Path, **env: str) -> Run:
    log = tmp_path / "tools.log"
    environment = dict(os.environ)
    environment.update({"STUB_LOG": log.as_posix(), "STUB_FAIL": ""})
    environment.update(env)
    result = subprocess.run(
        [BASH, str(script), command], cwd=cwd, env=environment, text=True, capture_output=True
    )
    calls = log.read_text(encoding="utf-8").splitlines() if log.exists() else []
    return result, calls
 # --------------------------------------------------------------------- C++
@pytest.fixture
 def cpp_bin(tmp_path: Path) -> Path:
    directory = tmp_path / "bin"
    directory.mkdir()
    for tool in ("clang-format", "clang-tidy"):
        stub(directory, tool)
    return directory
 def cpp_env(cpp_bin: Path, **extra: str) -> dict[str, str]:
    values = {
        "WORKING_DIRECTORY": ".",
        "STD": "c++20",
        "COMPILE_COMMANDS_DIR": "",
        "CLANG_FORMAT_VERSION": "23.1.3",
        "CLANG_TIDY_VERSION": "22.1.8",
        "QC_VENV": "/nonexistent",
        "QC_BIN": cpp_bin.as_posix(),
    }
    values.update(extra)
    return values
 class TestCppValidate:
    def run(self, tmp_path: Path, cpp_bin: Path, **extra: str) -> Run:
        return run_script(CPP_SCRIPT, "validate", tmp_path, tmp_path, **cpp_env(cpp_bin, **extra))
    def test_accepts_the_defaults(self, tmp_path: Path, cpp_bin: Path) -> None:
        result, _ = self.run(tmp_path, cpp_bin)
        assert result.returncode == 0, result.stdout
    @pytest.mark.parametrize("std", ["c++17", "c++23", "gnu++20"])
    def test_accepts_a_cpp_standard(self, tmp_path: Path, cpp_bin: Path, std: str) -> None:
        assert self.run(tmp_path, cpp_bin, STD=std)[0].returncode == 0
    @pytest.mark.parametrize("std", ["", "c17", "c++", "latest", "c++20; rm"])
    def test_rejects_a_value_that_is_not_a_cpp_standard(
        self,
        tmp_path: Path,
        cpp_bin: Path,
        std: str,
    ) -> None:
        result, _ = self.run(tmp_path, cpp_bin, STD=std)
        assert result.returncode == 1 and "[configuration]" in result.stdout
    @pytest.mark.parametrize("directory", ["/etc", "..", "../x", "a/../..", ""])
    def test_rejects_a_working_directory_outside_the_repository(
        self,
        tmp_path: Path,
        cpp_bin: Path,
        directory: str,
    ) -> None:
        result, _ = self.run(tmp_path, cpp_bin, WORKING_DIRECTORY=directory)
        assert result.returncode == 1 and "working-directory" in result.stdout
    @pytest.mark.parametrize("directory", ["/tmp/build", "../build"])
    def test_rejects_a_compile_commands_dir_outside_the_repository(
        self,
        tmp_path: Path,
        cpp_bin: Path,
        directory: str,
    ) -> None:
        result, _ = self.run(tmp_path, cpp_bin, COMPILE_COMMANDS_DIR=directory)
        assert result.returncode == 1 and "compile-commands-dir" in result.stdout
    @pytest.mark.parametrize("name", ["CLANG_FORMAT_VERSION", "CLANG_TIDY_VERSION"])
    @pytest.mark.parametrize("version", ["", "latest", "23", ">=23", "23.1.3 --pre"])
    def test_rejects_a_version_that_is_not_exact(
        self,
        tmp_path: Path,
        cpp_bin: Path,
        name: str,
        version: str,
    ) -> None:
        result, _ = self.run(tmp_path, cpp_bin, **{name: version})
        assert result.returncode == 1 and "exact version" in result.stdout
 class TestCppRun:
    @pytest.fixture
    def repo(self, tmp_path: Path) -> Path:
        root = make_repo(tmp_path)
        add_files(root, ".clang-format")
        return root
    def run(self, repo: Path, tmp_path: Path, cpp_bin: Path, **extra: str) -> Run:
        return run_script(CPP_SCRIPT, "run", repo, tmp_path, **cpp_env(cpp_bin, **extra))
    def test_runs_clang_format_once_and_clang_tidy_per_language(
        self,
        repo: Path,
        tmp_path: Path,
        cpp_bin: Path,
    ) -> None:
        add_files(repo, "src/a.cpp", "src/a.hpp", "lib/c.c")
        result, calls = self.run(repo, tmp_path, cpp_bin)
        assert result.returncode == 0, result.stdout + result.stderr
        assert [c.split(" :: ")[0] for c in calls] == ["clang-format", "clang-tidy", "clang-tidy"]
        assert "--dry-run -Werror" in calls[0]
        assert "src/a.cpp" in calls[0] and "lib/c.c" in calls[0]
        assert "-- -std=c++20" in calls[1] and "lib/c.c" not in calls[1]
        assert "-- -std=c17" in calls[2] and "lib/c.c" in calls[2]
        assert "All selected checks passed." in result.stdout
    def test_the_std_input_reaches_clang_tidy(self, repo: Path, tmp_path: Path, cpp_bin: Path) -> None:
        add_files(repo, "a.cpp")
        _, calls = self.run(repo, tmp_path, cpp_bin, STD="c++17")
        assert "-- -std=c++17" in calls[1]
    def test_a_compile_database_is_used_instead_of_a_standard(
        self,
        repo: Path,
        tmp_path: Path,
        cpp_bin: Path,
    ) -> None:
        add_files(repo, "a.cpp", "build/compile_commands.json")
        result, calls = self.run(repo, tmp_path, cpp_bin, COMPILE_COMMANDS_DIR="build")
        assert result.returncode == 0, result.stdout
        assert len(calls) == 2
        assert "-p build" in calls[1] and "-std=" not in calls[1]
    def test_a_missing_compile_database_is_a_configuration_error(
        self,
        repo: Path,
        tmp_path: Path,
        cpp_bin: Path,
    ) -> None:
        add_files(repo, "a.cpp")
        result, calls = self.run(repo, tmp_path, cpp_bin, COMPILE_COMMANDS_DIR="build")
        assert result.returncode == 1 and "compile_commands.json" in result.stdout
        assert calls == []
    def test_a_missing_clang_format_file_is_a_configuration_error(
        self,
        tmp_path: Path,
        cpp_bin: Path,
    ) -> None:
        repo = make_repo(tmp_path)
        add_files(repo, "a.cpp")
        result, calls = self.run(repo, tmp_path, cpp_bin)
        assert result.returncode == 1
        assert "[configuration]" in result.stdout and ".clang-format" in result.stdout
        assert calls == []
    def test_a_clang_format_file_above_the_working_directory_is_found(
        self,
        repo: Path,
        tmp_path: Path,
        cpp_bin: Path,
    ) -> None:
        add_files(repo, "service/a.cpp")
        result, _ = run_script(
            CPP_SCRIPT,
            "run",
            repo,
            tmp_path,
            **cpp_env(cpp_bin, WORKING_DIRECTORY="service"),
        )
        assert result.returncode == 0, result.stdout
    def test_a_failing_tool_fails_the_job_and_the_other_still_runs(
        self,
        repo: Path,
        tmp_path: Path,
        cpp_bin: Path,
    ) -> None:
        add_files(repo, "src/a.cpp")
        result, calls = self.run(repo, tmp_path, cpp_bin, STUB_FAIL="clang-format")
        assert result.returncode == 1
        assert len(calls) == 2, "clang-tidy runs after clang-format failed"
        assert "::group::clang-format" in result.stdout
        assert "src/a.cpp:3:1: stub finding from clang-format" in result.stdout
        assert "FAIL clang-format" in result.stdout and "PASS clang-tidy (C++)" in result.stdout
        assert "Quality checks failed: clang-format" in result.stdout
    def test_a_repository_without_c_or_cpp_files_passes_with_a_notice(
        self,
        tmp_path: Path,
        cpp_bin: Path,
    ) -> None:
        repo = make_repo(tmp_path)
        add_files(repo, "README.md")
        result, calls = self.run(repo, tmp_path, cpp_bin)
        assert result.returncode == 0 and calls == []
        assert "No C or C++ files" in result.stdout
    def test_only_tracked_files_under_the_working_directory_are_checked(
        self,
        repo: Path,
        tmp_path: Path,
        cpp_bin: Path,
    ) -> None:
        add_files(repo, "top.cpp", "service/api.cpp")
        (repo / "service" / "untracked.cpp").write_text("x\n", encoding="utf-8")
        _, calls = self.run(repo, tmp_path, cpp_bin, WORKING_DIRECTORY="service")
        text = "\n".join(calls)
        assert "api.cpp" in text and "top.cpp" not in text and "untracked" not in text
    def test_no_file_is_changed(self, repo: Path, tmp_path: Path, cpp_bin: Path) -> None:
        add_files(repo, "a.cpp")
        def snapshot() -> dict[str, bytes]:
            return {p.name: p.read_bytes() for p in repo.iterdir() if p.is_file()}
        before = snapshot()
        self.run(repo, tmp_path, cpp_bin, STUB_FAIL="clang-tidy (C++)")
        assert snapshot() == before
    def test_a_missing_working_directory_is_a_configuration_error(
        self,
        repo: Path,
        tmp_path: Path,
        cpp_bin: Path,
    ) -> None:
        result, _ = self.run(repo, tmp_path, cpp_bin, WORKING_DIRECTORY="nope")
        assert result.returncode == 1 and "[configuration]" in result.stdout
 def test_cpp_install_pins_both_tools_to_the_exact_versions(tmp_path: Path) -> None:
    """`install` creates the venv and installs `==` versions; checked with a fake pip."""
    venv = tmp_path / "venv"
    fake_python = tmp_path / "bin"
    fake_python.mkdir()
    log = tmp_path / "pip.log"
    python3 = fake_python / "python3"
    python3.write_text(
        "#!/usr/bin/env bash\n"
        'mkdir -p "$3/bin"\n'
        "printf '#!/usr/bin/env bash\\necho \"$*\" >> \"%s\"\\n' > \"$3/bin/pip\"\n" % log.as_posix()
        + 'chmod +x "$3/bin/pip"\n',
        encoding="utf-8",
        newline="\n",
    )
    python3.chmod(0o755)
    environment = dict(os.environ)
    environment["PATH"] = f"{fake_python.as_posix()}:{environment['PATH']}"
    environment.update(
        {
            "QC_VENV": venv.as_posix(),
            "CLANG_FORMAT_VERSION": "23.1.3",
            "CLANG_TIDY_VERSION": "22.1.8",
        }
    )
    result = subprocess.run(
        [BASH, str(CPP_SCRIPT), "install"], env=environment, text=True, capture_output=True
    )
    assert result.returncode == 0, result.stdout + result.stderr
    installed = log.read_text(encoding="utf-8")
    assert "clang-format==23.1.3" in installed
    assert "clang-tidy==22.1.8" in installed
 # --------------------------------------------------------------------- C#
@pytest.fixture
 def dotnet_stub(tmp_path: Path) -> Path:
    directory = tmp_path / "dotnet-bin"
    directory.mkdir()
    return stub(directory, "dotnet")
 def csharp_env(dotnet_stub: Path, tmp_path: Path, **extra: str) -> dict[str, str]:
    values = {
        "WORKING_DIRECTORY": ".",
        "PROJECT": "",
        "DOTNET_SDK_VERSION": "10.0.401",
        "DOTNET_ROOT": (tmp_path / "dotnet-root").as_posix(),
        "QC_DOTNET": dotnet_stub.as_posix(),
    }
    values.update(extra)
    return values
 class TestCsharpValidate:
    def run(self, tmp_path: Path, dotnet_stub: Path, **extra: str) -> Run:
        return run_script(
            CSHARP_SCRIPT, "validate", tmp_path, tmp_path, **csharp_env(dotnet_stub, tmp_path, **extra)
        )
    @pytest.mark.parametrize("version", ["10.0.401", "10.0.100", "11.0.100", "100.1.2"])
    def test_accepts_an_exact_sdk_of_version_10_or_later(
        self,
        tmp_path: Path,
        dotnet_stub: Path,
        version: str,
    ) -> None:
        assert self.run(tmp_path, dotnet_stub, DOTNET_SDK_VERSION=version)[0].returncode == 0
    @pytest.mark.parametrize(
        "version",
        ["", "8.0.425", "9.0.100", "10.0", "10", "10.0.x", "latest", "10.0.401-rc.1", "10.0.401 --verbose"],
    )
    def test_rejects_an_old_or_inexact_sdk(self, tmp_path: Path, dotnet_stub: Path, version: str) -> None:
        result, _ = self.run(tmp_path, dotnet_stub, DOTNET_SDK_VERSION=version)
        assert result.returncode == 1
        assert "[configuration]" in result.stdout and "dotnet-sdk-version" in result.stdout
    @pytest.mark.parametrize("directory", ["/etc", "..", "../x", ""])
    def test_rejects_a_working_directory_outside_the_repository(
        self,
        tmp_path: Path,
        dotnet_stub: Path,
        directory: str,
    ) -> None:
        result, _ = self.run(tmp_path, dotnet_stub, WORKING_DIRECTORY=directory)
        assert result.returncode == 1 and "working-directory" in result.stdout
    @pytest.mark.parametrize("project", ["/etc/x.sln", "../x.sln"])
    def test_rejects_a_project_outside_the_working_directory(
        self,
        tmp_path: Path,
        dotnet_stub: Path,
        project: str,
    ) -> None:
        result, _ = self.run(tmp_path, dotnet_stub, PROJECT=project)
        assert result.returncode == 1 and "project" in result.stdout
 class TestCsharpInstall:
    def test_installs_the_exact_version_with_the_official_script(
        self,
        tmp_path: Path,
        dotnet_stub: Path,
    ) -> None:
        root = tmp_path / "dotnet-root"
        installer = tmp_path / "dotnet-install.sh"
        installer.write_text(
            "#!/usr/bin/env bash\n"
            'echo "$*" >> "$STUB_LOG"\n'
            'dir=""\n'
            'while [ "$#" -gt 0 ]; do [ "$1" = --install-dir ] && dir="$2"; shift; done\n'
            'mkdir -p "$dir"\n'
            "printf '#!/usr/bin/env bash\\necho 10.0.401\\n' > \"$dir/dotnet\"\n"
            'chmod +x "$dir/dotnet"\n',
            encoding="utf-8",
            newline="\n",
        )
        result, calls = run_script(
            CSHARP_SCRIPT,
            "install",
            tmp_path,
            tmp_path,
            **csharp_env(dotnet_stub, tmp_path, QC_DOTNET_INSTALL_SCRIPT=installer.as_posix()),
        )
        assert result.returncode == 0, result.stdout + result.stderr
        assert calls and "--version 10.0.401" in calls[0]
        assert f"--install-dir {root.as_posix()}" in calls[0]
        assert "10.0.401" in result.stdout
 class TestCsharpRun:
    @pytest.fixture
    def repo(self, tmp_path: Path) -> Path:
        return make_repo(tmp_path)
    def run(self, repo: Path, tmp_path: Path, dotnet_stub: Path, **extra: str) -> Run:
        return run_script(
            CSHARP_SCRIPT, "run", repo, tmp_path, **csharp_env(dotnet_stub, tmp_path, **extra)
        )
    def test_runs_format_and_build_on_the_single_solution(
        self,
        repo: Path,
        tmp_path: Path,
        dotnet_stub: Path,
    ) -> None:
        add_files(repo, "App.sln", "src/App.csproj", "src/Program.cs")
        result, calls = self.run(repo, tmp_path, dotnet_stub)
        assert result.returncode == 0, result.stdout + result.stderr
        assert [c.split(" :: ")[0] for c in calls] == ["dotnet format", "dotnet build"]
        assert "App.sln" in calls[0] and "--verify-no-changes" in calls[0]
        assert "App.sln" in calls[1] and "-warnaserror" in calls[1]
        assert "All selected checks passed." in result.stdout
    def test_uses_the_single_project_when_there_is_no_solution(
        self,
        repo: Path,
        tmp_path: Path,
        dotnet_stub: Path,
    ) -> None:
        add_files(repo, "src/App.csproj", "src/Program.cs")
        _, calls = self.run(repo, tmp_path, dotnet_stub)
        assert "src/App.csproj" in calls[0]
    def test_several_projects_without_a_solution_need_the_project_input(
        self,
        repo: Path,
        tmp_path: Path,
        dotnet_stub: Path,
    ) -> None:
        add_files(repo, "a/A.csproj", "b/B.csproj", "a/P.cs")
        result, calls = self.run(repo, tmp_path, dotnet_stub)
        assert result.returncode == 1 and calls == []
        assert "[configuration]" in result.stdout
        assert "a/A.csproj" in result.stdout and "b/B.csproj" in result.stdout
    def test_the_project_input_picks_one(self, repo: Path, tmp_path: Path, dotnet_stub: Path) -> None:
        add_files(repo, "a/A.csproj", "b/B.csproj", "a/P.cs")
        result, calls = self.run(repo, tmp_path, dotnet_stub, PROJECT="b/B.csproj")
        assert result.returncode == 0 and "b/B.csproj" in calls[0]
    def test_a_missing_project_file_is_a_configuration_error(
        self,
        repo: Path,
        tmp_path: Path,
        dotnet_stub: Path,
    ) -> None:
        add_files(repo, "a/P.cs")
        result, calls = self.run(repo, tmp_path, dotnet_stub, PROJECT="nope.csproj")
        assert result.returncode == 1 and "does not exist" in result.stdout and calls == []
    def test_csharp_files_without_a_project_are_a_configuration_error(
        self,
        repo: Path,
        tmp_path: Path,
        dotnet_stub: Path,
    ) -> None:
        add_files(repo, "Program.cs")
        result, calls = self.run(repo, tmp_path, dotnet_stub)
        assert result.returncode == 1 and calls == []
        assert "[configuration]" in result.stdout and "no solution or project" in result.stdout
    def test_a_repository_without_csharp_files_passes_with_a_notice(
        self,
        repo: Path,
        tmp_path: Path,
        dotnet_stub: Path,
    ) -> None:
        add_files(repo, "README.md")
        result, calls = self.run(repo, tmp_path, dotnet_stub)
        assert result.returncode == 0 and calls == []
        assert "No C# files" in result.stdout
    def test_a_failing_tool_fails_the_job_and_the_other_still_runs(
        self,
        repo: Path,
        tmp_path: Path,
        dotnet_stub: Path,
    ) -> None:
        add_files(repo, "App.sln", "Program.cs")
        result, calls = self.run(repo, tmp_path, dotnet_stub, STUB_FAIL="dotnet format")
        assert result.returncode == 1 and len(calls) == 2
        assert "::group::dotnet format --verify-no-changes" in result.stdout
        assert "FAIL dotnet format --verify-no-changes" in result.stdout
        assert "PASS dotnet build -warnaserror" in result.stdout
        assert "Quality checks failed: dotnet format --verify-no-changes" in result.stdout
    def test_only_files_under_the_working_directory_are_considered(
        self,
        repo: Path,
        tmp_path: Path,
        dotnet_stub: Path,
    ) -> None:
        add_files(repo, "Top.sln", "svc/Svc.csproj", "svc/P.cs", "Top.cs")
        result, calls = self.run(repo, tmp_path, dotnet_stub, WORKING_DIRECTORY="svc")
        assert result.returncode == 0
        assert "Svc.csproj" in calls[0] and "Top.sln" not in calls[0]
    def test_a_missing_working_directory_is_a_configuration_error(
        self,
        repo: Path,
        tmp_path: Path,
        dotnet_stub: Path,
    ) -> None:
        result, _ = self.run(repo, tmp_path, dotnet_stub, WORKING_DIRECTORY="nope")
        assert result.returncode == 1 and "[configuration]" in result.stdout
@@ -1,144 +0,0 @@
 #!/usr/bin/env bash
 # Steps of the reusable workflow .gitea/workflows/quality-checks-cpp.yml
 # (ADR-0008). The workflow checks out the calling repository, fetches this file
 # into shared-scripts/ and runs one command per step:
 #
 #   quality-checks-cpp.sh validate   check the inputs, before anything is installed
 #   quality-checks-cpp.sh install    install the exact clang tool versions into a venv
 #   quality-checks-cpp.sh run        run clang-format and clang-tidy on the tracked files
 #
 # Settings come from the environment, never from interpolated expressions:
 #   WORKING_DIRECTORY, STD, COMPILE_COMMANDS_DIR, CLANG_FORMAT_VERSION,
 #   CLANG_TIDY_VERSION, QC_VENV (and QC_BIN for tests).
 # Every failure is printed as ::error::[category] message.
 C_STANDARD="${C_STANDARD:-c17}"
 validate_inputs() {
  set -u
  case "$WORKING_DIRECTORY" in
    "" | /* | .. | ../* | */.. | */../*)
      echo "::error::[configuration] working-directory must be a relative path inside the repository."
      exit 1
      ;;
  esac
  if ! [[ "$STD" =~ ^(c\+\+|gnu\+\+)[0-9]{2}$ ]]; then
    echo "::error::[configuration] std '$STD' is not a C++ standard such as c++20 or gnu++20."
    exit 1
  fi
  case "$COMPILE_COMMANDS_DIR" in
    /* | .. | ../* | */.. | */../*)
      echo "::error::[configuration] compile-commands-dir must be a relative path inside the repository."
      exit 1
      ;;
  esac
  local name version
  for name in CLANG_FORMAT_VERSION CLANG_TIDY_VERSION; do
    version="${!name}"
    if ! [[ "$version" =~ ^[0-9]+(\.[0-9]+){1,3}$ ]]; then
      echo "::error::[configuration] ${name,,} '$version' is not an exact version such as 23.1.3."
      exit 1
    fi
  done
  echo "Checking C and C++ in ${WORKING_DIRECTORY} with std ${STD}"
 }
 install_tools() {
  set -eu
  python3 -m venv "$QC_VENV"
  "$QC_VENV/bin/pip" install --quiet \
    "clang-format==${CLANG_FORMAT_VERSION}" "clang-tidy==${CLANG_TIDY_VERSION}"
 }
 # A .clang-format must exist in the working directory or above it, up to the
 # top of the repository: clang-format finds its style the same way.
 find_clang_format_config() {
  local top dir parent
  top="$(cd "$(git rev-parse --show-toplevel)" && pwd -P)"
  dir="$(pwd -P)"
  while true; do
    if [ -f "$dir/.clang-format" ] || [ -f "$dir/_clang-format" ]; then
      return 0
    fi
    parent="$(dirname "$dir")"
    # stop at the top of the repository, or at the file system root
    if [ "$dir" = "$top" ] || [ "$parent" = "$dir" ]; then
      return 1
    fi
    dir="$parent"
  done
 }
 run_checks() {
  set -u
  QC_BIN="${QC_BIN:-$QC_VENV/bin}"
  if [ ! -d "$WORKING_DIRECTORY" ]; then
    echo "::error::[configuration] working-directory '$WORKING_DIRECTORY' does not exist."
    exit 1
  fi
  cd "$WORKING_DIRECTORY"
  local all_files cpp_files c_files
  mapfile -t all_files < <(git ls-files -- '*.c' '*.cc' '*.cpp' '*.cxx' '*.h' '*.hh' '*.hpp' '*.hxx')
  if [ "${#all_files[@]}" -eq 0 ]; then
    echo "::notice::No C or C++ files in '$WORKING_DIRECTORY'; nothing was checked."
    echo "All selected checks passed."
    exit 0
  fi
  if ! find_clang_format_config; then
    echo "::error::[configuration] No .clang-format found in '$WORKING_DIRECTORY' or above it; add the style of the project."
    exit 1
  fi
  if [ -n "$COMPILE_COMMANDS_DIR" ] && [ ! -f "$COMPILE_COMMANDS_DIR/compile_commands.json" ]; then
    echo "::error::[configuration] compile-commands-dir '$COMPILE_COMMANDS_DIR' has no compile_commands.json; build it before the call."
    exit 1
  fi
  # .c files are C; everything else (including headers) is checked as C++.
  mapfile -t c_files < <(git ls-files -- '*.c')
  mapfile -t cpp_files < <(git ls-files -- '*.cc' '*.cpp' '*.cxx' '*.h' '*.hh' '*.hpp' '*.hxx')
  local failed=()
  run_tool() {
    local name="$1"
    shift
    echo "::group::$name"
    if "$@"; then
      echo "::endgroup::"
      echo "PASS $name"
    else
      echo "::endgroup::"
      echo "FAIL $name"
      failed+=("$name")
    fi
  }
  run_tool "clang-format" "$QC_BIN/clang-format" --dry-run -Werror "${all_files[@]}"
  if [ -n "$COMPILE_COMMANDS_DIR" ]; then
    run_tool "clang-tidy" "$QC_BIN/clang-tidy" --quiet -p "$COMPILE_COMMANDS_DIR" "${all_files[@]}"
  else
    if [ "${#cpp_files[@]}" -gt 0 ]; then
      run_tool "clang-tidy (C++)" "$QC_BIN/clang-tidy" --quiet "${cpp_files[@]}" -- "-std=${STD}"
    fi
    if [ "${#c_files[@]}" -gt 0 ]; then
      run_tool "clang-tidy (C)" "$QC_BIN/clang-tidy" --quiet "${c_files[@]}" -- "-std=${C_STANDARD}"
    fi
  fi
  if [ "${#failed[@]}" -gt 0 ]; then
    echo "::error::Quality checks failed: ${failed[*]}"
    exit 1
  fi
  echo "All selected checks passed."
 }
 case "${1:-}" in
  validate) validate_inputs ;;
  install) install_tools ;;
  run) run_checks ;;
  *)
    echo "::error::[configuration] usage: quality-checks-cpp.sh validate|install|run" >&2
    exit 2
    ;;
 esac
@@ -1,124 +0,0 @@
 #!/usr/bin/env bash
 # Steps of the reusable workflow .gitea/workflows/quality-checks-csharp.yml
 # (ADR-0008). The workflow checks out the calling repository, fetches this file
 # into shared-scripts/ and runs one command per step:
 #
 #   quality-checks-csharp.sh validate   check the inputs, before anything is installed
 #   quality-checks-csharp.sh install    install the exact .NET SDK version
 #   quality-checks-csharp.sh run        run dotnet format and dotnet build on the project
 #
 # Settings come from the environment, never from interpolated expressions:
 #   WORKING_DIRECTORY, PROJECT, DOTNET_SDK_VERSION, DOTNET_ROOT (and
 #   QC_DOTNET_INSTALL_SCRIPT, QC_DOTNET for tests).
 # Every failure is printed as ::error::[category] message.
 DOTNET_INSTALL_URL="https://dot.net/v1/dotnet-install.sh"
 validate_inputs() {
  set -u
  case "$WORKING_DIRECTORY" in
    "" | /* | .. | ../* | */.. | */../*)
      echo "::error::[configuration] working-directory must be a relative path inside the repository."
      exit 1
      ;;
  esac
  case "$PROJECT" in
    /* | .. | ../* | */.. | */../*)
      echo "::error::[configuration] project must be a relative path inside the working directory."
      exit 1
      ;;
  esac
  # An exact stable version of the .NET SDK, 10 or later (no channel, no range).
  if ! [[ "$DOTNET_SDK_VERSION" =~ ^([1-9][0-9]+)\.[0-9]+\.[0-9]+$ ]] || [ "${BASH_REMATCH[1]}" -lt 10 ]; then
    echo "::error::[configuration] dotnet-sdk-version '$DOTNET_SDK_VERSION' is not an exact stable version 10 or later, such as 10.0.401."
    exit 1
  fi
  echo "Checking C# in ${WORKING_DIRECTORY} with .NET SDK ${DOTNET_SDK_VERSION}"
 }
 install_sdk() {
  set -eu
  local script="${QC_DOTNET_INSTALL_SCRIPT:-}"
  if [ -z "$script" ]; then
    script="$(mktemp)"
    curl -fsSL "$DOTNET_INSTALL_URL" -o "$script"
  fi
  bash "$script" --version "$DOTNET_SDK_VERSION" --install-dir "$DOTNET_ROOT" --no-path
  "$DOTNET_ROOT/dotnet" --version
 }
 run_checks() {
  set -u
  if [ ! -d "$WORKING_DIRECTORY" ]; then
    echo "::error::[configuration] working-directory '$WORKING_DIRECTORY' does not exist."
    exit 1
  fi
  cd "$WORKING_DIRECTORY"
  local dotnet="${QC_DOTNET:-$DOTNET_ROOT/dotnet}"
  local sources
  mapfile -t sources < <(git ls-files -- '*.cs')
  if [ "${#sources[@]}" -eq 0 ]; then
    echo "::notice::No C# files in '$WORKING_DIRECTORY'; nothing was checked."
    echo "All selected checks passed."
    exit 0
  fi
  local target="$PROJECT" candidates
  if [ -z "$target" ]; then
    mapfile -t candidates < <(git ls-files -- '*.sln' '*.slnx')
    if [ "${#candidates[@]}" -eq 0 ]; then
      mapfile -t candidates < <(git ls-files -- '*.csproj')
    fi
    case "${#candidates[@]}" in
      0)
        echo "::error::[configuration] C# files exist but no solution or project was found in '$WORKING_DIRECTORY'; add one or set the input project."
        exit 1
        ;;
      1) target="${candidates[0]}" ;;
      *)
        echo "::error::[configuration] Several solutions or projects were found (${candidates[*]}); set the input project."
        exit 1
        ;;
    esac
  elif [ ! -f "$target" ]; then
    echo "::error::[configuration] project '$target' does not exist in '$WORKING_DIRECTORY'."
    exit 1
  fi
  echo "Checking $target"
  export DOTNET_CLI_TELEMETRY_OPTOUT=1 DOTNET_NOLOGO=1
  local failed=()
  run_tool() {
    local name="$1"
    shift
    echo "::group::$name"
    if "$@"; then
      echo "::endgroup::"
      echo "PASS $name"
    else
      echo "::endgroup::"
      echo "FAIL $name"
      failed+=("$name")
    fi
  }
  run_tool "dotnet format --verify-no-changes" "$dotnet" format "$target" --verify-no-changes
  run_tool "dotnet build -warnaserror" "$dotnet" build "$target" --nologo -warnaserror
  if [ "${#failed[@]}" -gt 0 ]; then
    echo "::error::Quality checks failed: ${failed[*]}"
    exit 1
  fi
  echo "All selected checks passed."
 }
 case "${1:-}" in
  validate) validate_inputs ;;
  install) install_sdk ;;
  run) run_checks ;;
  *)
    echo "::error::[configuration] usage: quality-checks-csharp.sh validate|install|run" >&2
    exit 2
    ;;
 esac
@@ -1,4 +1,4 @@
-<!-- translation of Home.md, source sha256 5751829e99af -->
+<!-- translation of Home.md, source sha256 510b243ec5f2 -->
 > Dette er en oversættelse af [`Home`](Home). Den engelske side er autoritativ, og ændringer her bliver overskrevet, næste gang wikien publiceres.
@@ -13,22 +13,19 @@ En samling af genbrugelige Gitea Actions-workflows til DevOps-professionelle og
 Dette repository er den centrale samling af genbrugelig automatisering til TirSystems repositories. Det primære repository ligger på `git.tirsystem.com` (Gitea) og spejles med push til GitHub.
-Det indeholder otte workflows: synkronisering af metadata til GitHub-spejlet, publicering af wiki, fælles kvalitetskontrol for Python og shell, for C og C++ og for C#, et udgivelsesworkflow, publicering af accepterede milepæle og repositoryets egen validering. De er listet med formål og diagram under [Workflows](#workflows).
+Det indeholder fem workflows: synkronisering af metadata til GitHub-spejlet, publicering af wiki, fælles kvalitetskontrol, et udgivelsesworkflow og repositoryets egen validering. De er listet med formål og diagram under [Workflows](#workflows).
 ## Workflows
-Der er otte workflows i dette repository. Et **scoped** workflow leveres af instansen til alle repositories i TirSystem-organisationerne og kræver intet i repositoryet; et **genbrugeligt** workflow kaldes fra et repository med `uses:`; de øvrige kører kun her. Diagrammerne er PlantUML-kildekode og er på engelsk.
+Der er fem workflows i dette repository. Et **scoped** workflow leveres af instansen til alle repositories i TirSystem-organisationerne og kræver intet i repositoryet; et **genbrugeligt** workflow kaldes fra et repository med `uses:`; de øvrige kører kun her. Diagrammerne er PlantUML-kildekode og er på engelsk.
 | Workflow | Fil | Type | Starter ved | Formål |
 | --- | --- | --- | --- | --- |
 | Sync GitHub mirror metadata | [`sync-github-metadata.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/scoped_workflows/sync-github-metadata.yml) | Scoped | push til `main`, manuelt, dagligt kl. 03:17 UTC | Kopierer beskrivelsen og emnerne for et Gitea-repository til dets GitHub push-spejl |
 | Publish wiki | [`publish-wiki.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/scoped_workflows/publish-wiki.yml) | Scoped, tilmelding med `wiki/.publish` | push til `main`, der ændrer `wiki/**`, manuelt | Publicerer siderne i `wiki/` til repositoryets wiki |
 | Quality checks | [`quality-checks.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/quality-checks.yml) | Genbrugeligt (`workflow_call`) | et kald fra et andet repository | Kører ruff, mypy, shellcheck og shfmt på de sporede filer og ændrer intet |
 | Quality checks C++ | [`quality-checks-cpp.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/quality-checks-cpp.yml) | Genbrugeligt (`workflow_call`) | et kald fra et andet repository | Kører clang-format og clang-tidy i præcise versioner på de sporede C- og C++-filer og ændrer intet |
 | Quality checks C# | [`quality-checks-csharp.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/quality-checks-csharp.yml) | Genbrugeligt (`workflow_call`) | et kald fra et andet repository | Kører `dotnet format` og `dotnet build` på et præcist .NET SDK 10 eller nyere og ændrer intet |
 | Release | [`release.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/release.yml) | Kun dette repository | manuelt | Opretter versionstagget, udgivelsessiden og major-tagget efter kontrollerne |
 | Publicering af accepterede milepæle | [`sync-milestones.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/sync-milestones.yml) | Kun dette repository | push til `main`, der ændrer `docs/milestones/**` eller `docs/sqa/reviews/**`, manuelt (tørkørsel som standard) | Opretter eller opdaterer Gitea-milepælen og issues for hver milepæl, der er Accepted med en Go-gennemgang |
 | Validate workflows | [`validate-workflows.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/validate-workflows.yml) | Kun dette repository | pull request, push til `main`, manuelt | Læser hvert workflow som YAML og kører offline-testene |
 ### Synkronisering af GitHub-metadata
@@ -187,96 +184,6 @@ deactivate Workflow
@enduml
 ```
 ### Kvalitetskontrol C++
 Et genbrugeligt workflow til C og C++, kaldt med `uses: TirSystem/github-action/.gitea/workflows/quality-checks-cpp.yml@v1` (ADR-0008). Repositoryet skal have en `.clang-format`; en `.clang-tidy` og en compile-database er valgfrie.
 #### Workflow
 ```plantuml
@startuml
 title Shared quality checks for C and C++ (reusable workflow)
 autonumber
 actor "Calling repository\nuses: ...quality-checks-cpp.yml@v1" as Caller
 participant "Gitea Actions\nquality-checks-cpp" as Workflow
 participant "PyPI" as PyPI
 Caller -> Workflow: workflow_call with working-directory, std,\ncompile-commands-dir and tool versions
 activate Workflow
 Workflow -> Workflow: Check out the caller and the shared script
 Workflow -> Workflow: Validate the inputs
 alt an input is invalid or a version is not exact
  Workflow --> Caller: Fail with [configuration]
 end
 Workflow -> PyPI: Install clang-format and clang-tidy at the exact versions
 PyPI --> Workflow: Tools installed
 alt no C or C++ file is tracked
  Workflow --> Caller: Notice: nothing was checked, pass
 else no .clang-format, or compile-commands-dir\nwithout compile_commands.json
  Workflow --> Caller: Fail with [configuration]
 else
  Workflow -> Workflow: clang-format --dry-run -Werror on all files
  Workflow -> Workflow: clang-tidy on the C++ files (-std=std)\nand on the C files (or with the compile database)
  alt any tool failed
    Workflow --> Caller: Fail with tool, file and line in the log
  else
    Workflow --> Caller: All selected checks passed
  end
 end
 deactivate Workflow
@enduml
 ```
 ### Kvalitetskontrol C#
 Et genbrugeligt workflow til C#, kaldt med `uses: TirSystem/github-action/.gitea/workflows/quality-checks-csharp.yml@v1` (ADR-0008). Det installerer det præcise .NET SDK, som `dotnet-sdk-version` angiver (10 eller nyere), og skal bruge netværket til pakkegendannelsen.
 #### Workflow
 ```plantuml
@startuml
 title Shared quality checks for C# (reusable workflow)
 autonumber
 actor "Calling repository\nuses: ...quality-checks-csharp.yml@v1" as Caller
 participant "Gitea Actions\nquality-checks-csharp" as Workflow
 participant "dot.net\n(dotnet-install.sh)" as DotNet
 Caller -> Workflow: workflow_call with working-directory,\nproject and dotnet-sdk-version
 activate Workflow
 Workflow -> Workflow: Check out the caller and the shared script
 Workflow -> Workflow: Validate the inputs
 alt an input is invalid or the SDK is not an exact\nstable version 10 or later
  Workflow --> Caller: Fail with [configuration]
 end
 Workflow -> DotNet: Install the exact .NET SDK version
 DotNet --> Workflow: SDK installed
 alt no C# file is tracked
  Workflow --> Caller: Notice: nothing was checked, pass
 else no solution or project, or several without the project input
  Workflow --> Caller: Fail with [configuration] that names them
 else
  Workflow -> Workflow: dotnet format --verify-no-changes
  Workflow -> Workflow: dotnet build -warnaserror\n(package restore needs the network)
  alt any tool failed
    Workflow --> Caller: Fail with tool, file and line in the log
  else
    Workflow --> Caller: All selected checks passed
  end
 end
 deactivate Workflow
@enduml
 ```
 ### Udgivelse
 Startes manuelt af en vedligeholder; med `dry_run` `true` (standard) kontrollerer det kun (se [udgivelsesprocessen](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/guides/release-process.md)).
@@ -326,54 +233,6 @@ deactivate Workflow
@enduml
 ```
 ### Publicering af accepterede milepæle
 Permanent tilladelse til at publicere: ved et push til `main`, der ændrer milepælene eller deres gennemgange, oprettes eller opdateres hver milepæl, hvis seneste række i Version History er Accepted, og hvis seneste gennemgang er en Go, på Gitea med sine opgaver som issues. Intet lukkes eller slettes. En manuel kørsel er en tørkørsel, medmindre `dry_run` slås fra. Det bruger secret'en `TOKEN_FOR_GITEA` og `--accepted-only`-reglen i det monterede framework (v0.5.0 eller nyere).
 #### Workflow
 ```plantuml
@startuml
 title Publish accepted milestones (this repository)
 autonumber
 actor "Push to main that changes\ndocs/milestones/** or docs/sqa/reviews/**,\nor manual trigger" as Trigger
 participant "Gitea Actions\nsync-milestones" as Workflow
 participant "framework/scripts/\nsync-project.sh" as Script
 participant "Gitea REST API" as Gitea
 Trigger -> Workflow: Start workflow
 activate Workflow
 Workflow -> Workflow: Check out the project and the framework\nsubmodules over HTTPS with TOKEN_FOR_GITEA
 Workflow -> Script: --accepted-only (dry run)\nor --accepted-only --apply
 activate Script
 loop for each docs/milestones/mil-*.md
  alt latest Version History row is not Accepted,\nor the latest review record is not a Go
    Script -> Script: Skip with the reason on stderr
  else
    alt dry run
      Script -> Script: Print the plan, no network call
    else
      Script -> Gitea: Create or update the Milestone\nand one Issue per task row
      Gitea --> Script: Milestone and issue numbers
    end
  end
 end
 note right of Script
 Nothing is closed or deleted.
 Each real run edits the issues
 of every accepted milestone.
 end note
 Script --> Workflow: Done, or "nothing to publish"
 deactivate Script
 Workflow --> Trigger: Workflow result
 deactivate Workflow
@enduml
 ```
 ### Validering af workflows
 Repositoryets egen validering: de offline-tests, der er en betingelse for hver pull request.
@@ -13,22 +13,19 @@ A collection of reusable Gitea Actions workflows for DevOps professionals and so
 This repository is the central collection of reusable automation for TirSystem repositories. The primary repository lives at `git.tirsystem.com` (Gitea) and is push-mirrored to GitHub.
-It contains eight workflows: metadata sync to the GitHub mirror, wiki publishing, shared quality checks for Python and shell, for C and C++ and for C#, a release workflow, the publishing of accepted milestones and the repository's own validation. They are listed with their purpose and a diagram under [Workflows](#workflows).
+It contains five workflows: metadata sync to the GitHub mirror, wiki publishing, shared quality checks, a release workflow and the repository's own validation. They are listed with their purpose and a diagram under [Workflows](#workflows).
 ## Workflows
-Eight workflows live in this repository. A **scoped** workflow is delivered by the instance to every repository of the TirSystem organizations and needs nothing in the repository; a **reusable** workflow is called by a repository with `uses:`; the others run only here. The diagrams are PlantUML source.
+Five workflows live in this repository. A **scoped** workflow is delivered by the instance to every repository of the TirSystem organizations and needs nothing in the repository; a **reusable** workflow is called by a repository with `uses:`; the others run only here. The diagrams are PlantUML source.
 | Workflow | File | Kind | Starts on | Purpose |
 | --- | --- | --- | --- | --- |
 | Sync GitHub mirror metadata | [`sync-github-metadata.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/scoped_workflows/sync-github-metadata.yml) | Scoped | push to `main`, manual, daily 03:17 UTC | Copies the description and topics of a Gitea repository to its GitHub push mirror |
 | Publish wiki | [`publish-wiki.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/scoped_workflows/publish-wiki.yml) | Scoped, opt-in with `wiki/.publish` | push to `main` that changes `wiki/**`, manual | Publishes the pages in `wiki/` to the repository wiki |
 | Quality checks | [`quality-checks.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/quality-checks.yml) | Reusable (`workflow_call`) | a call from another repository | Runs ruff, mypy, shellcheck and shfmt on the tracked files and changes nothing |
 | Quality checks C++ | [`quality-checks-cpp.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/quality-checks-cpp.yml) | Reusable (`workflow_call`) | a call from another repository | Runs clang-format and clang-tidy at exact versions on the tracked C and C++ files and changes nothing |
 | Quality checks C# | [`quality-checks-csharp.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/quality-checks-csharp.yml) | Reusable (`workflow_call`) | a call from another repository | Runs `dotnet format` and `dotnet build` on an exact .NET SDK 10 or later and changes nothing |
 | Release | [`release.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/release.yml) | This repository only | manual | Creates the version tag, the release page and the major tag after the checks |
 | Publish accepted milestones | [`sync-milestones.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/sync-milestones.yml) | This repository only | push to `main` that changes `docs/milestones/**` or `docs/sqa/reviews/**`, manual (dry run by default) | Creates or updates the Gitea milestone and issues of every milestone that is Accepted with a Go review |
 | Validate workflows | [`validate-workflows.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/validate-workflows.yml) | This repository only | pull request, push to `main`, manual | Parses every workflow and runs the offline tests |
 ### Sync GitHub metadata
@@ -187,96 +184,6 @@ deactivate Workflow
@enduml
 ```
 ### Quality checks C++
 A reusable workflow for C and C++, called with `uses: TirSystem/github-action/.gitea/workflows/quality-checks-cpp.yml@v1` (ADR-0008). The repository needs a `.clang-format`; a `.clang-tidy` and a compile database are optional.
 #### Workflow
 ```plantuml
@startuml
 title Shared quality checks for C and C++ (reusable workflow)
 autonumber
 actor "Calling repository\nuses: ...quality-checks-cpp.yml@v1" as Caller
 participant "Gitea Actions\nquality-checks-cpp" as Workflow
 participant "PyPI" as PyPI
 Caller -> Workflow: workflow_call with working-directory, std,\ncompile-commands-dir and tool versions
 activate Workflow
 Workflow -> Workflow: Check out the caller and the shared script
 Workflow -> Workflow: Validate the inputs
 alt an input is invalid or a version is not exact
  Workflow --> Caller: Fail with [configuration]
 end
 Workflow -> PyPI: Install clang-format and clang-tidy at the exact versions
 PyPI --> Workflow: Tools installed
 alt no C or C++ file is tracked
  Workflow --> Caller: Notice: nothing was checked, pass
 else no .clang-format, or compile-commands-dir\nwithout compile_commands.json
  Workflow --> Caller: Fail with [configuration]
 else
  Workflow -> Workflow: clang-format --dry-run -Werror on all files
  Workflow -> Workflow: clang-tidy on the C++ files (-std=std)\nand on the C files (or with the compile database)
  alt any tool failed
    Workflow --> Caller: Fail with tool, file and line in the log
  else
    Workflow --> Caller: All selected checks passed
  end
 end
 deactivate Workflow
@enduml
 ```
 ### Quality checks C#
 A reusable workflow for C#, called with `uses: TirSystem/github-action/.gitea/workflows/quality-checks-csharp.yml@v1` (ADR-0008). It installs the exact .NET SDK given by `dotnet-sdk-version` (10 or later) and needs the network for the package restore.
 #### Workflow
 ```plantuml
@startuml
 title Shared quality checks for C# (reusable workflow)
 autonumber
 actor "Calling repository\nuses: ...quality-checks-csharp.yml@v1" as Caller
 participant "Gitea Actions\nquality-checks-csharp" as Workflow
 participant "dot.net\n(dotnet-install.sh)" as DotNet
 Caller -> Workflow: workflow_call with working-directory,\nproject and dotnet-sdk-version
 activate Workflow
 Workflow -> Workflow: Check out the caller and the shared script
 Workflow -> Workflow: Validate the inputs
 alt an input is invalid or the SDK is not an exact\nstable version 10 or later
  Workflow --> Caller: Fail with [configuration]
 end
 Workflow -> DotNet: Install the exact .NET SDK version
 DotNet --> Workflow: SDK installed
 alt no C# file is tracked
  Workflow --> Caller: Notice: nothing was checked, pass
 else no solution or project, or several without the project input
  Workflow --> Caller: Fail with [configuration] that names them
 else
  Workflow -> Workflow: dotnet format --verify-no-changes
  Workflow -> Workflow: dotnet build -warnaserror\n(package restore needs the network)
  alt any tool failed
    Workflow --> Caller: Fail with tool, file and line in the log
  else
    Workflow --> Caller: All selected checks passed
  end
 end
 deactivate Workflow
@enduml
 ```
 ### Release
 Started by hand by a maintainer; with `dry_run` `true` (the default) it only checks (see the [release process](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/guides/release-process.md)).
@@ -326,54 +233,6 @@ deactivate Workflow
@enduml
 ```
 ### Publish accepted milestones
 Standing authorization to publish: on a push to `main` that changes the milestones or their reviews, every milestone whose latest Version History row is Accepted and whose latest review is a Go is created or updated on Gitea with its tasks as issues. Nothing is closed or deleted. A manual run is a dry run unless `dry_run` is switched off. It uses the secret `TOKEN_FOR_GITEA` and the `--accepted-only` rule of the mounted framework (v0.5.0 or later).
 #### Workflow
 ```plantuml
@startuml
 title Publish accepted milestones (this repository)
 autonumber
 actor "Push to main that changes\ndocs/milestones/** or docs/sqa/reviews/**,\nor manual trigger" as Trigger
 participant "Gitea Actions\nsync-milestones" as Workflow
 participant "framework/scripts/\nsync-project.sh" as Script
 participant "Gitea REST API" as Gitea
 Trigger -> Workflow: Start workflow
 activate Workflow
 Workflow -> Workflow: Check out the project and the framework\nsubmodules over HTTPS with TOKEN_FOR_GITEA
 Workflow -> Script: --accepted-only (dry run)\nor --accepted-only --apply
 activate Script
 loop for each docs/milestones/mil-*.md
  alt latest Version History row is not Accepted,\nor the latest review record is not a Go
    Script -> Script: Skip with the reason on stderr
  else
    alt dry run
      Script -> Script: Print the plan, no network call
    else
      Script -> Gitea: Create or update the Milestone\nand one Issue per task row
      Gitea --> Script: Milestone and issue numbers
    end
  end
 end
 note right of Script
 Nothing is closed or deleted.
 Each real run edits the issues
 of every accepted milestone.
 end note
 Script --> Workflow: Done, or "nothing to publish"
 deactivate Script
 Workflow --> Trigger: Workflow result
 deactivate Workflow
@enduml
 ```
 ### Validate workflows
 The repository's own validation: the offline tests that gate every pull request.
@@ -1,4 +1,4 @@
-<!-- translation of Home.md, source sha256 5751829e99af -->
+<!-- translation of Home.md, source sha256 510b243ec5f2 -->
 > Ini ialah terjemahan [`Home`](Home). Halaman bahasa Inggeris ialah teks yang sah, dan perubahan di sini akan ditimpa pada penerbitan wiki yang seterusnya.
@@ -13,22 +13,19 @@ Koleksi aliran kerja (workflow) Gitea Actions yang boleh digunakan semula untuk
 Repositori ini ialah koleksi pusat bagi automasi yang boleh digunakan semula untuk repositori TirSystem. Repositori utama berada di `git.tirsystem.com` (Gitea) dan dicerminkan dengan push ke GitHub.
-Ia mengandungi lapan aliran kerja: penyegerakan metadata ke cermin GitHub, penerbitan wiki, semakan kualiti bersama untuk Python dan shell, untuk C dan C++ serta untuk C#, aliran kerja keluaran, penerbitan pencapaian (milestone) yang diterima dan pengesahan repositori sendiri. Ia disenaraikan dengan tujuan dan rajah di bawah [Aliran kerja](#aliran-kerja).
+Ia mengandungi lima aliran kerja: penyegerakan metadata ke cermin GitHub, penerbitan wiki, semakan kualiti bersama, aliran kerja keluaran dan pengesahan repositori sendiri. Ia disenaraikan dengan tujuan dan rajah di bawah [Aliran kerja](#aliran-kerja).
 ## Aliran kerja
-Terdapat lapan aliran kerja dalam repositori ini. Aliran kerja **scoped** dihantar oleh instans ke setiap repositori organisasi TirSystem dan tidak memerlukan apa-apa dalam repositori; aliran kerja **boleh guna semula** dipanggil oleh sebuah repositori dengan `uses:`; yang lain hanya berjalan di sini. Rajah ialah kod sumber PlantUML dan dalam bahasa Inggeris.
+Terdapat lima aliran kerja dalam repositori ini. Aliran kerja **scoped** dihantar oleh instans ke setiap repositori organisasi TirSystem dan tidak memerlukan apa-apa dalam repositori; aliran kerja **boleh guna semula** dipanggil oleh sebuah repositori dengan `uses:`; yang lain hanya berjalan di sini. Rajah ialah kod sumber PlantUML dan dalam bahasa Inggeris.
 | Aliran kerja | Fail | Jenis | Bermula apabila | Tujuan |
 | --- | --- | --- | --- | --- |
 | Sync GitHub mirror metadata | [`sync-github-metadata.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/scoped_workflows/sync-github-metadata.yml) | Scoped | push ke `main`, manual, setiap hari 03:17 UTC | Menyalin penerangan dan topik repositori Gitea ke push mirror GitHub-nya |
 | Publish wiki | [`publish-wiki.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/scoped_workflows/publish-wiki.yml) | Scoped, pilih menyertai dengan `wiki/.publish` | push ke `main` yang mengubah `wiki/**`, manual | Menerbitkan halaman dalam `wiki/` ke wiki repositori |
 | Quality checks | [`quality-checks.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/quality-checks.yml) | Boleh guna semula (`workflow_call`) | panggilan daripada repositori lain | Menjalankan ruff, mypy, shellcheck dan shfmt pada fail yang dijejaki dan tidak mengubah apa-apa |
 | Quality checks C++ | [`quality-checks-cpp.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/quality-checks-cpp.yml) | Boleh guna semula (`workflow_call`) | panggilan daripada repositori lain | Menjalankan clang-format dan clang-tidy pada versi tepat pada fail C dan C++ yang dijejaki dan tidak mengubah apa-apa |
 | Quality checks C# | [`quality-checks-csharp.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/quality-checks-csharp.yml) | Boleh guna semula (`workflow_call`) | panggilan daripada repositori lain | Menjalankan `dotnet format` dan `dotnet build` pada .NET SDK 10 atau lebih baharu yang tepat dan tidak mengubah apa-apa |
 | Release | [`release.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/release.yml) | Repositori ini sahaja | manual | Mencipta tag versi, halaman keluaran dan tag major selepas semakan |
 | Menerbitkan milestone yang diterima | [`sync-milestones.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/sync-milestones.yml) | Repositori ini sahaja | push ke `main` yang mengubah `docs/milestones/**` atau `docs/sqa/reviews/**`, manual (larian percubaan secara lalai) | Mencipta atau mengemas kini milestone Gitea dan isu bagi setiap milestone yang Accepted dengan semakan Go |
 | Validate workflows | [`validate-workflows.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/validate-workflows.yml) | Repositori ini sahaja | pull request, push ke `main`, manual | Menghurai setiap aliran kerja sebagai YAML dan menjalankan ujian luar talian |
 ### Menyegerakkan metadata GitHub
@@ -187,96 +184,6 @@ deactivate Workflow
@enduml
 ```
 ### Semakan kualiti C++
 Aliran kerja boleh guna semula untuk C dan C++, dipanggil dengan `uses: TirSystem/github-action/.gitea/workflows/quality-checks-cpp.yml@v1` (ADR-0008). Repositori mesti mempunyai `.clang-format`; `.clang-tidy` dan pangkalan data kompilasi adalah pilihan.
 #### Aliran kerja
 ```plantuml
@startuml
 title Shared quality checks for C and C++ (reusable workflow)
 autonumber
 actor "Calling repository\nuses: ...quality-checks-cpp.yml@v1" as Caller
 participant "Gitea Actions\nquality-checks-cpp" as Workflow
 participant "PyPI" as PyPI
 Caller -> Workflow: workflow_call with working-directory, std,\ncompile-commands-dir and tool versions
 activate Workflow
 Workflow -> Workflow: Check out the caller and the shared script
 Workflow -> Workflow: Validate the inputs
 alt an input is invalid or a version is not exact
  Workflow --> Caller: Fail with [configuration]
 end
 Workflow -> PyPI: Install clang-format and clang-tidy at the exact versions
 PyPI --> Workflow: Tools installed
 alt no C or C++ file is tracked
  Workflow --> Caller: Notice: nothing was checked, pass
 else no .clang-format, or compile-commands-dir\nwithout compile_commands.json
  Workflow --> Caller: Fail with [configuration]
 else
  Workflow -> Workflow: clang-format --dry-run -Werror on all files
  Workflow -> Workflow: clang-tidy on the C++ files (-std=std)\nand on the C files (or with the compile database)
  alt any tool failed
    Workflow --> Caller: Fail with tool, file and line in the log
  else
    Workflow --> Caller: All selected checks passed
  end
 end
 deactivate Workflow
@enduml
 ```
 ### Semakan kualiti C#
 Aliran kerja boleh guna semula untuk C#, dipanggil dengan `uses: TirSystem/github-action/.gitea/workflows/quality-checks-csharp.yml@v1` (ADR-0008). Ia memasang .NET SDK tepat yang diberikan oleh `dotnet-sdk-version` (10 atau lebih baharu) dan memerlukan rangkaian untuk pemulihan pakej.
 #### Aliran kerja
 ```plantuml
@startuml
 title Shared quality checks for C# (reusable workflow)
 autonumber
 actor "Calling repository\nuses: ...quality-checks-csharp.yml@v1" as Caller
 participant "Gitea Actions\nquality-checks-csharp" as Workflow
 participant "dot.net\n(dotnet-install.sh)" as DotNet
 Caller -> Workflow: workflow_call with working-directory,\nproject and dotnet-sdk-version
 activate Workflow
 Workflow -> Workflow: Check out the caller and the shared script
 Workflow -> Workflow: Validate the inputs
 alt an input is invalid or the SDK is not an exact\nstable version 10 or later
  Workflow --> Caller: Fail with [configuration]
 end
 Workflow -> DotNet: Install the exact .NET SDK version
 DotNet --> Workflow: SDK installed
 alt no C# file is tracked
  Workflow --> Caller: Notice: nothing was checked, pass
 else no solution or project, or several without the project input
  Workflow --> Caller: Fail with [configuration] that names them
 else
  Workflow -> Workflow: dotnet format --verify-no-changes
  Workflow -> Workflow: dotnet build -warnaserror\n(package restore needs the network)
  alt any tool failed
    Workflow --> Caller: Fail with tool, file and line in the log
  else
    Workflow --> Caller: All selected checks passed
  end
 end
 deactivate Workflow
@enduml
 ```
 ### Keluaran
 Dimulakan secara manual oleh penyelenggara; dengan `dry_run` `true` (lalai) ia hanya menyemak (lihat [proses keluaran](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/guides/release-process.md)).
@@ -326,54 +233,6 @@ deactivate Workflow
@enduml
 ```
 ### Menerbitkan milestone yang diterima
 Kebenaran tetap untuk menerbitkan: pada push ke `main` yang mengubah milestone atau semakannya, setiap milestone yang baris terkini Version History-nya Accepted dan semakan terkininya Go dicipta atau dikemas kini di Gitea dengan tugasnya sebagai isu. Tiada apa-apa ditutup atau dipadam. Larian manual ialah larian percubaan kecuali `dry_run` dimatikan. Ia menggunakan secret `TOKEN_FOR_GITEA` dan peraturan `--accepted-only` framework yang dipasang (v0.5.0 atau lebih baharu).
 #### Aliran kerja
 ```plantuml
@startuml
 title Publish accepted milestones (this repository)
 autonumber
 actor "Push to main that changes\ndocs/milestones/** or docs/sqa/reviews/**,\nor manual trigger" as Trigger
 participant "Gitea Actions\nsync-milestones" as Workflow
 participant "framework/scripts/\nsync-project.sh" as Script
 participant "Gitea REST API" as Gitea
 Trigger -> Workflow: Start workflow
 activate Workflow
 Workflow -> Workflow: Check out the project and the framework\nsubmodules over HTTPS with TOKEN_FOR_GITEA
 Workflow -> Script: --accepted-only (dry run)\nor --accepted-only --apply
 activate Script
 loop for each docs/milestones/mil-*.md
  alt latest Version History row is not Accepted,\nor the latest review record is not a Go
    Script -> Script: Skip with the reason on stderr
  else
    alt dry run
      Script -> Script: Print the plan, no network call
    else
      Script -> Gitea: Create or update the Milestone\nand one Issue per task row
      Gitea --> Script: Milestone and issue numbers
    end
  end
 end
 note right of Script
 Nothing is closed or deleted.
 Each real run edits the issues
 of every accepted milestone.
 end note
 Script --> Workflow: Done, or "nothing to publish"
 deactivate Script
 Workflow --> Trigger: Workflow result
 deactivate Workflow
@enduml
 ```
 ### Mengesahkan aliran kerja
 Pengesahan repositori sendiri: ujian luar talian yang menjadi syarat bagi setiap pull request.
Author	SHA1	Message	Date
Tirsvad	ccb1b88b1d	Resolve the pending commit link in MIL-007 TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Skipped	2026-10-11 12:31:25 +08:00
Tirsvad	7bcc67a065	Use current tool versions only for MIL-007: .NET SDK 10 or later	2026-10-11 12:31:24 +08:00