On a throwaway branch, code-metrics.yml at @v2 with the defaults fails
in "Validate the inputs" (tools/code-metrics.sh absent at v1, run 1499),
and a call at @v1 creates no run at all. Of the five reusable workflows
only code-metrics.yml names a tag without its script.
First read found three corrections: the wording of O5 in the
traceability, "ten milestones" in the plan's purpose, and a scope row that
is not a Business Case item. Go; accepted by the author as stand-in for
S01, not independent. MIL-011 and its plan row are Accepted; the
traceability matrix has the new rows.
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 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).
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.
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.
The user asked for the deletion of TirSystem/qc-adoption-cpp and
TirSystem/qc-adoption-csharp on 2026-10-13. The remaining action, adoption in
a real C++ and C# project, stays open.
Task: MIL-007#7
Refs #101
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.
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
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.
Tirsvad