Adds MIL-009 (migrate the wiki callers and remove the scoped workflow) to the Project Plan and records its review.
docs/project-plan.md: Gateway Schedule row (2026-11-16 to 2026-11-30, S05), Gantt entries, Scope Coverage, Dependencies (MIL-006 -> MIL-008 -> MIL-009), a plan risk for a missing organisation secret or a failed first run, and the counts. The Gitea milestone is shown as not created yet.
docs/sqa/reviews/rc-064-mil-009-plan.md: full review of MIL-009 against QC-MIL-001 plus the plan delta; all criteria pass, verdict "Go proposed".
docs/sqa/traceability-matrix.md: MIL-009 and RC-064 rows, the MIL-008 to MIL-009 link, cross references; two-row Version History kept.
Status
MIL-009, the plan row and RC-064 are Proposed. The Go is S01's and has not been given; nothing is set to Accepted here (same handling as #137 and #138).
Needs a decision from S01 before the Go
Confirm the target date 2026-11-30.
Decide whether 027-sandbox and 028-pomodoro publish too.
(S03) Confirm that TirSystem-BashScript has its own TOKEN_FOR_GITEA_WIKI secret, needed by repo-foundry.
Order
Docs only; closes no issue. Merge after the Go is recorded, or merge as Proposed and flip the statuses in a follow-up as for MIL-008. The milestone sync creates the Gitea milestone and its 8 issues only when MIL-009 is Accepted.
## What
Adds **MIL-009** (migrate the wiki callers and remove the scoped workflow) to the Project Plan and records its review.
- `docs/project-plan.md`: Gateway Schedule row (2026-11-16 to 2026-11-30, S05), Gantt entries, Scope Coverage, Dependencies (`MIL-006 -> MIL-008 -> MIL-009`), a plan risk for a missing organisation secret or a failed first run, and the counts. The Gitea milestone is shown as not created yet.
- `docs/sqa/reviews/rc-064-mil-009-plan.md`: full review of MIL-009 against `QC-MIL-001` plus the plan delta; all criteria pass, verdict "Go proposed".
- `docs/sqa/traceability-matrix.md`: MIL-009 and RC-064 rows, the MIL-008 to MIL-009 link, cross references; two-row Version History kept.
## Status
MIL-009, the plan row and RC-064 are **`Proposed`**. The Go is S01's and has not been given; nothing is set to `Accepted` here (same handling as #137 and #138).
## Needs a decision from S01 before the Go
- Confirm the target date **2026-11-30**.
- Decide whether `027-sandbox` and `028-pomodoro` publish too.
- (S03) Confirm that `TirSystem-BashScript` has its own `TOKEN_FOR_GITEA_WIKI` secret, needed by `repo-foundry`.
## Order
Docs only; closes no issue. Merge after the Go is recorded, or merge as `Proposed` and flip the statuses in a follow-up as for MIL-008. The milestone sync creates the Gitea milestone and its 8 issues only when MIL-009 is `Accepted`.
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.
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.
What
Adds MIL-009 (migrate the wiki callers and remove the scoped workflow) to the Project Plan and records its review.
docs/project-plan.md: Gateway Schedule row (2026-11-16 to 2026-11-30, S05), Gantt entries, Scope Coverage, Dependencies (MIL-006 -> MIL-008 -> MIL-009), a plan risk for a missing organisation secret or a failed first run, and the counts. The Gitea milestone is shown as not created yet.docs/sqa/reviews/rc-064-mil-009-plan.md: full review of MIL-009 againstQC-MIL-001plus the plan delta; all criteria pass, verdict "Go proposed".docs/sqa/traceability-matrix.md: MIL-009 and RC-064 rows, the MIL-008 to MIL-009 link, cross references; two-row Version History kept.Status
MIL-009, the plan row and RC-064 are
Proposed. The Go is S01's and has not been given; nothing is set toAcceptedhere (same handling as #137 and #138).Needs a decision from S01 before the Go
027-sandboxand028-pomodoropublish too.TirSystem-BashScripthas its ownTOKEN_FOR_GITEA_WIKIsecret, needed byrepo-foundry.Order
Docs only; closes no issue. Merge after the Go is recorded, or merge as
Proposedand flip the statuses in a follow-up as for MIL-008. The milestone sync creates the Gitea milestone and its 8 issues only when MIL-009 isAccepted.