Plans the extraction of the embedded Python of the scoped workflows into files, as task 6 of MIL-004. Documents only; no code and no workflow is changed.
Why
sync-github-metadata.yml (about 230 lines) and publish-wiki.yml (about 310 lines) embed their Python in the YAML. That is hard to read, lint and review, and the tests have to exec it out of the workflow. The cross-repository checkout needed to run a script file from this repository was verified on 2026-10-10 from TirSystem/sqa-qc-checklists and TirSystem-BashScript/RepoFoundry (throwaway branches, deleted).
Changes to MIL-004
Deliverable: names scripts as files, fetched at a reference that a release can pin.
Task 6, "Move the embedded scripts of the scoped workflows to files":tools/sync_github_metadata.py and tools/publish_wiki.py; each scoped workflow checks out TirSystem/github-action into its own folder with actions/checkout and runs the file; behaviour, messages and offline tests stay, with the tests importing the files; ref: main first, pinning defined by task 1 of the milestone.
Go/No-Go criterion 5: no embedded Python remains in those two workflows, each runs a script file, and a run in another organization passes.
Traceability: O2 added next to O4.
Review (S01 standing in as ADR-0002 records; no independent reader)
RC-034 (QC-MIL-001): 6 of 6 Pass, Go. One finding fixed: task 6 serves O2 and the Traceability table listed only O4.
TM-001 lists RC-034; registry next RC 035.
Action item (S01, 2026-11-16): decide whether consumers pin a tag or follow main for the shared scripts.
Things a reviewer should know
Every consumer then runs whatever main of this repository holds, which is the same trust as scoped delivery today.
If this repository became private, the checkout would need a token; it is public now.
Dry run of sync-project.sh --milestone MIL-004: the five existing tasks match issues #20 to #24; one new issue would be created for task 6. Nothing has been applied.
No issue closed: the task 6 issue does not exist yet.
Plans the extraction of the embedded Python of the scoped workflows into files, as task 6 of MIL-004. Documents only; no code and no workflow is changed.
## Why
`sync-github-metadata.yml` (about 230 lines) and `publish-wiki.yml` (about 310 lines) embed their Python in the YAML. That is hard to read, lint and review, and the tests have to `exec` it out of the workflow. The cross-repository checkout needed to run a script file from this repository was verified on 2026-10-10 from `TirSystem/sqa-qc-checklists` and `TirSystem-BashScript/RepoFoundry` (throwaway branches, deleted).
## Changes to MIL-004
- Deliverable: names scripts as files, fetched at a reference that a release can pin.
- **Task 6, "Move the embedded scripts of the scoped workflows to files":** `tools/sync_github_metadata.py` and `tools/publish_wiki.py`; each scoped workflow checks out `TirSystem/github-action` into its own folder with `actions/checkout` and runs the file; behaviour, messages and offline tests stay, with the tests importing the files; `ref: main` first, pinning defined by task 1 of the milestone.
- **Go/No-Go criterion 5:** no embedded Python remains in those two workflows, each runs a script file, and a run in another organization passes.
- Traceability: O2 added next to O4.
## Review (S01 standing in as ADR-0002 records; no independent reader)
- **RC-034** (QC-MIL-001): 6 of 6 Pass, Go. One finding fixed: task 6 serves O2 and the Traceability table listed only O4.
- TM-001 lists RC-034; registry next RC 035.
- Action item (S01, 2026-11-16): decide whether consumers pin a tag or follow `main` for the shared scripts.
## Things a reviewer should know
- Every consumer then runs whatever `main` of this repository holds, which is the same trust as scoped delivery today.
- If this repository became private, the checkout would need a token; it is public now.
- Dry run of `sync-project.sh --milestone MIL-004`: the five existing tasks match issues #20 to #24; one new issue would be created for task 6. Nothing has been applied.
No issue closed: the task 6 issue does not exist yet.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Plans the extraction of the embedded Python of the scoped workflows into files, as task 6 of MIL-004. Documents only; no code and no workflow is changed.
Why
sync-github-metadata.yml(about 230 lines) andpublish-wiki.yml(about 310 lines) embed their Python in the YAML. That is hard to read, lint and review, and the tests have toexecit out of the workflow. The cross-repository checkout needed to run a script file from this repository was verified on 2026-10-10 fromTirSystem/sqa-qc-checklistsandTirSystem-BashScript/RepoFoundry(throwaway branches, deleted).Changes to MIL-004
tools/sync_github_metadata.pyandtools/publish_wiki.py; each scoped workflow checks outTirSystem/github-actioninto its own folder withactions/checkoutand runs the file; behaviour, messages and offline tests stay, with the tests importing the files;ref: mainfirst, pinning defined by task 1 of the milestone.Review (S01 standing in as ADR-0002 records; no independent reader)
mainfor the shared scripts.Things a reviewer should know
mainof this repository holds, which is the same trust as scoped delivery today.sync-project.sh --milestone MIL-004: the five existing tasks match issues #20 to #24; one new issue would be created for task 6. Nothing has been applied.No issue closed: the task 6 issue does not exist yet.