Release 2.1.0 documents code-metrics.yml at @v1 and defaults tools-ref to
v1, but the workflow and its scripts exist only from v2.1.0. MIL-011
plans the fix (a patch release 2.1.1), the test that would have caught
it, the guide and wiki corrections, and the removal of the workaround
from the framework Badges page. Proposed; no code changes yet.
All seven Go / No-Go criteria are met: framework v0.7.0, seven repositories
calling publish-wiki-pages.yml with 0-difference read-backs, no wiki/.publish
in 48 repositories, the scoped workflow removed, ADR-0004 superseded, 2.0.0
released with v1 left at 1.2.2. The acceptance is recorded as AI stand-in for
S01 (mode autonomous, not independent).
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
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.
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.
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.
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.
MIL-008 plans publishing the wiki through a reusable workflow that reads
docs/wiki/. ADR-0009 records the decision. RC-060 accepts the plan; RC-061
accepts the amendment that deprecates the scoped workflow instead of
removing it, because eight repositories still publish through it.
Results and review (RC-059, autonomous, AI as stand-in for S01) added to the
milestone. The guides and their wiki pages now say that clang-tidy and dotnet
print absolute paths in the workspace of the runner.
Task: MIL-007#7
Closes#101
Amends the accepted milestone with task 6 and records the review as RC-058
(autonomous, AI as stand-in for S01). The fix itself follows in a second pull
request under the Task: MIL-006#6 trailer.
Add the brief use case UC-006 (Release a Reusable Workflow), the use case in
UCD-001, stories US-001.11 to US-001.13 and ADR-0006: one version for the
repository with SemVer tags and a moving major tag, a release only from a
green commit with a changelog entry, consumers pin the major or an exact tag
and never main. Add the maintainers' checklist guides/release-process.md.
Review and accept them (RC-040 to RC-043), update TM-001 and the registry.
Task: MIL-004#1
Run against TirSystem-BashScript/RepoFoundry (39 shell files): shellcheck
passes with the project's .shellcheckrc, shfmt fails on 10 files only
because of the case indentation and passes after one .editorconfig line;
the pull request itself passes. Record the findings for the guide, review
the change (RC-039) and update TM-001. The adoption is complete when
RepoFoundry PR 76 is merged.
Task: MIL-003#4
Add the brief use case UC-005 (Run Project Quality Checks), the actor and
use case in UCD-001, stories US-001.09 and US-001.10, and ADR-0005 with the
inputs, the pinned tools and what a pass and a fail mean, based on a probe
of the runner image. Review and accept them (RC-035 to RC-038) and update
TM-001 and the registry.
Task: MIL-003#2
The sync and publish-wiki scoped workflows embed 200 to 300 lines of Python
in their YAML. Add task 6 to move them to tools/ and run them from a
checkout of this repository, as verified from two organisations, with a
Go/No-Go criterion and O2 in the traceability. Review and accept the
amendment (RC-034) and update TM-001.
Verified on 2026-10-10 with throwaway branches (deleted afterwards):
workflow_call and uses run from the same repository, another repository of
the organisation and a repository of another organisation, so MIL-003 needs
no copied-template fallback. Not tested: a private provider, secrets passed
to a called workflow, and a tag reference. Review it (RC-033) and update
TM-001.
Task: MIL-003#1
S01, standing in for S05 (ADR-0002), approves the minimum Gitea and GitHub
token permissions, recorded with the evidence from the Gitea source and the
GitHub documentation; they are still not tested with a minimal token on the
instance. Confirm the target dates of MIL-001 to MIL-006 and PP-001 (RC-026
to RC-032), update TM-001 and regenerate the Credentials wiki page with its
translations.
Task: MIL-002#4
Add the use case diagram UCD-001, the user stories US-001 and the brief use
cases UC-001 to UC-004 (Synchronize Repository Metadata, Configure Workflow
Credentials, Onboard a Repository, Diagnose a Failed Workflow). Review and
accept them (RC-019 to RC-024) and the PP-001 row that records them
(RC-025), and update TM-001 and the registry.
Task: MIL-002#1
A repository opts in with wiki/.publish; the word prune in it is the only
thing that lets the workflow delete pages. The shared workflow uses the
organisation's TOKEN_FOR_GITEA_WIKI only. Review and accept it (RC-018),
update TM-001 and link the MIL-006 milestone in PP-001.
Add milestone MIL-006 with five tasks: a scoped publish-wiki workflow with
an opt-in rule, piloted in one other repository. Schedule it in PP-001.
The milestone is Proposed; no code starts before it is accepted.
Add review record RC-015, remove JSON from the credential failures of UC
candidate 2 and the answered MIL-001 items from Open Issues, accept PP-001
and update TM-001.
ADR-0002: an artifact approved by S01 counts as approved for the other
named reviewers, with the stand-in recorded. ADR-0003: the wiki is published
with a separate TOKEN_FOR_GITEA_WIKI, dot-named titles work. Add review
records RC-013 and RC-014 and update TM-001.
English pages are generated and have no suffix; translations are named
<Page>.da and <Page>.ms, written by hand in wiki/, reviewed and checked for
staleness through a source hash. Add the ADR type to the registry.
Add milestone MIL-005 with seven tasks, schedule it in PP-001, add the wiki
to the Business Case scope and record the wiki languages in the registry.
The milestone is Proposed; no wiki work starts before it is accepted.
Adopt the SQA/QC framework as a submodule and plan the project before any
further code: Business Case, Stakeholder Analysis (S01-S05), Project Plan with
use case candidates and prioritisation, and milestones MIL-001..MIL-004
(24 tasks, synced to Gitea as milestones 18-21 and issues #1-#24).
README now separates implemented from planned capabilities, has an English
sequence diagram and points at the scoped workflow. The workflow file moves
out of the repository root and out of .gitea/workflows/; the scoped copy is
unchanged in behaviour here and still contains the known `exit 0` syntax
error, which MIL-001 fixes.
Refs #1
Refs #2
Refs #3
Refs #6
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Tirsvad
