Merge pull request 'MIL-009: remove the scoped publish-wiki workflow and the marker; ADR-0004 superseded' (#151 ) from mil-009-remove-scoped into main

Resolve pending commit links
Remove the scoped publish-wiki workflow and the marker path (2.0.0)
2026-10-14 06:15:32 +02:00 · 2026-10-14 11:45:08 +08:00 · 2026-10-14 11:45:03 +08:00 · 2026-10-14 11:45:01 +08:00 · 2026-10-13 18:01:46 +02:00 · 2026-10-14 00:00:39 +08:00
34 changed files with 481 additions and 483 deletions
@@ -1,48 +0,0 @@
 name: Publish wiki
 # DEPRECATED (ADR-0009, MIL-008): repositories publish their wiki by calling
 # the reusable workflow publish-wiki-pages.yml. This scoped workflow stays
 # until every repository that has wiki/.publish has migrated; it is then
 # removed in a later major release.
 # Shared through scoped delivery: it runs in every repository of an
 # organization, but writes only where the repository has opted in with
 # wiki/.publish (ADR-0004). TOKEN_FOR_GITEA_WIKI is read from the organization
 # secrets; there is no fallback to the read-only sync token. The script is a
 # file of TirSystem/github-action (tools/publish_wiki.py), fetched with a
 # second checkout so that it is readable, lintable and tested as a file
 # (MIL-004 task 6).
 on:
  push:
    branches: [ main ]
    paths:
      - "wiki/**"
  workflow_dispatch:
 concurrency:
  group: publish-wiki
  cancel-in-progress: false
 jobs:
  publish-wiki:
    permissions:
      contents: read
    runs-on: ubuntu-latest
    timeout-minutes: 10
    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: v1
          path: shared-scripts
      - name: Publish the pages to the wiki
        env:
          GITEA_API_URL: ${{ gitea.api_url }}
          SOURCE_REPOSITORY: ${{ gitea.repository }}
          WIKI_CREDENTIALS: ${{ secrets.TOKEN_FOR_GITEA_WIKI }}
        run: python3 shared-scripts/tools/publish_wiki.py
@@ -20,6 +20,31 @@ Each release lists its changes in these groups, in this order:
 ## [Unreleased]
 ## [2.0.0] - 2026-10-14
 ### Breaking
 - The scoped workflow `publish-wiki.yml` and the `wiki/.publish` marker are
  removed (ADR-0009, MIL-009). A repository publishes its wiki by calling the
  reusable workflow `publish-wiki-pages.yml`; one that still has the marker no
  longer publishes. The seven repositories that used the scoped workflow on
  2026-10-13 have a caller (checked on 2026-10-14). A repository that has
  `wiki/.publish` moves `wiki/` to `docs/wiki/`, copies
  `templates/ci/publish-wiki.yml` of the SQA and QC framework (0.7.0 or later)
  to `.gitea/workflows/publish-wiki.yml` and removes the marker.
 - `tools/publish_wiki.py` requires `WIKI_PRUNE` (`true` or `false`) and no longer
  reads a marker; `WIKI_DIR` defaults to `docs/wiki`.
 ### Changed
 - The README, the onboarding, troubleshooting and upgrading guides and the
  wiki pages (English, Danish, Bahasa Malaysia) no longer describe the scoped
  workflow or the marker.
 - ADR-0004 is `Superseded by ADR-0009`.
 - Callers of `quality-checks.yml`, `quality-checks-cpp.yml`,
  `quality-checks-csharp.yml`, `release.yml` and `publish-wiki-pages.yml` need no
  change; `v1` stays at 1.2.2 and `v2` is the new moving major tag.
 ## [1.2.2] - 2026-10-13
 ### Added
@@ -17,16 +17,15 @@ 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 ten workflows: metadata sync to the GitHub mirror, wiki publishing (scoped, and reusable for repositories that call it), 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 nine workflows: metadata sync to the GitHub mirror, wiki publishing (called by each repository), 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).
 ## 🔧 Workflows
-Ten 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.
+Nine 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`; deprecated, replaced by the reusable workflow below (ADR-0009) | push to `main` that changes `wiki/**`, manual | Publishes the pages in `wiki/` to the repository wiki |
 | Publish wiki pages | [`publish-wiki-pages.yml`](.gitea/workflows/publish-wiki-pages.yml) | Reusable (`workflow_call`) | a call from another repository | Publishes the pages in `docs/wiki/` (or the folder named by `wiki_dir`) to the wiki of the calling repository |
 | 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 |
@@ -102,50 +101,6 @@ deactivate Workflow
@enduml
 ```
 ### 📖 Publish wiki (scoped, deprecated)
 Publishes `wiki/` to the repository wiki, only in a repository that has opted in with `wiki/.publish`. The word `prune` in that file also deletes pages that are not in `wiki/`.
 #### 🔀 Workflow
 ```plantuml
@startuml
 title Publish wiki/ to the repository wiki
 autonumber
 actor "Push to main that changes wiki/**,\nor manual trigger" as Trigger
 participant "Gitea Actions\npublish-wiki" as Workflow
 participant "shared-scripts\n(tools/publish_wiki.py at v1)" as Script
 participant "Gitea wiki API" as Wiki
 Trigger -> Workflow: Start workflow
 activate Workflow
 Workflow -> Script: Check out the repository and the script, run it
 activate Script
 alt wiki/.publish does not exist
  Script --> Workflow: Log that publishing is not enabled and succeed\n(nothing is written)
 else wiki/ has no Markdown pages
  Script --> Workflow: Fail with [configuration]\n(an empty wiki/ never deletes pages)
 else
  Script -> Script: Read the marker (empty, or the word prune)\nand TOKEN_FOR_GITEA_WIKI
  Script -> Wiki: GET repository (preflight)
  Wiki --> Script: Wiki is enabled, token accepted
  Script -> Wiki: GET pages
  Wiki --> Script: Existing pages
  Script -> Wiki: Create new pages, update changed pages
  opt marker says prune
    Script -> Wiki: Delete pages that are not in wiki/
  end
  Script --> Workflow: Log created, updated and deleted counts
 end
 deactivate Script
 Workflow --> Trigger: Workflow result
 deactivate Workflow
@enduml
 ```
 ### ✅ Quality checks
 A reusable workflow for Python and shell, called with `uses: TirSystem/github-action/.gitea/workflows/quality-checks.yml@v1` (see the [guide](guides/quality-checks.md)).
@@ -542,8 +497,7 @@ Rows that say Implemented or Guides written exist today. The rest is planned and
 | Synchronize repository metadata (Gitea to GitHub mirror) | Implemented in `.gitea/scoped_workflows/`, with offline tests and a validation workflow |
 | Configure and validate workflow credentials | Implemented for the sync workflow: preflight checks both tokens before any change ([guide](guides/credentials.md)) |
 | Onboard a repository, manage runners, diagnose failures | Guides written ([onboarding](guides/onboarding.md), [troubleshooting](guides/troubleshooting.md)); scoped delivery to the repositories of all four organizations verified (MIL-002) |
-| Publish a repository wiki from `wiki/` (opt-in, delivered to every organization) | Implemented in `.gitea/scoped_workflows/publish-wiki.yml`, with offline tests; a pilot in a second repository publishes its wiki (MIL-006); being replaced by the reusable workflow below (ADR-0009) |
+| Publish a repository wiki from `docs/wiki/` through a called workflow | Implemented as the reusable workflow `.gitea/workflows/publish-wiki-pages.yml`, with offline tests; called by every repository that publishes a wiki, and this repository's own wiki is in `docs/wiki/` (MIL-008, MIL-009) |
 | Publish a repository wiki from `docs/wiki/` through a called workflow | Implemented as the reusable workflow `.gitea/workflows/publish-wiki-pages.yml`, with offline tests; this repository's own wiki is in `docs/wiki/` and published by it through `publish-own-wiki.yml`; not yet called from another repository (MIL-008) |
 | Shared quality checks (Python and shell) | Implemented as the reusable workflow `.gitea/workflows/quality-checks.yml`, with offline tests and a trial in a second organization; adopted in RepoFoundry ([guide](guides/quality-checks.md)) |
 | Shared quality checks (C and C++, C#) | Implemented as the reusable workflows `.gitea/workflows/quality-checks-cpp.yml` and `.gitea/workflows/quality-checks-csharp.yml` with exact tool versions and offline tests; not yet used in another repository (MIL-007) ([C and C++ guide](guides/quality-checks-cpp.md), [C# guide](guides/quality-checks-csharp.md)) |
 | Versioned release and publishing | Release process, changelog and upgrade guide defined; the release workflow exists and `v1.0.0` is released (MIL-004) ([guide](guides/upgrading.md)) |
@@ -4,13 +4,13 @@
 | Key | Value |
 | --- | --- |
 | ID | ADR-0004 |
-| CrossReference | [MIL-006], [ADR-0003], [ADR-0002] |
+| CrossReference | [MIL-006], [ADR-0003], [ADR-0002], [ADR-0009] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
-| 2026-10-10 | Deprecated | Jens Tirsvad Nielsen | S01 | Initial version | [b22a2cd] |
+| 2026-10-10 | Deprecated | Jens Tirsvad Nielsen | S01 | Reviewed (RC-018): the `prune` variant added to the evaluated options | [b22a2cd] |
-| 2026-10-10 | Accepted | Jens Tirsvad Nielsen | S01 | Reviewed (RC-018): the `prune` variant added to the evaluated options | [b22a2cd] |
+| 2026-10-14 | Superseded by ADR-0009 | Jens Tirsvad Nielsen | AI as stand-in for S01 | The scoped delivery and the `wiki/.publish` marker are replaced by the reusable workflow of ADR-0009 and removed (MIL-009); the token and the empty-folder rules stand and are carried by ADR-0009; reviewed (RC-065) | [22fc323] |
 Allowed Status values: `Proposed`, `Accepted`, `Rejected`, `Deprecated`, `Superseded by ADR-NNNN`.
@@ -108,10 +108,13 @@ The rules that follow from it:
 - [ADR-0003] — its fallback to `TOKEN_FOR_GITEA` no longer applies to the
  shared workflow.
 - [ADR-0002] — the stand-in rule applies to the review of this ADR.
 - [ADR-0009] — the successor: the reusable workflow replaces the scoped delivery and the marker.
 ---
 [MIL-006]: ../milestones/mil-006-shared-wiki-publishing.md
 [ADR-0003]: ./adr-0003-wiki-publish-token.md
 [ADR-0002]: ./adr-0002-s01-approves-as-stand-in.md
 [ADR-0009]: ./adr-0009-wiki-publishing-reusable-workflow.md
 [b22a2cd]: https://git.tirsystem.com/TirSystem/github-action/commit/b22a2cd59235078656c4440b945b787f88fbd345
 [22fc323]: https://git.tirsystem.com/TirSystem/github-action/commit/22fc323b41074ee0029ea2f07445a8e329e15d15
@@ -9,7 +9,8 @@
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
-| 2026-10-13 | Proposed | Jens Tirsvad Nielsen | S01 | Initial version | [01b9c29] |
+| 2026-10-13 | Deprecated | Jens Tirsvad Nielsen | S01 | Initial version | [01b9c29] |
 | 2026-10-13 | Accepted | Jens Tirsvad Nielsen | S01 | Review findings fixed (RC-063): the product owner's language is spelled out, the security consequence is named, and the secret passing is recorded as verified | [8c2c52e] |
 Allowed Status values: `Proposed`, `Accepted`, `Rejected`, `Deprecated`, `Superseded by ADR-NNNN`.
@@ -22,7 +23,8 @@ repository of an organisation, and a marker file `wiki/.publish` is the opt-in.
 That avoids a copy of the workflow, but it runs where nobody asked for it and
 needs a safety gate for that reason; its trigger path (`wiki/**`) and the
 version of the script (`v1`) are fixed centrally. The framework now prescribes
-the wiki in `docs/wiki/` with English and the PO language as a minimum, and
+the wiki in `docs/wiki/` with English and the product owner's language as a
 minimum, and
 repositories need to say where their wiki is.
 Options:
@@ -61,6 +63,9 @@ The rules that follow from it:
  to `docs/wiki/` one repository at a time.
 - Opting in is a file in the repository, reviewed in a pull request, and a
  repository without a caller is never written to.
 - Security: the token is passed explicitly by the caller and is never
  inherited or taken from a fallback, so a repository that does not pass it
  cannot write a wiki.
 - One call convention for every shared workflow of this repository.
 **Negative:**
@@ -74,8 +79,13 @@ The rules that follow from it:
  their migrations.
 - The owner chose a patch release (1.2.2) for this change although a new
  workflow is a minor one under [ADR-0006]; the changelog states the deviation.
- Passing a declared secret through `workflow_call` is not yet verified on this
+- Anyone who can change the caller file of a repository can change the folder
-  Gitea instance; it is checked by the first call, in this repository.
+  and `prune`, and so what the token deletes in that repository's wiki; this is
  the same exposure as the marker had, and it is reviewed through the pull
  request that changes the caller.
 - Passing a declared secret through `workflow_call`, and a local `uses:` call,
  were verified on this Gitea instance by run 316 of this repository on
  2026-10-13.
 ## Affected Artifacts
@@ -91,3 +101,4 @@ The rules that follow from it:
 [ADR-0006]: ./adr-0006-release-process-and-version-pinning.md
 [ADR-0005]: ./adr-0005-quality-check-contract.md
 [01b9c29]: https://git.tirsystem.com/TirSystem/github-action/commit/01b9c2972b4317bcc590540010aea0eaf7f30014
 [8c2c52e]: https://git.tirsystem.com/TirSystem/github-action/commit/8c2c52ebd2a27e4d0edb4008c31c002718d280fb
@@ -10,8 +10,8 @@ each document lives in *this* project and the next version to use.
 | BC | Business Case | docs/business-case.md | 002 |
 | SA | Stakeholder Analysis | docs/stakeholder-analysis.md | 002 |
 | PP | Project Plan | docs/project-plan.md | 002 |
-| MIL | Milestone / Gateway | docs/milestones/*.md | 009 |
+| MIL | Milestone / Gateway | docs/milestones/*.md | 010 |
-| RC | SQA Review Record | docs/sqa/reviews/rc-*.md | 062 |
+| RC | SQA Review Record | docs/sqa/reviews/rc-*.md | 066 |
 | TM | Traceability Matrix | docs/sqa/traceability-matrix.md | 002 |
 | ADR | Architecture Decision Record | docs/adr/adr-NNNN-*.md | 0010 |
 | UCD | Use Case Diagram | docs/use-case-diagram.md | 002 |
@@ -0,0 +1,92 @@
 # MIL-009: Migrate the wiki callers and remove the scoped workflow
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | MIL-009 |
 | CrossReference | [BC-001], [MIL-008], [ADR-0004], [ADR-0006], [ADR-0009] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-13 | Deprecated | Jens Tirsvad Nielsen | S01 | Initial version | [2b53ee6] |
 | 2026-10-14 | Accepted | Jens Tirsvad Nielsen | AI as stand-in for S01 | Plan accepted in chat with the defaults: target date 2026-11-30 confirmed, `027-sandbox` and `028-pomodoro` do not publish, framework release 0.7.0; reviewed (RC-064) | [2f267df] |
 ---
 ## Purpose
 Decide whether the scoped `publish-wiki.yml` can be removed: every repository
 that publishes its wiki through it has moved to `docs/wiki/` and calls the
 reusable workflow `publish-wiki-pages.yml`, and ADR-0004 is superseded by
 ADR-0009. MIL-008 deprecated the scoped workflow and kept it because seven
 repositories still depended on it (checked on 2026-10-13).
 ## Deliverable
 A released framework with the caller template; each of the seven repositories
 publishing its wiki from `docs/wiki/` through a caller, with its marker removed;
 the scoped workflow, its marker code path, its tests and every mention of the
 marker as an opt-in removed; ADR-0004 marked superseded; and the major release
 2.0.0 with the tag `v2`.
 ## Go / No-Go Criteria
 | # | Criterion (objectively checkable) | Go | No-Go |
 | --- | --- | --- | --- |
 | 1 | The framework is released as 0.7.0 with `templates/ci/publish-wiki.yml` and `process/wiki.md`, as a tag | The tag exists and each migrating repository pins it | No tag, or a repository pins an unmerged commit |
 | 2 | Each of the seven repositories publishes from `docs/wiki/` through a caller of `publish-wiki-pages.yml`, and has no `wiki/.publish` | A scan of the instance lists the seven with a caller and no marker | Any marker or missing caller remains |
 | 3 | The wiki of each of the seven equals its `docs/wiki/` after the first run | 0 differences read back through the API for each | A difference, or a failed run |
 | 4 | A scan of every repository of the four organisations finds no `wiki/.publish` and no run of the scoped workflow that wrote | None found | Any found |
 | 5 | The scoped `publish-wiki.yml`, the marker code path of `tools/publish_wiki.py`, their tests and the marker text of the guides, README and wiki pages are removed | Offline tests pass; a search finds no `wiki/.publish` outside the changelog and ADRs | A mention remains, or a test fails |
 | 6 | ADR-0004 is `Superseded by ADR-0009` with a review record, and ADR-0009 links back | Both rows and RC present | Missing |
 | 7 | Release 2.0.0 is published with a Breaking entry, `v2` points to it, and `v1` still points to 1.2.2 | Tags read back through the API | `v1` moved, or no Breaking entry |
 ## Dependencies
 | Depends on | Reason |
 | --- | --- |
 | MIL-008 | Provides the reusable workflow, the deprecation and the list of repositories |
 | `TirSystem/sqa-qc-framework` release | The caller template and `process/wiki.md` must be a tag before a repository pins them |
 ## Traceability
 | Business Case objective / KPI / user story | Reference |
 | --- | --- |
 | O2, O3 | [BC-001] |
 ## Ownership
 | Role | Stakeholder ID (SA) |
 | --- | --- |
 | Owner | S05 |
 | Approving reviewer | S01 |
 ## Target Date
 2026-11-30 — confirmed on 2026-10-14 by S01 in chat; the Business Case sets no deadline.
 ## Tasks
 | # | Task | Summary | Needs its own Use Case/User Story? | Reference |
 | --- | --- | --- | --- | --- |
 | 1 | Release the framework | `TirSystem/sqa-qc-framework` has the caller template and `process/wiki.md` merged (pull request 45). Add the changelog entry, tag the release and record the tag. Needed before any repository pins the template. | No | |
 | 2 | Migrate the three TirSystem projects | `sqa-and-qc`, `sqa-qc-framework` and `sqa-qc-checklists`: move `wiki/` to `docs/wiki/`, copy the caller from `templates/ci/publish-wiki.yml`, remove `wiki/.publish`, fix the paths in their generators and documents, move the framework pin to the released tag, one pull request each. Confirm the organisation secret `TOKEN_FOR_GITEA_WIKI` is present. | No | |
 | 3 | Migrate `repo-foundry` | Same steps for `TirSystem-BashScript/repo-foundry` (21 wiki files); the organisation `TirSystem-BashScript` needs its own `TOKEN_FOR_GITEA_WIKI` secret (S03). | No | |
 | 4 | Migrate the three Udemy repositories | Same steps for `021-snake-game`, `024-snake` and `025-weather` of `Tirsvad-Udemy-100-days-of-code` (5 wiki files each). `027-sandbox` and `028-pomodoro`, which have `docs/wiki/` and no marker, do not publish (decided by S01 on 2026-10-14). | No | |
 | 5 | Verify the migration | After each first run read the wiki back and compare it with `docs/wiki/`; then scan the four organisations for `wiki/.publish` and for repositories still publishing through the scoped workflow. Record the results in this milestone. | No | |
 | 6 | Remove the scoped workflow | Delete `.gitea/scoped_workflows/publish-wiki.yml`, the marker path of `tools/publish_wiki.py` (the `WIKI_PRUNE` input becomes required), the tests that cover it and the marker text in the guides, the README and the three wiki languages. Keep the drift test for the remaining scoped workflow. | No | |
 | 7 | Supersede ADR-0004 | Mark ADR-0004 `Superseded by ADR-0009` for the delivery and marker parts (new version row, review record), and make ADR-0009 link back. | No | |
 | 8 | Release 2.0.0 | Breaking entry (a removed workflow and marker); upgrade guide for callers; release through the release workflow; `v2` is created and `v1` stays at 1.2.2. Move the examples in the guides to `@v2` where the guide describes the new major. | No | |
 ---
 ---
 [BC-001]: ../business-case.md
 [MIL-008]: ./mil-008-wiki-reusable-workflow.md
 [ADR-0004]: ../adr/adr-0004-shared-wiki-publishing-opt-in.md
 [ADR-0009]: ../adr/adr-0009-wiki-publishing-reusable-workflow.md
 [ADR-0006]: ../adr/adr-0006-release-process-and-version-pinning.md
 [2b53ee6]: https://git.tirsystem.com/TirSystem/github-action/commit/2b53ee6d21babdefc30556b92c3300c6cd956898
 [2f267df]: https://git.tirsystem.com/TirSystem/github-action/commit/2f267df2a270087cb7dc482af4ce4f4341e97b03
@@ -4,25 +4,25 @@
 | Key | Value |
 | --- | --- |
 | ID | PP-001 |
-| CrossReference | [BC-001], [SA-001], [ADR-0002], [US-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004], [MIL-005], [MIL-006], [MIL-007] |
+| CrossReference | [BC-001], [SA-001], [ADR-0002], [US-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004], [MIL-005], [MIL-006], [MIL-007], [MIL-008], [MIL-009] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
-| 2026-10-10 | Deprecated | Jens Tirsvad Nielsen | S01 | Dates confirmed by S01 (stand-in for S05); the confirmation item is removed from Open Issues | [ea06eaa] |
+| 2026-10-13 | Deprecated | Jens Tirsvad Nielsen | S01 | Added MIL-009 (migrate the wiki callers, remove the scoped workflow); review RC-064 awaits S01 | [86e69ce] |
-| 2026-10-11 | Accepted | Jens Tirsvad Nielsen | S01 | Added MIL-007 (quality checks for C++ and C#); reviewed (RC-053) | [e3ad1fa] |
+| 2026-10-14 | Accepted | Jens Tirsvad Nielsen | AI as stand-in for S01 | MIL-009 plan accepted in chat with the defaults; target date 2026-11-30 confirmed (RC-064) | [2f267df] |
 ---
 ## Purpose
-This plan schedules seven milestones that move the repository from one
+This plan schedules nine milestones that move the repository from one
 workflow with known defects to a documented, versioned collection of shared
 workflows. The Business Case sets no deadline, so the dates are the plan's own; they were confirmed on 2026-10-10 by S01, standing in for S05 (ADR-0002).
 ## Planning Assumptions
- Week 1 starts 2026-10-05; phases are two weeks long; the last decision is 2026-12-26; MIL-007 follows in January 2027 (2027-01-04 to 2027-01-16, confirmed on 2026-10-11 by S01).
+- Week 1 starts 2026-10-05; phases are two weeks long; the last decision is 2026-12-26; MIL-007 follows in January 2027 (2027-01-04 to 2027-01-16, confirmed on 2026-10-11 by S01). MIL-008 amends the shared wiki publishing of MIL-006 and runs in parallel with the October and November windows: its work started on 2026-10-13 and its decision date is its own Target Date, 2026-11-15. MIL-009 follows MIL-008 and runs from 2026-11-16 to its proposed Target Date, 2026-11-30, confirmed by S01 in chat on 2026-10-14.
 - Work on a milestone starts only after its `MIL-*` document is `Accepted`.
 - Dates were confirmed on 2026-10-10 by S01, standing in for S05 (ADR-0002).
@@ -37,6 +37,8 @@ workflows. The Business Case sets no deadline, so the dates are the plan's own;
 | Wiki and translations | [MIL-005] | 2026-11-30 to 2026-12-12 | 2026-12-12 | S05 | None yet | Wiki pages in English, Danish and Bahasa Malaysia, kept current by every pull request | [Milestone MIL-005] |
 | Shared wiki publishing | [MIL-006] | 2026-12-14 to 2026-12-26 | 2026-12-26 | S05 | None yet | Scoped publish-wiki workflow with opt-in, piloted in one other repository | [Milestone MIL-006] |
 | Quality checks for C++ and C# | [MIL-007] | 2027-01-04 to 2027-01-16 | 2027-01-16 | S05 | US-001.09, US-001.10 (to extend) | Reusable quality-check workflows for C++ and C#, released | [Milestone MIL-007] |
 | Wiki publishing as a reusable workflow | [MIL-008] | 2026-10-13 to 2026-11-15 | 2026-11-15 | S05 | None yet | Reusable publish-wiki-pages workflow, wiki in docs/wiki, scoped workflow deprecated, released as 1.2.2 | [Milestone MIL-008] |
 | Migrate the wiki callers and remove the scoped workflow | [MIL-009] | 2026-11-16 to 2026-11-30 | 2026-11-30 | S05 | None yet | Seven repositories publish through a caller, scoped workflow removed, ADR-0004 superseded, released as 2.0.0 | Not created yet (the sync creates it when MIL-009 is Accepted) |
 ```plantuml
@startgantt
@@ -55,6 +57,10 @@ Project starts 2026-10-05
 [MIL-006 Go/No-Go] happens 2026-12-26
 [MIL-007 C++ and C#] starts 2027-01-04 and ends 2027-01-16
 [MIL-007 Go/No-Go] happens 2027-01-16
 [MIL-008 Reusable wiki workflow] starts 2026-10-13 and ends 2026-11-15
 [MIL-008 Go/No-Go] happens 2026-11-15
 [MIL-009 Migrate and remove] starts 2026-11-16 and ends 2026-11-30
 [MIL-009 Go/No-Go] happens 2026-11-30
@endgantt
 ```
@@ -69,6 +75,8 @@ Project starts 2026-10-05
 | Wiki pages in English, Danish and Bahasa Malaysia | [MIL-005] |
 | The wiki publisher shared with other repositories through scoped delivery | [MIL-006] |
 | Gitea Actions workflows for software engineers (quality checks for C++ and C#) | [MIL-007] |
 | The wiki publisher as a workflow that repositories call, from docs/wiki | [MIL-008] |
 | Moving every publishing repository to the called workflow and removing the scoped one | [MIL-009] |
 ## Dependencies
@@ -76,6 +84,7 @@ Project starts 2026-10-05
 MIL-001 → MIL-002 → MIL-003 → MIL-004
            MIL-002 → MIL-005 → MIL-006
   MIL-003 + MIL-004 → MIL-007
                      MIL-006 → MIL-008 → MIL-009
 ```
 A No-Go moves every later window by the rework time of the failed milestone.
@@ -86,6 +95,8 @@ A No-Go moves every later window by the rework time of the failed milestone.
 | --- | --- | --- |
 | The runner cannot provide the C++ or C# tools (MIL-007) | The workflows need a custom runner image or a longer install | MIL-007 task 2 verifies it first; the ADR of task 3 says what a build-dependent check needs from the caller. |
 | Reusable workflow support is missing on the instance | MIL-003 and MIL-004 change shape | Verify first in each milestone (MIL-002 task 2, MIL-003 task 1); fall back to copied templates. |
 | Eight repositories still publish through the scoped workflow that MIL-008 deprecates (MIL-008 task 5) | Removing it would stop their wikis | It is deprecated and kept; a follow-up milestone migrates them and removes it in a major release (RC-061). |
 | An organisation has no `TOKEN_FOR_GITEA_WIKI` secret, or a repository fails its first run (MIL-009 tasks 3 and 4) | The wiki of that repository stops updating | MIL-009 task 5 reads each wiki back after the first run; the scoped workflow is removed only after every repository passes. |
 | Security review by S05 is a bottleneck | Milestone decisions slip | Keep milestones small and plan review time before each decision date. |
 ## Open Issues
@@ -258,6 +269,8 @@ no tests, no release process.
 [MIL-005]: ./milestones/mil-005-wiki-and-translations.md
 [MIL-006]: ./milestones/mil-006-shared-wiki-publishing.md
 [MIL-007]: ./milestones/mil-007-cpp-csharp-quality-checks.md
 [MIL-008]: ./milestones/mil-008-wiki-reusable-workflow.md
 [MIL-009]: ./milestones/mil-009-migrate-wiki-callers-and-remove-scoped-workflow.md
 [Milestone MIL-001]: https://git.tirsystem.com/TirSystem/github-action/milestone/18
 [Milestone MIL-002]: https://git.tirsystem.com/TirSystem/github-action/milestone/19
 [Milestone MIL-003]: https://git.tirsystem.com/TirSystem/github-action/milestone/20
@@ -265,6 +278,7 @@ no tests, no release process.
 [Milestone MIL-005]: https://git.tirsystem.com/TirSystem/github-action/milestone/93
 [Milestone MIL-006]: https://git.tirsystem.com/TirSystem/github-action/milestone/94
 [Milestone MIL-007]: https://git.tirsystem.com/TirSystem/github-action/milestone/95
-[ea06eaa]: https://git.tirsystem.com/TirSystem/github-action/commit/ea06eaaa698247d20e4a8e2694d7acbb1de58b63
+[Milestone MIL-008]: https://git.tirsystem.com/TirSystem/github-action/milestone/152
 [b74ee0e]: https://git.tirsystem.com/TirSystem/github-action/commit/b74ee0e5cfd04f25ba5f2c1addc80699147c479a
-[e3ad1fa]: https://git.tirsystem.com/TirSystem/github-action/commit/e3ad1fa7e7eef57a6793a479edb41ac6fd2db688
+[86e69ce]: https://git.tirsystem.com/TirSystem/github-action/commit/86e69ce85df72ea3caed40253e08231c73187fde
 [2f267df]: https://git.tirsystem.com/TirSystem/github-action/commit/2f267df2a270087cb7dc482af4ce4f4341e97b03
@@ -0,0 +1,54 @@
 # Review Record: PP-001 Project Plan (MIL-008)
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | RC-062 |
 | CrossReference | [PP-001], [BC-001], [MIL-008] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-13 | Accepted | Jens Tirsvad Nielsen | S01 | Initial version | [9aeb74e] |
 ---
 ## Artifact Under Review
 - Instance reviewed: [PP-001]
 - Checklist used: none: the Project Plan has no QC checklist. Validated against the Business Case [BC-001] and the Go / No-Go criteria of each listed milestone, as `PP.md` prescribes.
 - Scope: delta re-review for the added MIL-008 row, Gantt entries, Scope Coverage, Dependencies, one Plan Risk and the counts; the earlier record is RC-053
 - Language and domain: n/a (technical type)
 - Mode: supervised (the AI prepared the record; S01, the user, gave the Go in chat on 2026-10-13)
 ## Checklist Results
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | Every milestone in the plan has a `MIL-*` document and the plan's dates equal that document's target date | Pass | MIL-001 to MIL-008 exist; the MIL-008 decision date 2026-11-15 equals its Target Date. |
 | 2 | Every Business Case scope item is covered by a gateway | Pass | The wiki publisher shared with other repositories is covered by MIL-006 and MIL-008 (O2, O3). |
 | 3 | The schedule respects the Business Case constraints | Pass | The Business Case sets no deadline; the MIL-008 window overlaps the October and November windows and says so under Planning Assumptions. |
 | 4 | Dependencies between milestones are stated | Pass | MIL-006 to MIL-008 is in the Dependencies diagram and in MIL-008's own document. |
 | 5 | Every gateway has an owner who is a stakeholder ID | Pass | MIL-008 is owned by S05. |
 | 6 | Plan content is internally consistent | Pass | "Eight milestones", the Planning Assumptions, the Gantt entries, the Gateway Schedule and the Scope Coverage agree. |
 | 7 | Open Issues are current | Pass | Unchanged items remain open; a plan risk was added for the repositories that still use the scoped workflow. |
 ## Overall Verdict
 Go - all seven criteria pass; no findings. S01 gave the Go in chat on 2026-10-13, after the change was merged as pull request 137 with the plan row `Proposed`; this record and the plan row are set to `Accepted` in the follow-up.
 ## Action Items
 | Action | Owner | Due |
 | --- | --- | --- |
 | Set PP-001 and this record to `Accepted` (done in the follow-up that follows pull request 137) | S05 | 2026-10-13 |
 | Review ADR-0009 (still without a review record) | S01 | after the plan |
 ---
 ---
 [PP-001]: ../../project-plan.md
 [BC-001]: ../../business-case.md
 [MIL-008]: ../../milestones/mil-008-wiki-reusable-workflow.md
 [9aeb74e]: https://git.tirsystem.com/TirSystem/github-action/commit/9aeb74e8b09bb7882847e9bd5d569dbc9856fc03
@@ -0,0 +1,56 @@
 # Review Record: ADR-0009 Wiki publishing as a reusable workflow
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | RC-063 |
 | CrossReference | [ADR-0009], [QC-ADR-001] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-13 | Accepted | Jens Tirsvad Nielsen | S01 | Initial version | [8c2c52e] |
 ---
 ## Artifact Under Review
 - Instance reviewed: [ADR-0009]
 - Checklist used: [QC-ADR-001]
 - Scope: full review
 - Language and domain: n/a (technical type)
 - Mode: supervised (the AI prepared the record; S01, the user, gave the Go in chat on 2026-10-13)
 ## Checklist Results
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | The ID (`ADR-NNNN`, 4-digit) matches the filename number and is unique and sequential | Pass | ADR-0009 in `adr-0009-wiki-publishing-reusable-workflow.md`; follows ADR-0008. |
 | 2 | Context states the problem, the forces (cost, risk, constraints) and the options evaluated | Pass | Names the scoped delivery, its gate, the fixed trigger path and version, and the new folder rule. |
 | 3 | At least two options were considered, or the absence of alternatives is justified | Pass | Two options: keep the scoped workflow and read both folders, or a reusable workflow. |
 | 4 | Decision is stated in one or two unhedged sentences and matches one of the evaluated options | Pass | Two sentences; matches option 2. The rules below it add detail only. |
 | 5 | Consequences list both Positive and Negative outcomes | Pass | Finding fixed during this review: the consequence "passing a declared secret is not yet verified" was out of date, because run 316 verified it on 2026-10-13. It now says so. Four positive and four negative outcomes. |
 | 6 | Quality-attribute impacts (performance, security, portability, etc.) are named where the decision affects them | Pass | Finding fixed during this review: the security impact was implicit. A positive bullet (explicit secret, no fallback) and a negative bullet (whoever changes the caller changes the folder and `prune`) were added. |
 | 7 | Affected Artifacts are listed as links, and each is also in CrossReference | Pass | MIL-008 and ADR-0004 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 findings fix is a new row; the first row is kept unchanged. |
 | 9 | A superseded or deprecated ADR names its successor, and the successor links back | N-A | ADR-0004 is superseded only in part and stays in force until the scoped workflow is removed; see the action item. |
 | 10 | Written in business or technical language of the domain, with no unexplained abbreviations | Pass | Finding fixed during this review: "PO language" is now "the product owner's language". |
 | 11 | Status is one of `Proposed`, `Accepted`, `Rejected`, `Deprecated` or `Superseded by ADR-NNNN`, and every Version History row uses only these | Pass | `Proposed` only. |
 ## Overall Verdict
 Go - all applicable criteria pass; the three findings (criteria 5, 6 and 10) were fixed during the review. S01 gave the Go in chat on 2026-10-13; there is no independent reader.
 ## Action Items
 | Action | Owner | Due |
 | --- | --- | --- |
 | When the scoped workflow is removed, mark ADR-0004 superseded by ADR-0009 for the delivery and marker parts (new version row and review record) | S01 | the follow-up milestone |
 ---
 ---
 [ADR-0009]: ../../adr/adr-0009-wiki-publishing-reusable-workflow.md
 [QC-ADR-001]: ../../../framework/qc/artifacts/qc-adr.md
 [8c2c52e]: https://git.tirsystem.com/TirSystem/github-action/commit/8c2c52ebd2a27e4d0edb4008c31c002718d280fb
@@ -0,0 +1,63 @@
 # Review Record: MIL-009 and PP-001 (MIL-009)
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | RC-064 |
 | CrossReference | [MIL-009], [PP-001], [BC-001], [QC-MIL-001] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-14 | Accepted | Jens Tirsvad Nielsen | AI as stand-in for S01 | Initial version; accepted | [86e69ce] |
 ---
 ## Artifact Under Review
 - Instance reviewed: [MIL-009]; delta of [PP-001] for the added milestone
 - Checklist used: [QC-MIL-001] for the milestone; for the plan, the criteria of `PP.md` (no QC checklist exists for PP-001)
 - Scope: full review of MIL-009; delta re-review of PP-001, earlier record RC-062
 - Language and domain: n/a (technical type)
 - Mode: autonomous, not independent (the reviewer is `AI as stand-in for S01`; the user accepted the plan in chat on 2026-10-14 with the defaults)
 ## Checklist Results
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | A concrete deliverable is defined for every gate | Pass | MIL-009 lists the released framework, seven callers, the removals, the superseded ADR and 2.0.0. |
 | 2 | Explicit Go/No-Go criteria are stated for each gate | Pass | Seven criteria with checkable Go and No-Go (tag, callers, read-backs, scan, removal, ADR rows, tags). |
 | 3 | Dependencies on other milestones are explicitly mapped | Pass | MIL-008 and the framework release; in the plan's Dependencies diagram (`MIL-008 -> MIL-009`). |
 | 4 | Each milestone is traceable to a Business Case objective or KPI | Pass | O2, O3 of [BC-001]. |
 | 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 | 2026-11-30 is proposed and equals the plan's decision date; the Business Case sets no deadline. S01 has not confirmed it, as MIL-009 and the plan say; this is an action item. |
 ## Plan delta (PP-001)
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | Every milestone has a `MIL-*` document and the plan's dates equal that document's target date | Pass | MIL-001 to MIL-009 exist; the MIL-009 decision date equals its Target Date. |
 | 2 | Every Business Case scope item is covered by a gateway | Pass | Scope Coverage names MIL-009 for the removal of the scoped publisher. |
 | 3 | The schedule respects the Business Case constraints | Pass | No deadline in the Business Case; the window follows MIL-008. |
 | 4 | Dependencies between milestones are stated | Pass | `MIL-006 -> MIL-008 -> MIL-009`. |
 | 5 | Every gateway has an owner who is a stakeholder ID | Pass | S05. |
 | 6 | Plan content is internally consistent | Pass | "Nine milestones", the assumptions, the Gantt, the schedule and the coverage agree. |
 | 7 | Open Issues are current | Pass | A plan risk was added for missing organisation secrets and failed first runs. |
 ## Overall Verdict
 Go - all criteria pass. The user switched to autonomous mode and accepted the plan in chat on 2026-10-14 with the defaults (target date 2026-11-30, no publishing for `027-sandbox` and `028-pomodoro`, framework release 0.7.0); the AI records the acceptance as stand-in for S01. There is no independent reader and the decision stays open to challenge in the run summary.
 ## Action Items
 | Action | Owner | Due |
 | --- | --- | --- |
 | Check that `TirSystem-BashScript` has its own `TOKEN_FOR_GITEA_WIKI` (S03); stop and report if it does not | S03 | MIL-009 task 3 |
 ---
 [MIL-009]: ../../milestones/mil-009-migrate-wiki-callers-and-remove-scoped-workflow.md
 [PP-001]: ../../project-plan.md
 [BC-001]: ../../business-case.md
 [QC-MIL-001]: ../../../framework/qc/artifacts/qc-milestones-gateways.md
 [86e69ce]: https://git.tirsystem.com/TirSystem/github-action/commit/86e69ce85df72ea3caed40253e08231c73187fde
@@ -0,0 +1,56 @@
 # Review Record: ADR-0004 superseded by ADR-0009
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | RC-065 |
 | CrossReference | [ADR-0004], [ADR-0009], [QC-ADR-001], [MIL-009] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-14 | Accepted | Jens Tirsvad Nielsen | AI as stand-in for S01 | Initial version | [22fc323] |
 ---
 ## Artifact Under Review
 - Instance reviewed: [ADR-0004] after the status change to `Superseded by ADR-0009` on 2026-10-14
 - Checklist used: [QC-ADR-001]
 - Scope: delta re-review of the criteria the status change touches (7, 8, 9, 11); the earlier record is RC-018
 - Language and domain: n/a (technical type)
 - Mode: autonomous, not independent (the reviewer is `AI as stand-in for S01`; the user accepted the plan [MIL-009] in chat on 2026-10-14)
 ## Checklist Results
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | The ID matches the filename number and is unique and sequential | Pass | Unchanged. |
 | 2 | Context states the problem, the forces and the options evaluated | Pass | Unchanged. |
 | 3 | At least two options were considered | Pass | Unchanged. |
 | 4 | Decision is stated in one or two unhedged sentences and matches an evaluated option | Pass | Unchanged. |
 | 5 | Consequences list both Positive and Negative outcomes | Pass | Unchanged. |
 | 6 | Quality-attribute impacts are named where the decision affects them | Pass | Unchanged. |
 | 7 | Affected Artifacts are listed as links, and each is also in CrossReference | Pass | ADR-0009 is added to both. |
 | 8 | Status changes are recorded as new Version History rows with a Change summary and Commit link; retained rows are never rewritten | Pass | The change is a new row; the earlier `Accepted` row became `Deprecated` and its content is unchanged. |
 | 9 | A superseded or deprecated ADR names its successor, and the successor links back | Pass | The status names ADR-0009; ADR-0009 lists ADR-0004 under Affected Artifacts and in CrossReference. This closes the N-A of RC-018. |
 | 10 | Written in the language of the domain, with no unexplained abbreviations | Pass | Unchanged. |
 | 11 | Status is one of the allowed values and every row uses only these | Pass | `Deprecated` and `Superseded by ADR-0009`. |
 ## Overall Verdict
 Go - all criteria pass. The scoped delivery and the marker are replaced and removed (MIL-009 tasks 2 to 6); the token and empty-folder rules of this ADR stand and are carried by ADR-0009. The AI records the acceptance as stand-in for S01; there is no independent reader, and the decision stays open to challenge in the run summary.
 ## Action Items
 | Action | Owner | Due |
 | --- | --- | --- |
 | None open | - | - |
 ---
 [ADR-0004]: ../../adr/adr-0004-shared-wiki-publishing-opt-in.md
 [ADR-0009]: ../../adr/adr-0009-wiki-publishing-reusable-workflow.md
 [QC-ADR-001]: ../../../framework/qc/artifacts/qc-adr.md
 [MIL-009]: ../../milestones/mil-009-migrate-wiki-callers-and-remove-scoped-workflow.md
 [22fc323]: https://git.tirsystem.com/TirSystem/github-action/commit/22fc323b41074ee0029ea2f07445a8e329e15d15
@@ -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], [MIL-008], [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], [RC-058], [RC-059], [RC-060], [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], [MIL-008], [MIL-009], [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], [RC-058], [RC-059], [RC-060], [RC-061], [RC-062], [RC-063], [RC-064], [RC-065], [ADR-0007], [ADR-0008], [ADR-0009], [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-13 | Proposed | Jens Tirsvad Nielsen | S01 | Added RC-059 (MIL-007 task 7 results) | [2481c26] |
+| 2026-10-14 | Proposed | Jens Tirsvad Nielsen | S01 | MIL-009, PP-001 and RC-064 accepted | [2f267df] |
-| 2026-10-13 | Proposed | Jens Tirsvad Nielsen | S01 | Added MIL-008, RC-060 and RC-061 | [01b9c29] |
+| 2026-10-14 | Proposed | Jens Tirsvad Nielsen | S01 | Added RC-065 (ADR-0004 superseded by ADR-0009) | [22fc323] |
 ---
@@ -26,7 +26,7 @@ updated whenever an artifact instance is created or reviewed.
 | --- | --- | --- | --- | --- |
 | [SA-001] | SA | - | [BC-001], [UCD-001] | [RC-004] |
 | [BC-001] | BC | [SA-001] | [PP-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004], [MIL-005], [MIL-006] | [RC-001], [RC-008] |
-| [PP-001] | PP | [BC-001], [SA-001] | [MIL-001], [MIL-002], [MIL-003], [MIL-004], [MIL-005], [MIL-006], [MIL-007], [US-001] | [RC-002], [RC-009], [RC-015], [RC-017], [RC-025], [RC-032], [RC-053] |
+| [PP-001] | PP | [BC-001], [SA-001] | [MIL-001], [MIL-002], [MIL-003], [MIL-004], [MIL-005], [MIL-006], [MIL-007], [MIL-008], [MIL-009], [US-001] | [RC-002], [RC-009], [RC-015], [RC-017], [RC-025], [RC-032], [RC-053], [RC-062], [RC-064] |
 | [MIL-001] | MIL | [BC-001], [PP-001] | [MIL-002] | [RC-003], [RC-026] |
 | [MIL-002] | MIL | [BC-001], [PP-001], [MIL-001] | [MIL-003], [MIL-005] | [RC-005], [RC-027] |
 | [MIL-003] | MIL | [BC-001], [PP-001], [MIL-002] | [MIL-004] | [RC-006], [RC-028], [RC-033], [RC-039] |
@@ -40,7 +40,8 @@ updated whenever an artifact instance is created or reviewed.
 | [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], [RC-058] |
 | [MIL-007] | MIL | [BC-001], [PP-001], [MIL-003], [MIL-004], [ADR-0008] | - | [RC-052], [RC-055], [RC-059] |
-| [MIL-008] | MIL | [BC-001], [MIL-006], [ADR-0004] | - | [RC-060], [RC-061] |
+| [MIL-008] | MIL | [BC-001], [PP-001], [MIL-006], [ADR-0004] | [MIL-009] | [RC-060], [RC-061] |
 | [MIL-009] | MIL | [BC-001], [PP-001], [MIL-008], [ADR-0004], [ADR-0006], [ADR-0009] | - | [RC-064] |
 | [RC-007] | RC | [MIL-004] | - | - |
 | [RC-008] | RC | [BC-001] | - | - |
 | [RC-009] | RC | [PP-001] | - | - |
@@ -48,7 +49,7 @@ updated whenever an artifact instance is created or reviewed.
 | [ADR-0001] | ADR | [BC-001], [MIL-005] | [ADR-0003] | [RC-012] |
 | [ADR-0002] | ADR | [SA-001], [RC-001] | - | [RC-013] |
 | [ADR-0003] | ADR | [MIL-005], [ADR-0001], [RC-011] | [ADR-0004] | [RC-014] |
-| [ADR-0004] | ADR | [MIL-006], [ADR-0003], [ADR-0002] | - | [RC-018] |
+| [ADR-0004] | ADR | [MIL-006], [ADR-0003], [ADR-0002] | [ADR-0009] | [RC-018], [RC-065] |
 | [RC-011] | RC | [MIL-005] | - | - |
 | [RC-012] | RC | [ADR-0001] | - | - |
 | [RC-013] | RC | [ADR-0002] | - | - |
@@ -69,6 +70,7 @@ updated whenever an artifact instance is created or reviewed.
 | [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] |
 | [ADR-0009] | ADR | [MIL-008], [ADR-0003], [ADR-0004], [ADR-0005], [ADR-0006] | - | [RC-063] |
 | [UC-007] | UC | [UCD-001], [US-001], [SA-001] | - | [RC-044] |
 | [RC-019] | RC | [UCD-001] | - | - |
 | [RC-020] | RC | [US-001] | - | - |
@@ -113,6 +115,10 @@ updated whenever an artifact instance is created or reviewed.
 | [RC-059] | RC | [MIL-007] | - | - |
 | [RC-060] | RC | [MIL-008] | - | - |
 | [RC-061] | RC | [MIL-008] | - | - |
 | [RC-062] | RC | [PP-001] | - | - |
 | [RC-063] | RC | [ADR-0009] | - | - |
 | [RC-064] | RC | [MIL-009], [PP-001] | - | - |
 | [RC-065] | RC | [ADR-0004] | - | - |
 ## Coverage Notes
@@ -134,6 +140,7 @@ updated whenever an artifact instance is created or reviewed.
 [MIL-006]: ../milestones/mil-006-shared-wiki-publishing.md
 [MIL-007]: ../milestones/mil-007-cpp-csharp-quality-checks.md
 [MIL-008]: ../milestones/mil-008-wiki-reusable-workflow.md
 [MIL-009]: ../milestones/mil-009-migrate-wiki-callers-and-remove-scoped-workflow.md
 [RC-001]: ./reviews/rc-001-business-case.md
 [RC-002]: ./reviews/rc-002-project-plan.md
 [RC-003]: ./reviews/rc-003-mil-001.md
@@ -205,7 +212,12 @@ updated whenever an artifact instance is created or reviewed.
 [RC-059]: ./reviews/rc-059-mil-007-adoption.md
 [RC-060]: ./reviews/rc-060-mil-008-plan.md
 [RC-061]: ./reviews/rc-061-mil-008-task-5-deferred.md
 [RC-062]: ./reviews/rc-062-pp-001-mil-008.md
 [RC-063]: ./reviews/rc-063-adr-0009.md
 [RC-064]: ./reviews/rc-064-mil-009-plan.md
 [RC-065]: ./reviews/rc-065-adr-0004-superseded.md
 [ADR-0008]: ../adr/adr-0008-cpp-csharp-quality-check-contract.md
 [ADR-0009]: ../adr/adr-0009-wiki-publishing-reusable-workflow.md
 [ADR-0007]: ../adr/adr-0007-release-publish-destination.md
 [UC-007]: ../uc-007/uc.md
 [UC-006]: ../uc-006/uc.md
@@ -214,5 +226,5 @@ updated whenever an artifact instance is created or reviewed.
 [ADR-0005]: ../adr/adr-0005-quality-check-contract.md
 [faf13b2]: https://git.tirsystem.com/TirSystem/github-action/commit/faf13b2c2a4901c0171977de1ffc2841023f537a
 [1bc56f8]: https://git.tirsystem.com/TirSystem/github-action/commit/1bc56f8b771531f221f218fc00b147ecc73c051e
-[2481c26]: https://git.tirsystem.com/TirSystem/github-action/commit/2481c26d802464decd51d75539157093b60e08e8
+[2f267df]: https://git.tirsystem.com/TirSystem/github-action/commit/2f267df2a270087cb7dc482af4ce4f4341e97b03
-[01b9c29]: https://git.tirsystem.com/TirSystem/github-action/commit/01b9c2972b4317bcc590540010aea0eaf7f30014
+[22fc323]: https://git.tirsystem.com/TirSystem/github-action/commit/22fc323b41074ee0029ea2f07445a8e329e15d15
@@ -1,4 +1,4 @@
-<!-- translation of Capabilities.md, source sha256 c60d434988dc -->
+<!-- translation of Capabilities.md, source sha256 7c310ccc1a66 -->
 > Dette er en oversættelse af [`Capabilities`](Capabilities). Den engelske side er autoritativ, og ændringer her bliver overskrevet, næste gang wikien publiceres.
@@ -13,8 +13,7 @@ Rækker, der siger Implementeret eller Vejledninger er skrevet, findes i dag. Re
 | Synkronisering af repositorymetadata (Gitea til GitHub-spejl) | Implementeret i `.gitea/scoped_workflows/`, med offline-tests og et valideringsworkflow |
 | Konfiguration og validering af workflow-credentials | Implementeret for synkroniseringsworkflowet: en forhåndskontrol tjekker begge tokens før enhver ændring ([vejledning](Credentials.da)) |
 | Tilslutning af et repository, administration af runners, fejlfinding | Vejledninger er skrevet ([tilslutning](Onboarding.da), [fejlfinding](Troubleshooting.da)); scoped levering til alle fire organisationers repositories er verificeret (MIL-002) |
-| Publicering af et repositorys wiki fra `wiki/` (tilmelding, leveres til alle organisationer) | Implementeret i `.gitea/scoped_workflows/publish-wiki.yml`, med offline-tests; et pilotforsøg i et andet repository publicerer sin wiki (MIL-006); afløses af det genbrugelige workflow nedenfor (ADR-0009) |
+| Publicering af et repositorys wiki fra `docs/wiki/` gennem et kaldt workflow | Implementeret som det genbrugelige workflow `.gitea/workflows/publish-wiki-pages.yml`, med offline-tests; kaldt af hvert repository, der publicerer en wiki, og dette repositorys egen wiki er i `docs/wiki/` (MIL-008, MIL-009) |
 | Publicering af et repositorys wiki fra `docs/wiki/` gennem et kaldt workflow | Implementeret som det genbrugelige workflow `.gitea/workflows/publish-wiki-pages.yml`, med offline-tests; dette repositorys egen wiki er i `docs/wiki/` og publiceres af det gennem `publish-own-wiki.yml`; endnu ikke kaldt fra et andet repository (MIL-008) |
 | Fælles kvalitetskontrol (Python og shell) | Implementeret som det genbrugelige workflow `.gitea/workflows/quality-checks.yml`, med offline-tests og et forsøg i en anden organisation; taget i brug i RepoFoundry ([vejledning](QualityChecksPythonShell.da)) |
 | Fælles kvalitetskontrol (C og C++, C#) | Implementeret som de genbrugelige workflows `.gitea/workflows/quality-checks-cpp.yml` og `.gitea/workflows/quality-checks-csharp.yml` med præcise værktøjsversioner og offline-tests; endnu ikke brugt i et andet repository (MIL-007) ([vejledning til C og C++](QualityChecksCpp.da), [vejledning til C#](QualityChecksCSharp.da)) |
 | Versioneret udgivelse og publicering | Udgivelsesproces, changelog og opgraderingsvejledning er defineret; udgivelsesworkflowet findes, og `v1.0.0` er udgivet (MIL-004) ([vejledning](Upgrading.da)) |
@@ -13,8 +13,7 @@ Rows that say Implemented or Guides written exist today. The rest is planned and
 | Synchronize repository metadata (Gitea to GitHub mirror) | Implemented in `.gitea/scoped_workflows/`, with offline tests and a validation workflow |
 | Configure and validate workflow credentials | Implemented for the sync workflow: preflight checks both tokens before any change ([guide](Credentials)) |
 | Onboard a repository, manage runners, diagnose failures | Guides written ([onboarding](Onboarding), [troubleshooting](Troubleshooting)); scoped delivery to the repositories of all four organizations verified (MIL-002) |
-| Publish a repository wiki from `wiki/` (opt-in, delivered to every organization) | Implemented in `.gitea/scoped_workflows/publish-wiki.yml`, with offline tests; a pilot in a second repository publishes its wiki (MIL-006); being replaced by the reusable workflow below (ADR-0009) |
+| Publish a repository wiki from `docs/wiki/` through a called workflow | Implemented as the reusable workflow `.gitea/workflows/publish-wiki-pages.yml`, with offline tests; called by every repository that publishes a wiki, and this repository's own wiki is in `docs/wiki/` (MIL-008, MIL-009) |
 | Publish a repository wiki from `docs/wiki/` through a called workflow | Implemented as the reusable workflow `.gitea/workflows/publish-wiki-pages.yml`, with offline tests; this repository's own wiki is in `docs/wiki/` and published by it through `publish-own-wiki.yml`; not yet called from another repository (MIL-008) |
 | Shared quality checks (Python and shell) | Implemented as the reusable workflow `.gitea/workflows/quality-checks.yml`, with offline tests and a trial in a second organization; adopted in RepoFoundry ([guide](QualityChecksPythonShell)) |
 | Shared quality checks (C and C++, C#) | Implemented as the reusable workflows `.gitea/workflows/quality-checks-cpp.yml` and `.gitea/workflows/quality-checks-csharp.yml` with exact tool versions and offline tests; not yet used in another repository (MIL-007) ([C and C++ guide](QualityChecksCpp), [C# guide](QualityChecksCSharp)) |
 | Versioned release and publishing | Release process, changelog and upgrade guide defined; the release workflow exists and `v1.0.0` is released (MIL-004) ([guide](Upgrading)) |
@@ -1,4 +1,4 @@
-<!-- translation of Capabilities.md, source sha256 c60d434988dc -->
+<!-- translation of Capabilities.md, source sha256 7c310ccc1a66 -->
 > Ini ialah terjemahan [`Capabilities`](Capabilities). Halaman bahasa Inggeris ialah teks yang sah, dan perubahan di sini akan ditimpa pada penerbitan wiki yang seterusnya.
@@ -13,8 +13,7 @@ Baris yang menyatakan Dilaksanakan atau Panduan telah ditulis wujud hari ini. Se
 | Menyegerakkan metadata repositori (Gitea ke cermin GitHub) | Dilaksanakan dalam `.gitea/scoped_workflows/`, dengan ujian luar talian dan aliran kerja pengesahan |
 | Mengkonfigur dan mengesahkan kelayakan (credentials) aliran kerja | Dilaksanakan untuk aliran kerja penyegerakan: semakan awal (preflight) memeriksa kedua-dua token sebelum sebarang perubahan ([panduan](Credentials.ms)) |
 | Menyertakan repositori, mengurus runner, mendiagnosis kegagalan | Panduan telah ditulis ([menyertakan repositori](Onboarding.ms), [diagnosis](Troubleshooting.ms)); penghantaran scoped ke repositori keempat-empat organisasi telah disahkan (MIL-002) |
-| Menerbitkan wiki repositori daripada `wiki/` (pilih menyertai, dihantar ke setiap organisasi) | Dilaksanakan dalam `.gitea/scoped_workflows/publish-wiki.yml`, dengan ujian luar talian; satu juruterbang dalam repositori kedua menerbitkan wikinya (MIL-006); sedang diganti oleh aliran kerja boleh guna semula di bawah (ADR-0009) |
+| Menerbitkan wiki repositori daripada `docs/wiki/` melalui aliran kerja yang dipanggil | Dilaksanakan sebagai aliran kerja boleh guna semula `.gitea/workflows/publish-wiki-pages.yml`, dengan ujian luar talian; dipanggil oleh setiap repositori yang menerbitkan wiki, dan wiki repositori ini sendiri ada dalam `docs/wiki/` (MIL-008, MIL-009) |
 | Menerbitkan wiki repositori daripada `docs/wiki/` melalui aliran kerja yang dipanggil | Dilaksanakan sebagai aliran kerja boleh guna semula `.gitea/workflows/publish-wiki-pages.yml`, dengan ujian luar talian; wiki repositori ini sendiri ada dalam `docs/wiki/` dan diterbitkan olehnya melalui `publish-own-wiki.yml`; belum dipanggil daripada repositori lain (MIL-008) |
 | Semakan kualiti bersama (Python dan shell) | Dilaksanakan sebagai aliran kerja boleh guna semula `.gitea/workflows/quality-checks.yml`, dengan ujian luar talian dan percubaan dalam organisasi kedua; digunakan dalam RepoFoundry ([panduan](QualityChecksPythonShell.ms)) |
 | Semakan kualiti bersama (C dan C++, C#) | Dilaksanakan sebagai aliran kerja boleh guna semula `.gitea/workflows/quality-checks-cpp.yml` dan `.gitea/workflows/quality-checks-csharp.yml` dengan versi alat yang tepat dan ujian luar talian; belum digunakan dalam repositori lain (MIL-007) ([panduan C dan C++](QualityChecksCpp.ms), [panduan C#](QualityChecksCSharp.ms)) |
 | Keluaran berversi dan penerbitan | Proses keluaran, changelog dan panduan naik taraf telah ditakrifkan; aliran kerja keluaran sudah ada dan `v1.0.0` telah dikeluarkan (MIL-004) ([panduan](Upgrading.ms)) |
@@ -1,4 +1,4 @@
-<!-- translation of Home.md, source sha256 b6796554f4eb -->
+<!-- translation of Home.md, source sha256 074ce16f3435 -->
 > Dette er en oversættelse af [`Home`](Home). Den engelske side er autoritativ, og ændringer her bliver overskrevet, næste gang wikien publiceres.
@@ -13,17 +13,16 @@ 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 ti workflows: synkronisering af metadata til GitHub-spejlet, publicering af wiki (scoped og genbrugeligt for repositories, der kalder det), 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 ni workflows: synkronisering af metadata til GitHub-spejlet, publicering af wiki (kaldt af hvert repository), 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).
 ## Workflows
-Der er ti 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 ni 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`; forældet, afløses af det genbrugelige workflow nedenfor (ADR-0009) | push til `main`, der ændrer `wiki/**`, manuelt | Publicerer siderne i `wiki/` til repositoryets wiki |
 | Publish wiki pages | [`publish-wiki-pages.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/publish-wiki-pages.yml) | Genbrugeligt (`workflow_call`) | et kald fra et andet repository | Publicerer siderne i `docs/wiki/` (eller den mappe, `wiki_dir` angiver) til wikien i det kaldende repository |
 | 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 |
@@ -99,50 +98,6 @@ deactivate Workflow
@enduml
 ```
 ### Publicering af wiki (scoped, forældet)
 Publicerer `wiki/` til repositoryets wiki, kun i et repository, der har tilmeldt sig med `wiki/.publish`. Ordet `prune` i den fil sletter også sider, som ikke findes i `wiki/`.
 #### Workflow
 ```plantuml
@startuml
 title Publish wiki/ to the repository wiki
 autonumber
 actor "Push to main that changes wiki/**,\nor manual trigger" as Trigger
 participant "Gitea Actions\npublish-wiki" as Workflow
 participant "shared-scripts\n(tools/publish_wiki.py at v1)" as Script
 participant "Gitea wiki API" as Wiki
 Trigger -> Workflow: Start workflow
 activate Workflow
 Workflow -> Script: Check out the repository and the script, run it
 activate Script
 alt wiki/.publish does not exist
  Script --> Workflow: Log that publishing is not enabled and succeed\n(nothing is written)
 else wiki/ has no Markdown pages
  Script --> Workflow: Fail with [configuration]\n(an empty wiki/ never deletes pages)
 else
  Script -> Script: Read the marker (empty, or the word prune)\nand TOKEN_FOR_GITEA_WIKI
  Script -> Wiki: GET repository (preflight)
  Wiki --> Script: Wiki is enabled, token accepted
  Script -> Wiki: GET pages
  Wiki --> Script: Existing pages
  Script -> Wiki: Create new pages, update changed pages
  opt marker says prune
    Script -> Wiki: Delete pages that are not in wiki/
  end
  Script --> Workflow: Log created, updated and deleted counts
 end
 deactivate Script
 Workflow --> Trigger: Workflow result
 deactivate Workflow
@enduml
 ```
 ### Kvalitetskontrol
 Et genbrugeligt workflow til Python og shell, kaldt med `uses: TirSystem/github-action/.gitea/workflows/quality-checks.yml@v1` (se [vejledningen](QualityChecksPythonShell)).
@@ -13,17 +13,16 @@ 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 ten workflows: metadata sync to the GitHub mirror, wiki publishing (scoped, and reusable for repositories that call it), 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 nine workflows: metadata sync to the GitHub mirror, wiki publishing (called by each repository), 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).
 ## Workflows
-Ten 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.
+Nine 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`; deprecated, replaced by the reusable workflow below (ADR-0009) | push to `main` that changes `wiki/**`, manual | Publishes the pages in `wiki/` to the repository wiki |
 | Publish wiki pages | [`publish-wiki-pages.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/publish-wiki-pages.yml) | Reusable (`workflow_call`) | a call from another repository | Publishes the pages in `docs/wiki/` (or the folder named by `wiki_dir`) to the wiki of the calling repository |
 | 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 |
@@ -99,50 +98,6 @@ deactivate Workflow
@enduml
 ```
 ### Publish wiki (scoped, deprecated)
 Publishes `wiki/` to the repository wiki, only in a repository that has opted in with `wiki/.publish`. The word `prune` in that file also deletes pages that are not in `wiki/`.
 #### Workflow
 ```plantuml
@startuml
 title Publish wiki/ to the repository wiki
 autonumber
 actor "Push to main that changes wiki/**,\nor manual trigger" as Trigger
 participant "Gitea Actions\npublish-wiki" as Workflow
 participant "shared-scripts\n(tools/publish_wiki.py at v1)" as Script
 participant "Gitea wiki API" as Wiki
 Trigger -> Workflow: Start workflow
 activate Workflow
 Workflow -> Script: Check out the repository and the script, run it
 activate Script
 alt wiki/.publish does not exist
  Script --> Workflow: Log that publishing is not enabled and succeed\n(nothing is written)
 else wiki/ has no Markdown pages
  Script --> Workflow: Fail with [configuration]\n(an empty wiki/ never deletes pages)
 else
  Script -> Script: Read the marker (empty, or the word prune)\nand TOKEN_FOR_GITEA_WIKI
  Script -> Wiki: GET repository (preflight)
  Wiki --> Script: Wiki is enabled, token accepted
  Script -> Wiki: GET pages
  Wiki --> Script: Existing pages
  Script -> Wiki: Create new pages, update changed pages
  opt marker says prune
    Script -> Wiki: Delete pages that are not in wiki/
  end
  Script --> Workflow: Log created, updated and deleted counts
 end
 deactivate Script
 Workflow --> Trigger: Workflow result
 deactivate Workflow
@enduml
 ```
 ### Quality checks
 A reusable workflow for Python and shell, called with `uses: TirSystem/github-action/.gitea/workflows/quality-checks.yml@v1` (see the [guide](QualityChecksPythonShell)).
@@ -1,4 +1,4 @@
-<!-- translation of Home.md, source sha256 b6796554f4eb -->
+<!-- translation of Home.md, source sha256 074ce16f3435 -->
 > Ini ialah terjemahan [`Home`](Home). Halaman bahasa Inggeris ialah teks yang sah, dan perubahan di sini akan ditimpa pada penerbitan wiki yang seterusnya.
@@ -13,17 +13,16 @@ 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 sepuluh aliran kerja: penyegerakan metadata ke cermin GitHub, penerbitan wiki (scoped, dan boleh guna semula bagi repositori yang memanggilnya), 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 sembilan aliran kerja: penyegerakan metadata ke cermin GitHub, penerbitan wiki (dipanggil oleh setiap repositori), 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).
 ## Aliran kerja
-Terdapat sepuluh 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 sembilan 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`; usang, sedang diganti oleh aliran kerja boleh guna semula di bawah (ADR-0009) | push ke `main` yang mengubah `wiki/**`, manual | Menerbitkan halaman dalam `wiki/` ke wiki repositori |
 | Publish wiki pages | [`publish-wiki-pages.yml`](https://git.tirsystem.com/TirSystem/github-action/src/branch/main/.gitea/workflows/publish-wiki-pages.yml) | Boleh guna semula (`workflow_call`) | panggilan daripada repositori lain | Menerbitkan halaman dalam `docs/wiki/` (atau folder yang dinamakan oleh `wiki_dir`) ke wiki repositori pemanggil |
 | 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 |
@@ -99,50 +98,6 @@ deactivate Workflow
@enduml
 ```
 ### Menerbitkan wiki (scoped, usang)
 Menerbitkan `wiki/` ke wiki repositori, hanya dalam repositori yang telah menyertai dengan `wiki/.publish`. Perkataan `prune` dalam fail itu juga memadam halaman yang tiada dalam `wiki/`.
 #### Aliran kerja
 ```plantuml
@startuml
 title Publish wiki/ to the repository wiki
 autonumber
 actor "Push to main that changes wiki/**,\nor manual trigger" as Trigger
 participant "Gitea Actions\npublish-wiki" as Workflow
 participant "shared-scripts\n(tools/publish_wiki.py at v1)" as Script
 participant "Gitea wiki API" as Wiki
 Trigger -> Workflow: Start workflow
 activate Workflow
 Workflow -> Script: Check out the repository and the script, run it
 activate Script
 alt wiki/.publish does not exist
  Script --> Workflow: Log that publishing is not enabled and succeed\n(nothing is written)
 else wiki/ has no Markdown pages
  Script --> Workflow: Fail with [configuration]\n(an empty wiki/ never deletes pages)
 else
  Script -> Script: Read the marker (empty, or the word prune)\nand TOKEN_FOR_GITEA_WIKI
  Script -> Wiki: GET repository (preflight)
  Wiki --> Script: Wiki is enabled, token accepted
  Script -> Wiki: GET pages
  Wiki --> Script: Existing pages
  Script -> Wiki: Create new pages, update changed pages
  opt marker says prune
    Script -> Wiki: Delete pages that are not in wiki/
  end
  Script --> Workflow: Log created, updated and deleted counts
 end
 deactivate Script
 Workflow --> Trigger: Workflow result
 deactivate Workflow
@enduml
 ```
 ### Semakan kualiti
 Aliran kerja boleh guna semula untuk Python dan shell, dipanggil dengan `uses: TirSystem/github-action/.gitea/workflows/quality-checks.yml@v1` (lihat [panduan](QualityChecksPythonShell)).
@@ -1,4 +1,4 @@
-<!-- translation of Onboarding.md, source sha256 4de4897fb3b7 -->
+<!-- translation of Onboarding.md, source sha256 1bc66efd5874 -->
 > Dette er en oversættelse af [`Onboarding`](Onboarding). Den engelske side er autoritativ, og ændringer her bliver overskrevet, næste gang wikien publiceres.
@@ -56,8 +56,6 @@ Det genbrugelige workflow **Publish wiki pages** kopierer Markdown-siderne i `do
 4. Gem `TOKEN_FOR_GITEA_WIKI` som en secret i repositoryets organisation med det scope, der står i [credentials.md](Credentials.da).
 5. Flet ændringen til `main`. Loggen skal slutte med `Published <n> page(s) to the wiki of <owner>/<repo>`.
 Et repository, der stadig har markøren `wiki/.publish`, publiceres af det ældre scoped workflow, som fjernes, når alle repositories har et kald. Flyt siderne til `docs/wiki/` og tilføj kaldet, før det sker.
 ## Runners
 | Punkt | Værdi |
@@ -85,10 +85,6 @@ The wiki has English and the product owner's language as a minimum.
 5. Merge the change to `main`. The log must end with `Published <n> page(s) to
   the wiki of <owner>/<repo>`.
 A repository that still has the marker `wiki/.publish` is published by the
 older scoped workflow, which is removed once every repository has a call.
 Move the pages to `docs/wiki/` and add the call before that.
 ## Runners
 | Item | Value |
@@ -1,4 +1,4 @@
-<!-- translation of Onboarding.md, source sha256 4de4897fb3b7 -->
+<!-- translation of Onboarding.md, source sha256 1bc66efd5874 -->
 > Ini ialah terjemahan [`Onboarding`](Onboarding). Halaman bahasa Inggeris ialah teks yang sah, dan perubahan di sini akan ditimpa pada penerbitan wiki yang seterusnya.
@@ -56,8 +56,6 @@ Aliran kerja boleh guna semula **Publish wiki pages** menyalin halaman Markdown
 4. Simpan `TOKEN_FOR_GITEA_WIKI` sebagai secret organisasi repositori, dengan skop yang tertera dalam [credentials.md](Credentials.ms).
 5. Gabungkan perubahan ke `main`. Log mesti berakhir dengan `Published <n> page(s) to the wiki of <owner>/<repo>`.
 Repositori yang masih mempunyai penanda `wiki/.publish` diterbitkan oleh aliran kerja scoped yang lebih lama, yang dibuang apabila setiap repositori mempunyai panggilan. Alihkan halaman ke `docs/wiki/` dan tambah panggilan sebelum itu.
 ## Runners
 | Perkara | Nilai |
@@ -1,4 +1,4 @@
-<!-- translation of Troubleshooting.md, source sha256 c68827295812 -->
+<!-- translation of Troubleshooting.md, source sha256 cad6363616e8 -->
 > Dette er en oversættelse af [`Troubleshooting`](Troubleshooting). Den engelske side er autoritativ, og ændringer her bliver overskrevet, næste gang wikien publiceres.
@@ -31,7 +31,6 @@ Kategorien fortæller, hvor du skal kigge. En fejl uden for scriptet (jobbet sta
 | `Could not determine the Gitea source repository.` | configuration | Kørslen har intet repositorynavn; meld det som en defekt |
 | `Expected at most one GitHub push mirror ... found N` | configuration | Behold ét GitHub push-spejl |
 | `TOKEN_FOR_GITEA_WIKI is missing or empty.` | configuration | Kun wiki-publicering: repositoryet kalder workflowet, men dets organisation har ingen sådan secret, eller kaldet sender den ikke; gem den og send den i `secrets:` (se [credentials.md](Credentials.da)) |
 | `wiki/.publish may only be empty or contain the word 'prune'.` | configuration | Kun wiki-publicering gennem det ældre scoped workflow: lad markøren være tom, eller skriv kun ordet `prune` i den |
 | `The prune input must be 'true' or 'false'` | configuration | Kun wiki-publicering: sæt `prune` i kaldet til `"true"` eller `"false"` |
 | `The wiki folder ... does not exist` | configuration | Kun wiki-publicering: sæt `wiki_dir` i kaldet til mappen med siderne (standard `docs/wiki`) |
 | `... HTTP 403 ...` ved publicering af wikien | permissions | Kun wiki-publicering: tokenet skal have `write:repository` og skriveadgang til dette repository |
@@ -53,9 +52,7 @@ Kategorien fortæller, hvor du skal kigge. En fejl uden for scriptet (jobbet sta
 `WARNING: Gitea returned an invalid push mirror list; GitHub metadata was not synced.` Kørslen lykkes, men intet blev synkroniseret. Kontroller, at Gitea-versionen understøtter push mirror-API'et, og kør igen.
-`No wiki/.publish marker in <owner>/<repo>; wiki publishing is not enabled for this repository.` Kørslen af det ældre scoped Publish wiki lykkes og skriver intet. Repositoryet har ikke meldt sig til; kald det genbrugelige workflow **Publish wiki pages** (se [onboarding.md](Onboarding.da)), hvis det skal publicere.
+`<n> page(s) are in the wiki but not in <folder>/ and were kept; set the prune input to true to delete them.` Kørslen lykkes. Sider, der kun findes i wikien, lades i fred, medmindre kaldet sætter `prune: "true"`.
 `<n> page(s) are in the wiki but not in <folder>/ and were kept; set the prune input to true to delete them.` Kørslen lykkes. Sider, der kun findes i wikien, lades i fred, medmindre kaldet sætter `prune: "true"` (med det ældre scoped workflow: ordet `prune` i `wiki/.publish`).
 ## Runner-problemer
@@ -33,7 +33,6 @@ never starts, or stops before the step) is a **runner** problem.
 | `Could not determine the Gitea source repository.` | configuration | The run has no repository name; report as a defect |
 | `Expected at most one GitHub push mirror ... found N` | configuration | Keep one GitHub push mirror |
 | `TOKEN_FOR_GITEA_WIKI is missing or empty.` | configuration | Wiki publishing only: the repository calls the workflow but its organization has no such secret, or the call does not pass it; store it and pass it in `secrets:` (see [credentials.md](Credentials)) |
 | `wiki/.publish may only be empty or contain the word 'prune'.` | configuration | Wiki publishing through the older scoped workflow only: leave the marker empty, or put only the word `prune` in it |
 | `The prune input must be 'true' or 'false'` | configuration | Wiki publishing only: set `prune` in the call to `"true"` or `"false"` |
 | `The wiki folder ... does not exist` | configuration | Wiki publishing only: set `wiki_dir` in the call to the folder with the pages (default `docs/wiki`) |
 | `... HTTP 403 ...` while publishing the wiki | permissions | Wiki publishing only: the token needs `write:repository` and write access to this repository |
@@ -60,15 +59,9 @@ settings.
 synced.` The run succeeds but nothing was synced. Check that the Gitea
 version supports the push mirror API and re-run.
 `No wiki/.publish marker in <owner>/<repo>; wiki publishing is not enabled for
 this repository.` The older scoped Publish wiki run succeeds and writes
 nothing. The repository has not opted in; call the reusable workflow
 **Publish wiki pages** (see [onboarding.md](Onboarding)) if it should publish.
 `<n> page(s) are in the wiki but not in <folder>/ and were kept; set the prune
 input to true to delete them.` The run succeeds. Pages that exist only in the
-wiki are left alone unless the call sets `prune: "true"` (with the older scoped
+wiki are left alone unless the call sets `prune: "true"`.
 workflow: the word `prune` in `wiki/.publish`).
 ## Runner problems
@@ -1,4 +1,4 @@
-<!-- translation of Troubleshooting.md, source sha256 c68827295812 -->
+<!-- translation of Troubleshooting.md, source sha256 cad6363616e8 -->
 > Ini ialah terjemahan [`Troubleshooting`](Troubleshooting). Halaman bahasa Inggeris ialah teks yang sah, dan perubahan di sini akan ditimpa pada penerbitan wiki yang seterusnya.
@@ -31,7 +31,6 @@ Kategori menunjukkan di mana perlu dilihat. Kegagalan di luar skrip (kerja tidak
 | `Could not determine the Gitea source repository.` | configuration | Larian tiada nama repositori; laporkan sebagai kecacatan |
 | `Expected at most one GitHub push mirror ... found N` | configuration | Kekalkan satu push mirror GitHub |
 | `TOKEN_FOR_GITEA_WIKI is missing or empty.` | configuration | Penerbitan wiki sahaja: repositori memanggil aliran kerja tetapi organisasinya tiada secret itu, atau panggilan tidak menghantarnya; simpannya dan hantar dalam `secrets:` (lihat [credentials.md](Credentials.ms)) |
 | `wiki/.publish may only be empty or contain the word 'prune'.` | configuration | Penerbitan wiki melalui aliran kerja scoped yang lebih lama sahaja: biarkan penanda kosong, atau letakkan hanya perkataan `prune` di dalamnya |
 | `The prune input must be 'true' or 'false'` | configuration | Penerbitan wiki sahaja: tetapkan `prune` dalam panggilan kepada `"true"` atau `"false"` |
 | `The wiki folder ... does not exist` | configuration | Penerbitan wiki sahaja: tetapkan `wiki_dir` dalam panggilan kepada folder yang mengandungi halaman (lalai `docs/wiki`) |
 | `... HTTP 403 ...` semasa menerbitkan wiki | permissions | Penerbitan wiki sahaja: token memerlukan `write:repository` dan akses tulis kepada repositori ini |
@@ -53,9 +52,7 @@ Kategori menunjukkan di mana perlu dilihat. Kegagalan di luar skrip (kerja tidak
 `WARNING: Gitea returned an invalid push mirror list; GitHub metadata was not synced.` Larian berjaya tetapi tiada apa-apa disegerakkan. Semak bahawa versi Gitea menyokong API push mirror dan jalankan semula.
-`No wiki/.publish marker in <owner>/<repo>; wiki publishing is not enabled for this repository.` Larian Publish wiki scoped yang lebih lama berjaya dan tidak menulis apa-apa. Repositori belum memilih menyertainya; panggil aliran kerja boleh guna semula **Publish wiki pages** (lihat [onboarding.md](Onboarding.ms)) jika ia sepatutnya menerbitkan.
+`<n> page(s) are in the wiki but not in <folder>/ and were kept; set the prune input to true to delete them.` Larian berjaya. Halaman yang hanya ada dalam wiki dibiarkan melainkan panggilan menetapkan `prune: "true"`.
 `<n> page(s) are in the wiki but not in <folder>/ and were kept; set the prune input to true to delete them.` Larian berjaya. Halaman yang hanya ada dalam wiki dibiarkan melainkan panggilan menetapkan `prune: "true"` (dengan aliran kerja scoped yang lebih lama: perkataan `prune` dalam `wiki/.publish`).
 ## Masalah runner
@@ -1,4 +1,4 @@
-<!-- translation of Upgrading.md, source sha256 7fba937279b1 -->
+<!-- translation of Upgrading.md, source sha256 1e6a40ed1320 -->
 > Dette er en oversættelse af [`Upgrading`](Upgrading). Den engelske side er autoritativ, og ændringer her bliver overskrevet, næste gang wikien publiceres.
@@ -20,7 +20,7 @@ En udgivelse, der bryder kompatibiliteten, får en ny major-version (`v2`), så
 Kvalitetskontrol-workflowene (`quality-checks.yml`, `quality-checks-cpp.yml` og `quality-checks-csharp.yml`) henter deres script ved deres input `tools-ref`, som som standard er `v1`. For at fastlåse et helt skal du kalde det ved et præcist tag og sætte `tools-ref` til samme tag; ellers følger scriptet major-tagget.
-De to scoped workflows (**Sync GitHub mirror metadata** og **Publish wiki**) leveres af instansen og står ikke i dine `uses:`-linjer; du kan ikke fastlåse dem, men de henter deres scripts ved major-tagget.
+Det scoped workflow **Sync GitHub mirror metadata** leveres af instansen og står ikke i dine `uses:`-linjer; du kan ikke fastlåse det, men det henter sit script ved major-tagget. Publicering af wiki er et genbrugeligt workflow, du kalder (`publish-wiki-pages.yml`); det scoped workflow **Publish wiki** og dets markør `wiki/.publish` blev fjernet i 2.0.0, så et repository, der stadig har markøren, publicerer ikke mere, før det kalder det genbrugelige workflow (se introduktionsguiden).
 ## Aflæsning af en changelog-post
@@ -27,9 +27,13 @@ The quality-checks workflows (`quality-checks.yml`, `quality-checks-cpp.yml` and
 defaults to `v1`. To pin one completely, call it at an exact tag and set
 `tools-ref` to the same tag; otherwise the script follows the major tag.
-The two scoped workflows (**Sync GitHub mirror metadata** and **Publish
+The scoped workflow **Sync GitHub mirror metadata** is delivered by the
-wiki**) are delivered by the instance and are not in your `uses:` lines; you
+instance and is not in your `uses:` lines; you cannot pin it, but it fetches its
-cannot pin them, but they fetch their scripts at the major tag.
+script at the major tag. Wiki publishing is a reusable workflow you call
 (`publish-wiki-pages.yml`); the scoped **Publish wiki** workflow and its
 `wiki/.publish` marker were removed in 2.0.0, so a repository that still has the
 marker no longer publishes until it calls the reusable workflow (see the
 onboarding guide).
 ## Reading a changelog entry
@@ -1,4 +1,4 @@
-<!-- translation of Upgrading.md, source sha256 7fba937279b1 -->
+<!-- translation of Upgrading.md, source sha256 1e6a40ed1320 -->
 > Ini ialah terjemahan [`Upgrading`](Upgrading). Halaman bahasa Inggeris ialah teks yang sah, dan perubahan di sini akan ditimpa pada penerbitan wiki yang seterusnya.
@@ -20,7 +20,7 @@ Keluaran yang memecahkan keserasian mendapat versi major baharu (`v2`), jadi sal
 Aliran kerja semakan kualiti (`quality-checks.yml`, `quality-checks-cpp.yml` dan `quality-checks-csharp.yml`) mengambil skripnya pada inputnya `tools-ref`, yang lalai ialah `v1`. Untuk menyematkan satu sepenuhnya, panggil pada tag tepat dan tetapkan `tools-ref` kepada tag yang sama; jika tidak, skrip mengikuti tag major.
-Dua aliran kerja scoped (**Sync GitHub mirror metadata** dan **Publish wiki**) dihantar oleh instans dan tidak terdapat dalam baris `uses:` anda; anda tidak boleh menyematkannya, tetapi ia mengambil skripnya pada tag major.
+Aliran kerja scoped **Sync GitHub mirror metadata** dihantar oleh instans dan tidak terdapat dalam baris `uses:` anda; anda tidak boleh menyematkannya, tetapi ia mengambil skripnya pada tag major. Penerbitan wiki ialah aliran kerja boleh guna semula yang anda panggil (`publish-wiki-pages.yml`); aliran kerja scoped **Publish wiki** dan penanda `wiki/.publish` telah dibuang dalam 2.0.0, jadi repositori yang masih mempunyai penanda itu tidak lagi menerbitkan sehingga ia memanggil aliran kerja boleh guna semula (lihat panduan permulaan).
 ## Membaca satu catatan changelog
@@ -79,10 +79,6 @@ The wiki has English and the product owner's language as a minimum.
 5. Merge the change to `main`. The log must end with `Published <n> page(s) to
   the wiki of <owner>/<repo>`.
 A repository that still has the marker `wiki/.publish` is published by the
 older scoped workflow, which is removed once every repository has a call.
 Move the pages to `docs/wiki/` and add the call before that.
 ## Runners
 | Item | Value |
@@ -27,7 +27,6 @@ never starts, or stops before the step) is a **runner** problem.
 | `Could not determine the Gitea source repository.` | configuration | The run has no repository name; report as a defect |
 | `Expected at most one GitHub push mirror ... found N` | configuration | Keep one GitHub push mirror |
 | `TOKEN_FOR_GITEA_WIKI is missing or empty.` | configuration | Wiki publishing only: the repository calls the workflow but its organization has no such secret, or the call does not pass it; store it and pass it in `secrets:` (see [credentials.md](credentials.md)) |
 | `wiki/.publish may only be empty or contain the word 'prune'.` | configuration | Wiki publishing through the older scoped workflow only: leave the marker empty, or put only the word `prune` in it |
 | `The prune input must be 'true' or 'false'` | configuration | Wiki publishing only: set `prune` in the call to `"true"` or `"false"` |
 | `The wiki folder ... does not exist` | configuration | Wiki publishing only: set `wiki_dir` in the call to the folder with the pages (default `docs/wiki`) |
 | `... HTTP 403 ...` while publishing the wiki | permissions | Wiki publishing only: the token needs `write:repository` and write access to this repository |
@@ -54,15 +53,9 @@ settings.
 synced.` The run succeeds but nothing was synced. Check that the Gitea
 version supports the push mirror API and re-run.
 `No wiki/.publish marker in <owner>/<repo>; wiki publishing is not enabled for
 this repository.` The older scoped Publish wiki run succeeds and writes
 nothing. The repository has not opted in; call the reusable workflow
 **Publish wiki pages** (see [onboarding.md](onboarding.md)) if it should publish.
 `<n> page(s) are in the wiki but not in <folder>/ and were kept; set the prune
 input to true to delete them.` The run succeeds. Pages that exist only in the
-wiki are left alone unless the call sets `prune: "true"` (with the older scoped
+wiki are left alone unless the call sets `prune: "true"`.
 workflow: the word `prune` in `wiki/.publish`).
 ## Runner problems
@@ -21,9 +21,13 @@ The quality-checks workflows (`quality-checks.yml`, `quality-checks-cpp.yml` and
 defaults to `v1`. To pin one completely, call it at an exact tag and set
 `tools-ref` to the same tag; otherwise the script follows the major tag.
-The two scoped workflows (**Sync GitHub mirror metadata** and **Publish
+The scoped workflow **Sync GitHub mirror metadata** is delivered by the
-wiki**) are delivered by the instance and are not in your `uses:` lines; you
+instance and is not in your `uses:` lines; you cannot pin it, but it fetches its
-cannot pin them, but they fetch their scripts at the major tag.
+script at the major tag. Wiki publishing is a reusable workflow you call
 (`publish-wiki-pages.yml`); the scoped **Publish wiki** workflow and its
 `wiki/.publish` marker were removed in 2.0.0, so a repository that still has the
 marker no longer publishes until it calls the reusable workflow (see the
 onboarding guide).
 ## Reading a changelog entry
@@ -7,7 +7,7 @@ import urllib.error
 import pytest
 import yaml
-from workflow_source import PUBLISH_WORKFLOW, REPO_ROOT, load_publish_module
+from workflow_source import REPO_ROOT, load_publish_module
 REUSABLE_WORKFLOW = REPO_ROOT / ".gitea" / "workflows" / "publish-wiki-pages.yml"
@@ -25,22 +25,6 @@ def b64(text: str) -> str:
    return base64.b64encode(text.encode()).decode()
 class TestParseMarker:
    @pytest.mark.parametrize(
        ("text", "expected"),
        [("", False), ("  \n", False), (None, False), ("prune", True), (" prune\n", True)],
    )
    def test_reads_the_empty_marker_and_the_prune_word(self, publish_wiki, text, expected):
        assert publish_wiki.parse_marker(text) is expected
    @pytest.mark.parametrize("text", ["Prune", "prune: true", "delete", "prune\nmore"])
    def test_rejects_anything_else(self, publish_wiki, text):
        with pytest.raises(publish_wiki.WorkflowError) as caught:
            publish_wiki.parse_marker(text)
        assert caught.value.category == "configuration"
        assert "prune" in str(caught.value)
 class TestParseGiteaToken:
    def test_returns_the_stripped_token(self, publish_wiki):
        assert publish_wiki.parse_gitea_token(" abc \n") == "abc"
@@ -54,17 +38,15 @@ class TestParseGiteaToken:
 class TestReadPages:
-    def test_reads_markdown_files_by_stem_and_ignores_the_marker(self, publish_wiki, tmp_path):
+    def test_reads_markdown_files_by_stem_and_ignores_other_files(self, publish_wiki, tmp_path):
        (tmp_path / "Home.md").write_bytes(b"home")
        (tmp_path / "Home.da.md").write_bytes(b"hjem")
        (tmp_path / ".publish").write_bytes(b"prune")
        (tmp_path / "Notes.txt").write_bytes(b"ignored")
        assert publish_wiki.read_pages(tmp_path) == {"Home": b"home", "Home.da": b"hjem"}
    def test_rejects_a_directory_without_pages_so_the_wiki_is_never_wiped(
        self, publish_wiki, tmp_path
    ):
        (tmp_path / ".publish").write_text("prune", encoding="utf-8")
        with pytest.raises(publish_wiki.WorkflowError, match="no Markdown pages"):
            publish_wiki.read_pages(tmp_path)
@@ -143,7 +125,7 @@ def environment(monkeypatch, tmp_path):
    wiki_dir.mkdir()
    (wiki_dir / "Home.md").write_text("home v2", encoding="utf-8")
    (wiki_dir / "Credentials.md").write_text("credentials", encoding="utf-8")
-    (wiki_dir / ".publish").write_text("prune\n", encoding="utf-8")
+    monkeypatch.setenv("WIKI_PRUNE", "true")
    monkeypatch.setenv("WIKI_DIR", str(wiki_dir))
    monkeypatch.setenv("GITEA_API_URL", f"{API}/")
    monkeypatch.setenv("SOURCE_REPOSITORY", "TirSystem/repo")
@@ -156,58 +138,6 @@ def run_main(publish_wiki, gitea):
    return publish_wiki.main()
 class TestOptIn:
    def test_a_repository_without_the_marker_is_never_written_to(
        self, publish_wiki, environment, capsys
    ):
        (environment / ".publish").unlink()
        gitea = FakeGitea(publish_wiki, wiki={"Old": b64("hand written")})
        assert run_main(publish_wiki, gitea) == 0
        assert gitea.calls == []
        assert "wiki publishing is not enabled" in capsys.readouterr().out
        assert gitea.wiki == {"Old": b64("hand written")}
    def test_a_repository_without_the_marker_does_not_need_the_secret(
        self, publish_wiki, environment, monkeypatch
    ):
        (environment / ".publish").unlink()
        monkeypatch.setenv("WIKI_CREDENTIALS", "")
        assert run_main(publish_wiki, FakeGitea(publish_wiki)) == 0
    def test_a_repository_without_a_wiki_directory_is_skipped(
        self, publish_wiki, monkeypatch, tmp_path
    ):
        monkeypatch.setenv("WIKI_DIR", str(tmp_path / "missing"))
        monkeypatch.setenv("SOURCE_REPOSITORY", "TirSystem/repo")
        gitea = FakeGitea(publish_wiki)
        assert run_main(publish_wiki, gitea) == 0
        assert gitea.calls == []
    def test_an_opted_in_repository_without_the_secret_fails_before_any_request(
        self, publish_wiki, environment, monkeypatch
    ):
        monkeypatch.setenv("WIKI_CREDENTIALS", "")
        gitea = FakeGitea(publish_wiki)
        with pytest.raises(publish_wiki.WorkflowError, match="TOKEN_FOR_GITEA_WIKI"):
            run_main(publish_wiki, gitea)
        assert gitea.calls == []
    def test_an_unknown_marker_content_is_refused_before_any_request(
        self, publish_wiki, environment
    ):
        (environment / ".publish").write_text("mirror everything", encoding="utf-8")
        gitea = FakeGitea(publish_wiki)
        with pytest.raises(publish_wiki.WorkflowError, match="prune"):
            run_main(publish_wiki, gitea)
        assert gitea.calls == []
 class TestPublish:
    def test_prune_creates_updates_and_deletes_to_match_the_source(
        self, publish_wiki, environment, capsys
@@ -227,9 +157,9 @@ class TestPublish:
        assert "0 created, 1 updated, 1 deleted" in capsys.readouterr().out
    def test_without_prune_pages_outside_the_source_are_kept(
-        self, publish_wiki, environment, capsys
+        self, publish_wiki, environment, capsys, monkeypatch
    ):
-        (environment / ".publish").write_text("", encoding="utf-8")
+        monkeypatch.setenv("WIKI_PRUNE", "false")
        gitea = FakeGitea(
            publish_wiki, wiki={"Home": b64("home v1"), "Old": b64("hand written")}
        )
@@ -302,11 +232,11 @@ class TestPageIdentity:
    """A wiki that already has pages named with spaces, as Gitea stores them."""
    def test_a_file_named_with_a_space_updates_the_existing_page(
-        self, publish_wiki, environment
+        self, publish_wiki, environment, monkeypatch
    ):
        (environment / "Home.md").unlink()
        (environment / "Credentials.md").unlink()
-        (environment / ".publish").write_text("", encoding="utf-8")
+        monkeypatch.setenv("WIKI_PRUNE", "false")
        (environment / "Home da.md").write_text("hjem v2", encoding="utf-8")
        gitea = FakeGitea(publish_wiki, wiki={"Home-da": b64("hjem v1")})
@@ -457,7 +387,6 @@ class TestExplicitPrune:
    @pytest.fixture()
    def explicit(self, environment, monkeypatch):
        (environment / ".publish").unlink()
        monkeypatch.setenv("WIKI_PRUNE", "false")
        return environment
@@ -567,38 +496,12 @@ class TestReusableWorkflow:
        assert fetch["ref"] == "${{ inputs.tools-ref }}"
-class TestWorkflow:
+def test_the_scoped_workflow_is_gone_and_the_script_has_no_marker_path():
-    @pytest.fixture()
+    """ADR-0009, MIL-009: the scoped publish-wiki.yml and the marker are removed."""
-    def document(self):
+    assert not (REPO_ROOT / ".gitea" / "scoped_workflows" / "publish-wiki.yml").exists()
-        return yaml.safe_load(PUBLISH_WORKFLOW.read_text(encoding="utf-8"))
+    source = (REPO_ROOT / "tools" / "publish_wiki.py").read_text(encoding="utf-8")
-
+    assert "MARKER_NAME" not in source
-    def test_runs_only_on_main_when_wiki_changes_or_by_hand(self, document):
+    assert "parse_marker" not in source
        triggers = document[True]  # PyYAML reads the key `on` as True
        assert triggers["push"]["branches"] == ["main"]
        assert triggers["push"]["paths"] == ["wiki/**"]
        assert "workflow_dispatch" in triggers
    def test_job_has_read_only_permissions(self, document):
        assert document["jobs"]["publish-wiki"]["permissions"] == {"contents": "read"}
    def test_secret_is_passed_only_through_the_environment_and_has_no_fallback(self, document):
        text = PUBLISH_WORKFLOW.read_text(encoding="utf-8")
        assert "secrets.TOKEN_FOR_GITEA }}" not in text
        publish_step = document["jobs"]["publish-wiki"]["steps"][-1]
        assert publish_step["env"]["WIKI_CREDENTIALS"] == "${{ secrets.TOKEN_FOR_GITEA_WIKI }}"
        assert "secrets" not in publish_step["run"]
    def test_the_scoped_workflow_runs_the_script_file(self, document):
        assert (REPO_ROOT / "tools" / "publish_wiki.py").is_file()
        steps = document["jobs"]["publish-wiki"]["steps"]
        assert "python3 - <<" not in PUBLISH_WORKFLOW.read_text(encoding="utf-8")
        assert steps[0]["uses"].startswith("actions/checkout@")
        assert steps[1]["with"] == {
            "repository": "TirSystem/github-action",
            "ref": "v1",
            "path": "shared-scripts",
        }
        assert steps[-1]["run"] == "python3 shared-scripts/tools/publish_wiki.py"
 def test_this_repository_publishes_docs_wiki_through_the_reusable_workflow():
@@ -13,7 +13,6 @@ WORKFLOW_DIRS = (
 )
 SYNC_WORKFLOW = WORKFLOW_DIRS[0] / "sync-github-metadata.yml"
 SYNC_SCRIPT = REPO_ROOT / "tools" / "sync_github_metadata.py"
 PUBLISH_WORKFLOW = WORKFLOW_DIRS[0] / "publish-wiki.yml"
 PUBLISH_SCRIPT = REPO_ROOT / "tools" / "publish_wiki.py"
 _HEREDOC = re.compile(
@@ -1,19 +1,15 @@
 """Publish the pages of a folder to the Gitea wiki of the repository.
-Run by the reusable workflow publish-wiki.yml, which a repository calls
+Run by the reusable workflow publish-wiki-pages.yml, which a repository calls
-(MIL-008), and by the scoped workflow of the same name until it is removed.
+(ADR-0009). The caller is the opt-in: the workflow sets WIKI_PRUNE and the
-The reusable workflow sets WIKI_PRUNE: the caller is the opt-in, and the
+folder must exist. It reads its settings from the environment:
 folder must exist. The scoped workflow leaves WIKI_PRUNE unset: a repository
 publishes only when it has opted in with WIKI_DIR/.publish (ADR-0004), and the
 word prune in that file lets the run delete wiki pages that are not in the
 folder. It reads its settings from the environment:
    GITEA_API_URL        Gitea API base, for example https://host/api/v1
    SOURCE_REPOSITORY    owner/repo of the repository whose wiki is written
    WIKI_CREDENTIALS     the Gitea token, as clear text (TOKEN_FOR_GITEA_WIKI)
-    WIKI_DIR             directory with the pages (default: wiki)
+    WIKI_DIR             directory with the pages (default: docs/wiki)
-    WIKI_PRUNE           true or false: delete pages that are not in the
+    WIKI_PRUNE           true or false, required: delete pages that are not in
-                         folder; when set, no .publish marker is read
+                         the folder
 Every failure is printed as ``ERROR: [category] message`` with the categories
 configuration, credentials, permissions and api; no secret value is printed.
@@ -32,8 +28,7 @@ from pathlib import Path
 PAGE_LIMIT = 50
 REQUEST_TIMEOUT_SECONDS = 30
 COMMIT_MESSAGE = "Publish wiki from the repository"
-MARKER_NAME = ".publish"
+DEFAULT_WIKI_DIR = "docs/wiki"
 PRUNE_WORD = "prune"
 class WorkflowError(RuntimeError):
@@ -81,19 +76,6 @@ def request_json(url, method="GET", headers=None, body=None):
        raise WorkflowError("api", f"Gitea API is unreachable ({error}).") from None
 def parse_marker(text):
    """Return True when the marker asks for pruning, False when it is empty."""
    word = (text or "").strip()
    if not word:
        return False
    if word == PRUNE_WORD:
        return True
    raise WorkflowError(
        "configuration",
        f"wiki/{MARKER_NAME} may only be empty or contain the word '{PRUNE_WORD}'.",
    )
 def parse_prune_setting(text):
    """Return the boolean of the WIKI_PRUNE input: true or false, nothing else."""
    word = (text or "").strip().lower()
@@ -254,27 +236,16 @@ def publish(pages, wiki_url, headers, send, prune):
 def main():
-    wiki_dir = Path(os.environ.get("WIKI_DIR", "wiki"))
+    wiki_dir = Path(os.environ.get("WIKI_DIR", DEFAULT_WIKI_DIR))
    owner, repo = split_repository(os.environ.get("SOURCE_REPOSITORY"))
-    prune_setting = os.environ.get("WIKI_PRUNE")
+    prune = parse_prune_setting(os.environ.get("WIKI_PRUNE"))
-    if prune_setting is None:
+    if not wiki_dir.is_dir():
-        marker = wiki_dir / MARKER_NAME
+        raise WorkflowError(
-        if not marker.is_file():
+            "configuration",
-            print(
+            f"The wiki folder {wiki_dir} does not exist in {owner}/{repo}; "
-                f"No {wiki_dir}/{MARKER_NAME} marker in {owner}/{repo}; "
+            "set the wiki_dir input to the folder with the pages.",
-                "wiki publishing is not enabled for this repository."
+        )
            )
            return 0
        prune = parse_marker(marker.read_text(encoding="utf-8"))
    else:
        prune = parse_prune_setting(prune_setting)
        if not wiki_dir.is_dir():
            raise WorkflowError(
                "configuration",
                f"The wiki folder {wiki_dir} does not exist in {owner}/{repo}; "
                "set the wiki_dir input to the folder with the pages.",
            )
    pages = read_pages(wiki_dir)
    token = parse_gitea_token(os.environ.get("WIKI_CREDENTIALS"))
@@ -316,12 +287,7 @@ def main():
    if result["kept"]:
        print(
            f"{len(result['kept'])} page(s) are in the wiki but not in "
-            f"{wiki_dir}/ and were kept; "
+            f"{wiki_dir}/ and were kept; set the prune input to true to delete them."
            + (
                f"put the word '{PRUNE_WORD}' in {wiki_dir}/{MARKER_NAME} to delete them."
                if prune_setting is None
                else "set the prune input to true to delete them."
            )
        )
    return 0
Author	SHA1	Message	Date
Tirsvad	6e8e5489d1	Merge pull request 'MIL-009: remove the scoped publish-wiki workflow and the marker; ADR-0004 superseded' (#151 ) from mil-009-remove-scoped into main Publish accepted milestones / publish (push) Successful in 44s Details Validate workflows / validate (push) Successful in 23s Details TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 5s Details Publish wiki / publish-wiki (push) Successful in 28s Details Publish own wiki / wiki (push) Successful in 28s Details	2026-10-14 06:15:32 +02:00
Tirsvad	8e32f48757	Resolve pending commit links Validate workflows / validate (pull_request) Successful in 27s Details TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Skipped	2026-10-14 11:45:08 +08:00
Tirsvad	78d21b34a3	Remove the scoped publish-wiki workflow and the marker path (2.0.0) - .gitea/scoped_workflows/publish-wiki.yml is deleted - tools/publish_wiki.py requires WIKI_PRUNE, reads no marker, and defaults WIKI_DIR to docs/wiki; its tests follow - README, onboarding, troubleshooting and upgrading guides, and the wiki pages in English, Danish and Bahasa Malaysia no longer describe the scoped workflow - changelog entry 2.0.0 with the Breaking group Task: MIL-009#6 Task: MIL-009#8	2026-10-14 11:45:03 +08:00
Tirsvad	22fc323b41	ADR-0004: superseded by ADR-0009; review record RC-065 The scoped delivery and the wiki/.publish marker are replaced by the reusable workflow of ADR-0009. The AI records the acceptance as stand-in for S01 (mode autonomous, not independent). Task: MIL-009#7	2026-10-14 11:45:01 +08:00
Tirsvad	878adbf148	Merge pull request 'MIL-009, PP-001 and RC-064: accepted' (#142 ) from plan-mil-009 into main TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped Publish accepted milestones / publish (push) Successful in 45s Details Validate workflows / validate (push) Successful in 22s Details TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 6s Details	2026-10-13 18:01:46 +02:00
Tirsvad	9963d69731	Resolve pending commit links TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Skipped Validate workflows / validate (pull_request) Successful in 24s Details	2026-10-14 00:00:39 +08:00
Tirsvad	2f267df2a2	MIL-009, PP-001 and RC-064: accepted The user switched to autonomous mode and accepted the plan in chat on 2026-10-14 with the defaults: target date 2026-11-30, no publishing for 027-sandbox and 028-pomodoro, framework release 0.7.0. The acceptance is recorded as AI stand-in for S01 (RC-064, mode autonomous, not independent).	2026-10-14 00:00:38 +08:00
Tirsvad	8051a07e7b	Merge pull request 'PP-001: add MIL-009 and review record RC-064' (#141 ) from plan-mil-009 into main TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped Publish accepted milestones / publish (push) Successful in 53s Details Validate workflows / validate (push) Successful in 27s Details TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 7s Details Reviewed-on: #141	2026-10-13 17:59:28 +02:00
Tirsvad	38deeba89b	Resolve pending commit link of RC-064 TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Skipped Validate workflows / validate (pull_request) Successful in 26s Details	2026-10-13 23:58:46 +08:00
Tirsvad	856197d0bb	Resolve pending commit links TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Skipped	2026-10-13 23:58:34 +08:00
Tirsvad	86e69ce85d	PP-001: add MIL-009 and review record RC-064 MIL-009 (migrate the wiki callers, remove the scoped workflow) joins the Gateway Schedule, the Gantt, Scope Coverage, Dependencies and Plan Risks. RC-064 records the review; MIL-009, the plan row and the record stay Proposed until S01 gives the Go and confirms the target date.	2026-10-13 23:58:33 +08:00
Tirsvad	bb3b0f242b	Merge pull request 'MIL-009: draft the milestone to migrate the wiki callers and remove the scoped workflow' (#140 ) from mil-009-migrate-and-remove into main TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped Publish accepted milestones / publish (push) Successful in 56s Details Validate workflows / validate (push) Successful in 25s Details TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 6s Details Reviewed-on: #140	2026-10-13 17:48:57 +02:00
Tirsvad	922ff18c0a	Resolve pending commit link of MIL-009 TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Skipped Validate workflows / validate (pull_request) Successful in 25s Details	2026-10-13 23:36:25 +08:00
Tirsvad	2b53ee6d21	MIL-009: draft the milestone to migrate the wiki callers and remove the scoped workflow Proposed. Seven repositories still publish through the scoped publish-wiki.yml with wiki/.publish; MIL-009 moves them to docs/wiki/ and a caller of publish-wiki-pages.yml, removes the scoped workflow, supersedes ADR-0004 and releases 2.0.0. The target date awaits S01.	2026-10-13 23:36:23 +08:00
Tirsvad	157bf6560d	Merge pull request 'ADR-0009 and RC-063: review and acceptance' (#139 ) from review-adr-0009 into main TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped Publish accepted milestones / publish (push) Successful in 35s Details Validate workflows / validate (push) Successful in 21s Details TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 5s Details Reviewed-on: #139	2026-10-13 17:33:55 +02:00
Tirsvad	8c0f006dc5	Resolve pending commit link of RC-063 TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Skipped Validate workflows / validate (pull_request) Successful in 24s Details	2026-10-13 23:32:52 +08:00
Tirsvad	7fecb33a72	Resolve pending commit links	2026-10-13 23:32:41 +08:00
Tirsvad	8c2c52ebd2	ADR-0009 and RC-063: review and acceptance RC-063 reviews ADR-0009 against QC-ADR-001: three findings fixed (stale verification statement, security impact named, product owner spelled out). S01 gave the Go in chat on 2026-10-13; ADR-0009 and RC-063 are Accepted.	2026-10-13 23:32:39 +08:00
Tirsvad	2ee3d4d535	Merge pull request 'PP-001 and RC-062: accepted' (#138 ) from accept-pp-001-mil-008 into main TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped Publish accepted milestones / publish (push) Successful in 33s Details Validate workflows / validate (push) Successful in 21s Details TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 5s Details Reviewed-on: #138	2026-10-13 16:43:04 +02:00
Tirsvad	8f0ded2593	Resolve pending commit links TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Skipped Validate workflows / validate (pull_request) Successful in 20s Details	2026-10-13 22:42:06 +08:00
Tirsvad	23a64a3f35	PP-001 and RC-062: accepted S01 gave the Go on the MIL-008 plan change in chat on 2026-10-13. The change was merged as pull request 137 with the plan row Proposed; this sets PP-001 and RC-062 to Accepted.	2026-10-13 22:42:04 +08:00
Tirsvad	8c1fba6d9d	Merge pull request 'PP-001: add MIL-008 and review record RC-062' (#137 ) from project-plan-mil-008 into main TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped Publish accepted milestones / publish (push) Successful in 36s Details Validate workflows / validate (push) Successful in 22s Details TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 6s Details Reviewed-on: #137	2026-10-13 16:38:52 +02:00
Tirsvad	672bc2988e	Resolve pending commit links TirSystem/github-action: Publish wiki / publish-wiki (push) Skipped TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Skipped Validate workflows / validate (pull_request) Successful in 23s Details	2026-10-13 22:37:54 +08:00
Tirsvad	9aeb74e8b0	PP-001: add MIL-008 and review record RC-062 MIL-008 (wiki publishing as a reusable workflow) joins the Gateway Schedule, the Gantt, Scope Coverage, Dependencies and Plan Risks. RC-062 records the review; the plan row stays Proposed until S01 gives the Go.	2026-10-13 22:37:52 +08:00