2026-10-27 16:34:30 +01:00
6 changed files with 315 additions and 13 deletions
@@ -0,0 +1,101 @@
 # ADR-0013: Wiki publishing as a scoped workflow
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | ADR-0013 |
 | CrossReference | [MIL-014], [ADR-0009], [ADR-0004] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-27 | Accepted | Jens Tirsvad Nielsen | S01 | Initial version; Accepted on a Go review (RC-086); accepted by the author in chat on 2026-10-27 as stand-in for S01, not independent | pending |
 Allowed Status values: `Proposed`, `Accepted`, `Rejected`, `Deprecated`, `Superseded by ADR-NNNN`.
 ---
 ## Context
 [ADR-0004] published wikis with a scoped workflow and a marker file
 `wiki/.publish`. [ADR-0009] replaced it with the reusable workflow
 `publish-wiki-pages.yml`, because the marker was an opt-in the workflow had to
 guard, and a repository needed to say where its wiki is. Since then the folder
 is settled: the framework prescribes the wiki in `docs/wiki/`, and every
 publishing repository uses the defaults. Seven repositories carry a caller file
 with the same trigger and the same secret, and the only setting a caller adds
 to the defaults is `prune`; each caller is a file to keep current when the
 workflow changes.
 Options:
 1. **Keep the reusable workflow.** Explicit opt-in per repository, but a caller
   file per repository that repeats the same trigger and the same secret.
 2. **A scoped workflow that runs in every repository and publishes when
   `docs/wiki/` exists.** Nothing to copy or call; the opt-in is the folder
   itself, which is also what the content is.
 3. **A scoped workflow with a marker file.** The marker was the thing
   [ADR-0009] removed; the folder says the same thing.
 ## Decision
 Wiki publishing is the scoped workflow `.gitea/scoped_workflows/publish-wiki-pages.yml`,
 which runs in every repository and publishes `docs/wiki/` when the folder
 exists; the reusable workflow, its inputs and the caller files are removed.
 The rules that follow from it:
 - The settings are fixed, not inputs: the folder is `docs/wiki`, pruning is off,
  and the script is fetched from this repository at the current major tag.
 - The secret `TOKEN_FOR_GITEA_WIKI` is read from the organization secrets of the
  running repository; there is no fallback to another token.
 - The workflow runs on a push to `main` that changes `docs/wiki/**`, and
  manually, and ends without doing anything when the folder does not exist.
 - Pages that are in the wiki but not in the folder are kept, so a repository
  that needs pruning removes them by hand.
 - The script, the page-title rules, the empty-folder protection and the error
  categories of [ADR-0004] and [ADR-0003] are unchanged.
 ## Consequences
 **Positive:**
 - Nothing to add to a repository: a folder `docs/wiki/` is the whole opt-in, and
  there is one workflow to maintain instead of one plus seven callers.
 - A change to the workflow reaches every repository at once, the way the
  metadata sync does.
 **Negative:**
 - Security: every repository of an organization that has `docs/wiki/` can write
  its own wiki with the organization token. A repository that must not publish
  has to disable its wiki or not use the folder; before the release a scan names
  the repositories that would start publishing (`027-sandbox` and `028-pomodoro`
  did not in MIL-009).
 - A repository cannot choose another folder or prune; the repositories whose
  caller sets `prune: "true"` lose that, and a page deleted from `docs/wiki/`
  then stays in the wiki. One that needs either stays on `@v2` of the reusable
  workflow, which keeps working because the `v2` tag is not moved.
 - Removing the reusable workflow is a breaking change under [ADR-0006]: release
  3.0.0. A repository that keeps its caller at `@v3` fails and one that keeps
  both publishes twice, so the callers are removed first (MIL-014 task 5).
 - A scoped workflow cannot be pinned by a repository and follows the major tag
  of the script; a faulty script release reaches all repositories until the tag
  is moved back.
 - It reverses a decision reached two weeks earlier ([ADR-0009]) and the
  framework template `templates/ci/publish-wiki.yml` is retired with it.
 ## Affected Artifacts
 - [MIL-014] — the plan this decision belongs to.
 - [ADR-0009] — its delivery and caller parts are replaced; its token rule and
  the amendment of the `tools-ref` default stand as history for `@v2`.
 - [ADR-0004] — its token and safety rules stand; its marker is not restored.
 ---
 [MIL-014]: ../milestones/mil-014-wiki-publishing-scoped-again.md
 [ADR-0003]: ./adr-0003-wiki-publish-token.md
 [ADR-0004]: ./adr-0004-shared-wiki-publishing-opt-in.md
 [ADR-0006]: ./adr-0006-release-process-and-version-pinning.md
 [ADR-0009]: ./adr-0009-wiki-publishing-reusable-workflow.md
@@ -10,10 +10,10 @@ 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 | 014 |
+| MIL | Milestone / Gateway | docs/milestones/*.md | 015 |
-| RC | SQA Review Record | docs/sqa/reviews/rc-*.md | 086 |
+| RC | SQA Review Record | docs/sqa/reviews/rc-*.md | 087 |
 | TM | Traceability Matrix | docs/sqa/traceability-matrix.md | 002 |
-| ADR | Architecture Decision Record | docs/adr/adr-NNNN-*.md | 0013 |
+| ADR | Architecture Decision Record | docs/adr/adr-NNNN-*.md | 0014 |
 | UCD | Use Case Diagram | docs/use-case-diagram.md | 002 |
 | US | User Story | docs/user-stories.md | 002 |
 | UC | Use Case | docs/uc-NNN/uc.md | 009 |
@@ -0,0 +1,94 @@
 # MIL-014: Publish wiki pages as a scoped workflow
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | MIL-014 |
 | CrossReference | [BC-001], [MIL-009], [ADR-0004], [ADR-0009], [ADR-0013], [RC-086] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-27 | Accepted | Jens Tirsvad Nielsen | S01 | Initial version; Accepted on a Go review (RC-086); accepted by the author in chat on 2026-10-27 as stand-in for S01, not independent | pending |
 ---
 ## Purpose
 Decide whether wiki publishing returns to a scoped workflow: the instance runs
 `publish-wiki-pages.yml` in every repository of the organizations, and a
 repository opts in by having a `docs/wiki/` folder. MIL-008 and MIL-009 replaced
 the scoped workflow by a reusable one that each of seven repositories calls; the
 owner now wants the call and the caller file gone, because the folder
 `docs/wiki/` is already the convention of the framework and a caller file adds
 nothing a repository decides. This reverses part of [ADR-0009].
 ## Deliverable
 The scoped workflow `.gitea/scoped_workflows/publish-wiki-pages.yml` (already
 written in the working tree, with its tests and the guides, README and wiki
 pages in three languages); the reusable workflow and this repository's own
 caller removed; [ADR-0013] accepted and [ADR-0009] marked superseded; the seven
 repositories that call the reusable workflow have dropped their caller; the
 framework template `templates/ci/publish-wiki.yml` retired in the framework
 repository; and the major release 3.0.0 with the tag `v3`.
 ## Go / No-Go Criteria
 | # | Criterion (objectively checkable) | Go | No-Go |
 | --- | --- | --- | --- |
 | 1 | The scoped workflow runs in a repository with `docs/wiki/` and ends without publishing in one without | A run in this repository publishes; a run in a test repository without the folder succeeds and logs that there is nothing to publish | Either run fails, or the second one writes a wiki |
 | 2 | The wiki of this repository equals `docs/wiki/` after the first run, and pages that are only in the wiki are kept | 0 differences read back through the API for the pages in the folder | A difference, or a deleted page |
 | 3 | The organization secret `TOKEN_FOR_GITEA_WIKI` is available to the scoped run in each organization that has a repository with `docs/wiki/` | A scan lists each such organization with the secret present | A repository with the folder and no secret that is not named as an accepted failure |
 | 4 | A scan of the four organizations lists every repository with `docs/wiki/` that has no wiki enabled, or where the first run would write unwanted pages (for example `027-sandbox` and `028-pomodoro`, which MIL-009 decided must not publish) | Each such repository is named and resolved (wiki disabled, folder renamed or owner accepts publishing) before the release | A repository would publish that its owner did not accept |
 | 5 | The reusable workflow, this repository's caller, and every mention of calling it are removed; the tests, README, guides and the three wiki languages describe the scoped workflow | Offline tests pass and `python tools/build_wiki.py --check` is clean | A mention remains, or a test fails |
 | 6 | [ADR-0013] is `Accepted` with a review record, [ADR-0009] is `Superseded by ADR-0013` with a review record, and [ADR-0013] links back | Both rows and the `RC-*` records present | Missing |
 | 7 | The seven repositories no longer call `publish-wiki-pages.yml`, and each wiki still equals its `docs/wiki/` after the first scoped run | 0 differences for each, and no caller workflow found by the scan | A caller remains, or a difference |
 | 8 | The framework has retired `templates/ci/publish-wiki.yml` and `process/wiki.md` describes the scoped workflow, released as a tag that this project pins | The tag exists and this project pins it | The pin is an unmerged commit |
 | 9 | Release 3.0.0 is published with a Breaking entry, `v3` points to it, and `v2` still points to the last 2.x release | Tags read back through the API | `v2` moved, or no Breaking entry |
 ## Dependencies
 | Depends on | Reason |
 | --- | --- |
 | MIL-009 | Removed the first scoped workflow, migrated the seven callers and set the list of repositories this milestone migrates back |
 | MIL-013 | Release 2.3.0 comes first, so the 3.0.0 release carries one breaking change and nothing else |
 | `TirSystem/sqa-qc-framework` release | `process/wiki.md` and the CI template 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-27 — proposed after MIL-013 (2026-11-20); the Business Case sets no deadline, and S01 confirms the date when accepting the plan.
 ## Tasks
 | # | Task | Summary | Needs its own Use Case/User Story? | Reference |
 | --- | --- | --- | --- | --- |
 | 1 | Record the decision | Write [ADR-0013] (wiki publishing as a scoped workflow, with the opt-in, the fixed settings and the security consequence of a token that every repository of an organization can reach) and review it. Mark [ADR-0009] `Superseded by ADR-0013` for the delivery and caller parts, with a review record, once [ADR-0013] is accepted. | No | [ADR-0013] |
 | 2 | Check the instance | Verify on this Gitea instance that a scoped workflow with a `paths:` filter fires only on a push that changes `docs/wiki/**`, that the organization secret reaches a scoped run, how the file in `.gitea/scoped_workflows/` reaches the instance (S03), and list every repository of the four organizations that has `docs/wiki/`, its wiki setting and whether its owner wants it published (`027-sandbox` and `028-pomodoro` did not in MIL-009). | No | |
 | 3 | Make the repository change | Review the working-tree change (scoped workflow, removed reusable workflow and caller, `tools/publish_wiki.py` message, tests, fixtures, README, guides, wiki pages in three languages) and merge it; confirm the first run on `main` publishes and a repository without the folder is skipped. | No | |
 | 4 | Move the framework | In `TirSystem/sqa-qc-framework` retire `templates/ci/publish-wiki.yml`, rewrite `process/wiki.md` and the install guide for the scoped workflow, add the changelog entry and tag the release; then this project moves the submodule pin to the tag. | No | |
 | 5 | Remove the callers | In each of `sqa-and-qc`, `sqa-qc-framework`, `sqa-qc-checklists`, `repo-foundry`, `021-snake-game`, `024-snake` and `025-weather`: delete the caller workflow (it would publish twice), keep `docs/wiki/`, one pull request each. Do this only after task 3 is merged and released, so no repository is left without publishing. | No | |
 | 6 | Verify the migration | After each first scoped run read the wiki back and compare it with `docs/wiki/`; scan the four organizations for callers of `publish-wiki-pages.yml` and for repositories whose wiki would be written without their owner's agreement. Record the results in this milestone. | No | |
 | 7 | Release 3.0.0 | Breaking entry (a removed reusable workflow and its inputs); upgrade guide for callers: remove the call and rely on the scoped workflow; release through the release workflow; `v3` is created and `v2` stays at the last 2.x release, so a caller still pinned at `@v2` keeps working. Move the examples in the guides to `@v3` where they describe the new major. | No | |
 ---
 [BC-001]: ../business-case.md
 [MIL-009]: ./mil-009-migrate-wiki-callers-and-remove-scoped-workflow.md
 [ADR-0004]: ../adr/adr-0004-shared-wiki-publishing-opt-in.md
 [ADR-0009]: ../adr/adr-0009-wiki-publishing-reusable-workflow.md
 [ADR-0013]: ../adr/adr-0013-wiki-publishing-scoped-workflow.md
 [RC-086]: ../sqa/reviews/rc-086-adr-0013-mil-014-pp-001.md
@@ -4,19 +4,19 @@
 | 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], [MIL-008], [MIL-009], [MIL-010], [MIL-011], [MIL-012], [MIL-013] |
+| 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], [MIL-010], [MIL-011], [MIL-012], [MIL-013], [MIL-014] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
-| 2026-10-19 | Deprecated | Jens Tirsvad Nielsen | S01 | Added MIL-012 (VPN actions for deployment); reviewed (RC-080), accepted by the author in chat as stand-in for S01 | [c5d5941] |
+| 2026-10-19 | Deprecated | Jens Tirsvad Nielsen | S01 | Added MIL-013 (source code comments are in English); reviewed (RC-083), accepted by the author in chat as stand-in for S01 | [e35b1c5] |
-| 2026-10-19 | Accepted | Jens Tirsvad Nielsen | S01 | Added MIL-013 (source code comments are in English); reviewed (RC-083), accepted by the author in chat as stand-in for S01 | [e35b1c5] |
+| 2026-10-27 | Accepted | Jens Tirsvad Nielsen | S01 | Added MIL-014 (wiki publishing as a scoped workflow, reversing part of ADR-0009); reviewed (RC-086), accepted by the author in chat as stand-in for S01 | pending |
 ---
 ## Purpose
-This plan schedules thirteen milestones that move the repository from one
+This plan schedules fourteen 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).
@@ -25,6 +25,7 @@ workflows. The Business Case sets no deadline, so the dates are the plan's own;
 - 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. MIL-010 (code metrics and coverage badges) follows MIL-007 in January 2027, from 2027-01-18 to its Target Date, 2027-01-30, accepted by the user in chat on 2026-10-14.
 - MIL-012 (VPN actions for deployment) runs from 2026-10-26 to its Target Date, 2026-11-06, proposed by the author and accepted by S01 in chat on 2026-10-19; it overlaps MIL-002 and MIL-003, which do not touch the runners' network.
 - MIL-013 (source code comments are in English) runs from 2026-11-09 to its Target Date, 2026-11-20, proposed by the author and accepted by S01 in chat on 2026-10-19; it overlaps MIL-009, whose work is on wiki callers and does not touch the runners or the reviewer of the check.
 - MIL-014 (publish wiki pages as a scoped workflow) runs from 2026-11-23 to its Target Date, 2026-11-27, proposed by the author; it follows MIL-013 so that release 3.0.0 carries one breaking change, and it reverses part of ADR-0009. S01 confirms the dates when accepting it.
 - 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).
@@ -45,6 +46,7 @@ workflows. The Business Case sets no deadline, so the dates are the plan's own;
 | Fix the defaults of the code metrics workflow | [MIL-011] | 2026-10-14 to 2026-10-23 | 2026-10-23 | S05 | None (technical tasks) | Patch release 2.1.1: the default `tools-ref` of every reusable workflow names a tag that holds its scripts, a test for it, guides and wiki at `@v2`, the framework Badges page without the workaround | Not created yet (the sync creates it when MIL-011 is Accepted) |
 | VPN actions for deployment | [MIL-012] | 2026-10-26 to 2026-11-06 | 2026-11-06 | S05 | None (technical tasks) | Release 2.2.0: composite actions `connect-wireguard` and `connect-tailscale` verified on a runner of the instance, with guides, wiki in three languages and the framework templates pinned to the release | Not created yet (the sync creates it when MIL-012 is Accepted) |
 | Source code comments are in English | [MIL-013] | 2026-11-09 to 2026-11-20 | 2026-11-20 | S05 | None (technical tasks) | Release 2.3.0: reusable workflow `english-comments.yml` that fails a pull request with a non-English comment and tells the author, with its ADR, tests, guides and wiki, and the rule proposed in the framework | Not created yet (the sync creates it when MIL-013 is Accepted) |
 | Publish wiki pages as a scoped workflow | [MIL-014] | 2026-11-23 to 2026-11-27 | 2026-11-27 | S05 | None (technical tasks) | Release 3.0.0: scoped publish-wiki-pages workflow opted into by the docs/wiki folder, reusable workflow and the seven callers removed, ADR-0009 superseded | Not created yet (the sync runs after acceptance) |
 ```plantuml
@startgantt
@@ -75,6 +77,8 @@ Project starts 2026-10-05
 [MIL-012 Go/No-Go] happens 2026-11-06
 [MIL-013 English comments] starts 2026-11-09 and ends 2026-11-20
 [MIL-013 Go/No-Go] happens 2026-11-20
 [MIL-014 Scoped wiki] starts 2026-11-23 and ends 2026-11-27
 [MIL-014 Go/No-Go] happens 2026-11-27
@endgantt
 ```
@@ -94,6 +98,7 @@ Project starts 2026-10-05
 | A shared workflow for code metrics and coverage badges | [MIL-010], [MIL-011] |
 | Shared composite actions that connect a deployment job to a private network through WireGuard or Tailscale | [MIL-012] |
 | A shared workflow that checks that comments in source code are in English and tells the author | [MIL-013] |
 | The wiki publisher as a scoped workflow again, opt-in by the docs/wiki folder, without callers | [MIL-014] |
 ## Dependencies
@@ -105,6 +110,7 @@ MIL-001 → MIL-002 → MIL-003 → MIL-004
   MIL-003 + MIL-004 → MIL-010 → MIL-011
   MIL-004 + MIL-011 → MIL-012
   MIL-004 + MIL-010 + MIL-011 → MIL-013
                 MIL-009 + MIL-013 → MIL-014
 ```
 A No-Go moves every later window by the rework time of the failed milestone.
@@ -120,11 +126,11 @@ A No-Go moves every later window by the rework time of the failed milestone.
 | The token of a run cannot push to a `badges` branch, or the SVG does not render on the mirror (MIL-010) | The delivery of the badges changes shape | MIL-010 task 3 verifies it first; fall back to a badge file in a path of the default branch or to a run artifact. |
 | The runner cannot give a job `NET_ADMIN` and `/dev/net/tun`, or `tailscaled` does not survive to the next step (MIL-012) | The actions need another shape (a different start of the daemon, or userspace mode only) | MIL-012 tasks 2 to 4 verify it first on a runner of the instance; the release waits for criteria 2 and 3. |
 | The check calls a correct comment non-English, or misses a Danish or Malay one (MIL-013) | Authors lose trust in the check, or it is turned off | MIL-013 tasks 1 and 2 measure the method on a corpus before anything is built, and the exception marker and the allowed-words file (criterion 4) take care of the rest. |
 | A repository with a `docs/wiki/` folder starts publishing a wiki its owner did not want, or its first scoped run fails (MIL-014) | An unwanted wiki is written with the organization token, or a wiki stops updating | MIL-014 tasks 2 and 6 list every repository with the folder before the release and read each wiki back after its first run; the reusable workflow stays at `v2` for a repository that needs it. |
 | Security review by S05 is a bottleneck | Milestone decisions slip | Keep milestones small and plan review time before each decision date. |
 ## Open Issues
 - No QC checklist exists for the Project Plan.
 - The P1 candidates are written as brief use cases (UC-001 to UC-004) with a use case diagram (UCD-001) and user stories (US-001). The P2 and P3 candidates have no use case document yet.
 ## Appendix: Use Case Candidates and Prioritisation
@@ -298,6 +304,7 @@ no tests, no release process.
 [MIL-011]: ./milestones/mil-011-code-metrics-default-tools-ref.md
 [MIL-012]: ./milestones/mil-012-vpn-actions-for-deployment.md
 [MIL-013]: ./milestones/mil-013-english-comments-check.md
 [MIL-014]: ./milestones/mil-014-wiki-publishing-scoped-again.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
@@ -0,0 +1,95 @@
 # Review Record: ADR-0013, MIL-014 and PP-001 (MIL-014)
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | RC-086 |
 | CrossReference | [ADR-0013], [MIL-014], [PP-001], [QC-ADR-001], [QC-MIL-001], [QC-PP-001] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-27 | Accepted | Jens Tirsvad Nielsen | S01 | Initial version; accepted by the author in chat on 2026-10-27 as stand-in for S01, after the corrections listed under Overall Verdict | pending |
 ---
 ## Artifact Under Review
 - Instances reviewed: [ADR-0013], [MIL-014]; delta of [PP-001] for the added milestone
 - Checklists used: [QC-ADR-001], [QC-MIL-001], [QC-PP-001]
 - Scope: full review of ADR-0013 and MIL-014; delta re-review of PP-001 (criteria 2, 3, 4, 5, 8, 10, 11, 12, 13, 14 and 15, the ones the added milestone touches), earlier record [RC-083]
 - Language and domain: n/a (technical types)
 - Language reviewer: none
 - Mode: supervised, not independent (the author, Jens Tirsvad Nielsen, accepted the plan and its dates in chat on 2026-10-27 and stands in for S01; the AI prepared the evidence)
 ## Checklist Results
 ADR-0013 against [QC-ADR-001]:
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | The ID matches the filename number and is unique and sequential | Pass | `ADR-0013` in `adr-0013-wiki-publishing-scoped-workflow.md`; the registry's next ADR is 0014. |
 | 2 | Context states the problem, the forces and the options evaluated | Pass | The callers repeat the same trigger and secret; the folder is already the framework convention; three options. |
 | 3 | At least two options were considered | Pass | Keep the reusable workflow; scoped with the folder as opt-in; scoped with a marker. |
 | 4 | Decision is unhedged, in one or two sentences, and matches an evaluated option | Pass | The first read found three sentences; the decision is now one sentence and matches option 2. The rules that follow it are a list. |
 | 5 | Consequences list Positive and Negative outcomes | Pass | Two positive, five negative. |
 | 6 | Quality-attribute impacts are named | Pass | Security (every repository with the folder can write its wiki with the organization token), compatibility (breaking change, `v2` kept), maintainability (one workflow instead of one plus seven callers). |
 | 7 | Affected Artifacts are links and are in CrossReference | Pass | MIL-014, ADR-0009, ADR-0004 are in both. |
 | 8 | Status changes are new Version History rows | Pass | One row; nothing rewritten. |
 | 9 | A superseded ADR names its successor, and the successor links back | N-A | ADR-0013 names ADR-0009 as replaced in part; the row `Superseded by ADR-0013` in ADR-0009 is task 1 of MIL-014, done after this acceptance. |
 | 10 | Written in the language of the domain, no unexplained abbreviations | Pass | |
 | 11 | Status values are from the allowed set | Pass | `Accepted`. |
 MIL-014 against [QC-MIL-001]:
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | A concrete deliverable is defined for every gate | Pass | The scoped workflow, the removals, the two ADR states, the seven callers dropped, the framework template retired, release 3.0.0 with `v3`. |
 | 2 | Explicit Go/No-Go criteria | Pass | Nine criteria, each checkable (a run, a scan, a read-back through the API, a tag). |
 | 3 | Dependencies are mapped | Pass | MIL-009, MIL-013 and the framework release; the instance delivery of the file is made a check in task 2. |
 | 4 | Traceable to a Business Case objective | Pass | O2 and O3 of [BC-001], as in MIL-009. |
 | 5 | Owner and approving reviewer | Pass | S05 and S01, both in [SA-001]. |
 | 6 | Target date consistent with the constraints | Pass | 2026-11-27, accepted by the author in chat on 2026-10-27; the Business Case sets no deadline. It follows MIL-013 (2026-11-20). |
 PP-001 delta against [QC-PP-001]:
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 2 | Every gateway is listed once with document, decision date and owner | Pass | Schedule row: [MIL-014], 2026-11-27, S05. |
 | 3 | Decision dates agree with the `MIL-*` document | Pass | 2026-11-27 in the plan, the Gantt and the Target Date of MIL-014. |
 | 4 | Every in-scope item has a gateway | Pass | Scope row "The wiki publisher as a scoped workflow again, opt-in by the docs/wiki folder, without callers". |
 | 5 | Dependencies are stated, acyclic and in schedule order | Pass | `MIL-009 + MIL-013 -> MIL-014`; MIL-014 is decided after both. |
 | 8 | Assumptions are listed with their source | Pass | A planning assumption names the dates, that the author proposed them and the reversal of ADR-0009. |
 | 10 | Open issues are current | Pass | The first read found the entry "No QC checklist exists for the Project Plan", stale since [QC-PP-001] exists (framework v0.17.0); removed. |
 | 11 | The plan deliverable matches the `MIL-*` deliverable | Pass | Both say release 3.0.0, the scoped workflow, the removal of the reusable workflow and the seven callers, ADR-0009 superseded. |
 | 12 | Gateways name their user stories or say why not | Pass | "None (technical tasks)". |
 | 13 | Schedule view and dependency view agree | Pass | Table, Gantt bar and dependency line all carry MIL-014. |
 | 14 | Each gateway links to its tracker milestone or is marked not synced | Pass | "Not created yet (the sync runs after acceptance)"; the dry run of `sync-project.sh --milestone MIL-014` lists one Milestone and seven Issues. |
 | 15 | The plan is a singleton and changes are in Version History | Pass | New row; the two latest are kept. |
 The Purpose of the plan said "thirteen" milestones; the first read changed it to "fourteen". A plan risk for the new milestone was added (a repository starting to publish a wiki its owner did not want, or a failed first run).
 ## Overall Verdict
 Go. Corrections made in the first read: the decision of ADR-0013 shortened to one sentence; the claim that callers set nothing but defaults replaced by the fact that a caller may set `prune` (and the loss of pruning added as a negative consequence); "four weeks earlier" corrected to two; the stale open issue and the milestone count of the plan. The author accepted the plan and the dates in chat on 2026-10-27 as stand-in for S01; this is not an independent review.
 ## Action Items
 | Action | Owner | Due |
 | --- | --- | --- |
 | Confirm this record by S01 when an independent reading is possible | S01 | 2026-11-06 |
 | Mark ADR-0009 `Superseded by ADR-0013` with a review record (MIL-014 task 1); until then ADR-0009 and ADR-0013 both read `Accepted` | S05 | Before the pull request merges |
 | Verify that a scoped workflow with a `paths:` filter fires on this instance, that the organization secret reaches it, and how the file reaches the instance (MIL-014 task 2) | S03 | 2026-11-23 |
 | Decide for each repository with `docs/wiki/` whether it publishes (`027-sandbox`, `028-pomodoro`) before task 5 | S01 | 2026-11-23 |
 ---
 [ADR-0013]: ../../adr/adr-0013-wiki-publishing-scoped-workflow.md
 [MIL-014]: ../../milestones/mil-014-wiki-publishing-scoped-again.md
 [PP-001]: ../../project-plan.md
 [BC-001]: ../../business-case.md
 [SA-001]: ../../stakeholder-analysis.md
 [RC-083]: ./rc-083-mil-013-plan.md
 [QC-ADR-001]: ../../../framework/qc/artifacts/qc-adr.md
 [QC-MIL-001]: ../../../framework/qc/artifacts/qc-milestones-gateways.md
 [QC-PP-001]: ../../../framework/qc/artifacts/qc-project-plan.md
@@ -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], [MIL-009], [MIL-010], [MIL-011], [MIL-012], [MIL-013], [ADR-0011], [ADR-0012], [UC-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], [RC-061], [RC-062], [RC-063], [RC-064], [RC-065], [RC-066], [RC-067], [RC-068], [RC-069], [RC-070], [RC-071], [RC-072], [RC-073], [RC-074], [RC-075], [RC-076], [RC-077], [RC-078], [RC-079], [RC-080], [RC-081], [RC-082], [RC-083], [RC-084], [RC-085], [ADR-0007], [ADR-0008], [ADR-0009], [ADR-0010], [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], [MIL-010], [MIL-011], [MIL-012], [MIL-013], [MIL-014], [ADR-0011], [ADR-0012], [ADR-0013], [UC-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], [RC-061], [RC-062], [RC-063], [RC-064], [RC-065], [RC-066], [RC-067], [RC-068], [RC-069], [RC-070], [RC-071], [RC-072], [RC-073], [RC-074], [RC-075], [RC-076], [RC-077], [RC-078], [RC-079], [RC-080], [RC-081], [RC-082], [RC-083], [RC-084], [RC-085], [ADR-0007], [ADR-0008], [ADR-0009], [ADR-0010], [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-19 | Proposed | Jens Tirsvad Nielsen | S01 | Added MIL-013 (English comments check), RC-083 and RC-084 (its plan and objective O7) | [e35b1c5] |
 | 2026-10-21 | Proposed | Jens Tirsvad Nielsen | S01 | Added ADR-0012 and RC-085 (MIL-013 results of the trial) | [88f852a] |
 | 2026-10-27 | Proposed | Jens Tirsvad Nielsen | S01 | Added MIL-014 (scoped wiki publishing), ADR-0013 and RC-086 (their review) | pending |
 ---
@@ -25,8 +25,8 @@ updated whenever an artifact instance is created or reviewed.
 | Artifact Instance | Type | Upstream (Backward Link) | Downstream (Forward Link) | Last Reviewed (RC-ID) |
 | --- | --- | --- | --- | --- |
 | [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], [MIL-012], [MIL-013] | [RC-001], [RC-008], [RC-067], [RC-081], [RC-084] |
+| [BC-001] | BC | [SA-001] | [PP-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004], [MIL-005], [MIL-006], [MIL-012], [MIL-013], [MIL-014] | [RC-001], [RC-008], [RC-067], [RC-081], [RC-084] |
-| [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], [MIL-010], [MIL-011], [MIL-012], [MIL-013], [US-001] | [RC-002], [RC-009], [RC-015], [RC-017], [RC-025], [RC-032], [RC-053], [RC-062], [RC-064], [RC-068], [RC-080], [RC-083] |
+| [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], [MIL-010], [MIL-011], [MIL-012], [MIL-013], [MIL-014], [US-001] | [RC-002], [RC-009], [RC-015], [RC-017], [RC-025], [RC-032], [RC-053], [RC-062], [RC-064], [RC-068], [RC-080], [RC-083], [RC-086] |
 | [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] |
@@ -34,6 +34,7 @@ updated whenever an artifact instance is created or reviewed.
 | [ADR-0010] | ADR | [MIL-010], [UC-008], [US-001], [ADR-0005], [ADR-0006] | - | [RC-072], [RC-073] |
 | [ADR-0011] | ADR | [MIL-012], [ADR-0005], [ADR-0006] | - | - |
 | [ADR-0012] | ADR | [MIL-013], [ADR-0005], [ADR-0010] | - | - |
 | [ADR-0013] | ADR | [MIL-014], [ADR-0009], [ADR-0004] | - | [RC-086] |
 | [RC-001] | RC | [BC-001] | - | - |
 | [RC-002] | RC | [PP-001] | - | - |
 | [RC-003] | RC | [MIL-001] | - | - |
@@ -49,6 +50,7 @@ updated whenever an artifact instance is created or reviewed.
 | [MIL-011] | MIL | [BC-001], [PP-001], [MIL-010], [ADR-0006], [ADR-0010] | [MIL-012] | [RC-076], [RC-077], [RC-078], [RC-079] |
 | [MIL-012] | MIL | [BC-001], [PP-001], [MIL-004], [MIL-011], [ADR-0006], [ADR-0011] | - | [RC-080], [RC-082] |
 | [MIL-013] | MIL | [BC-001], [PP-001], [MIL-004], [MIL-010], [MIL-011], [ADR-0005], [ADR-0006], [ADR-0010] | - | [RC-083], [RC-085] |
 | [MIL-014] | MIL | [BC-001], [PP-001], [MIL-009], [MIL-013], [ADR-0004], [ADR-0009], [ADR-0013] | - | [RC-086] |
 | [RC-007] | RC | [MIL-004] | - | - |
 | [RC-008] | RC | [BC-001] | - | - |
 | [RC-009] | RC | [PP-001] | - | - |
@@ -147,6 +149,7 @@ updated whenever an artifact instance is created or reviewed.
 | [RC-083] | RC | [MIL-013], [PP-001] | - | - |
 | [RC-084] | RC | [BC-001] | - | - |
 | [RC-085] | RC | [MIL-013] | - | - |
 | [RC-086] | RC | [ADR-0013], [MIL-014], [PP-001] | - | - |
 ## Coverage Notes
@@ -176,6 +179,9 @@ updated whenever an artifact instance is created or reviewed.
 [ADR-0010]: ../adr/adr-0010-code-metrics-badges-contract.md
 [ADR-0011]: ../adr/adr-0011-vpn-composite-actions.md
 [ADR-0012]: ../adr/adr-0012-english-comment-detection.md
 [ADR-0013]: ../adr/adr-0013-wiki-publishing-scoped-workflow.md
 [MIL-014]: ../milestones/mil-014-wiki-publishing-scoped-again.md
 [RC-086]: ./reviews/rc-086-adr-0013-mil-014-pp-001.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
@@ -281,5 +287,4 @@ updated whenever an artifact instance is created or reviewed.
 [UC-005]: ../uc-005/uc.md
 [ADR-0005]: ../adr/adr-0005-quality-check-contract.md
 [3d7a9df]: https://git.tirsystem.com/TirSystem/github-action/commit/3d7a9df3a3a4712dcc5214a71b0569d90122bf4e
 [e35b1c5]: https://git.tirsystem.com/TirSystem/github-action/commit/e35b1c56748a50430503f5518602469f93262357
 [88f852a]: https://git.tirsystem.com/TirSystem/github-action/commit/88f852af9398468b91e88fe0190ce5c35dcf0fa2