From 0eb90b130828df2eab80b5efaf9b1bb84f98a272 Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 5 Jun 2026 15:43:14 +0200 Subject: [PATCH] Close forge rescope task --- .../RAILIANCE-WP-0006-railiance-forge-extraction.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md b/workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md index f7dc636..5a9e9f4 100644 --- a/workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md +++ b/workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md @@ -167,7 +167,7 @@ decryption, or Kubernetes apply was run. ```task id: RAILIANCE-WP-0006-T04 -status: todo +status: done priority: high state_hub_task_id: "64ac73e7-abe5-47df-abbc-51aed25a7ce4" ``` @@ -195,9 +195,12 @@ In `railiance-enablement`: Done when a new operator can answer "is this S4, S5, or forge?" from the scope documents without inspecting historical workplans. -Progress 2026-06-05: `railiance-apps/SCOPE.md` now treats forge as an upstream -service and keeps only compatibility wrappers. `railiance-enablement` still -needs the S4 handoff wording checked after the deploy move. +Completed 2026-06-05: `railiance-apps/SCOPE.md` now treats forge as an upstream +service and keeps only compatibility wrappers for moved Gitea operations. +`railiance-enablement/SCOPE.md` and `railiance-enablement/INTENT.md` now +separate reusable S4 workflow templates and paved paths from forge-owned +runtime, registries, runner substrate, labels, credentials, and artifact +evidence. ---