docs: publish foreach back-edge semantics

docs/current_roadmap.md

@@ -795,12 +795,6 @@ stable.
 
 - Native subgraph polish: optional per-use-site child deployment overrides and
   clearer child trace inspection.
-- Active concurrent foreach correction: replace item-body `END` routes with
-  canonical back-edges to the owning foreach. The approved semantics are in the
-  [`foreach back-edge design`](superpowers/specs/2026-09-04-foreach-back-edge-design.md).
-  This slice also makes foreach control regions fail-closed, rejects unreachable
-  workflow nodes, and gives repeated visits to one foreach node distinct
-  persisted activation identities.
 - After that correction, reuse the foreach barrier/lineage machinery for
   fork/gather. The proposed control semantics are recorded in
   [`ADR-0006`](adr/0006-explicit-fork-and-topology-driven-gather.md).
@@ -942,6 +936,11 @@ stable.
   routes, or outputs. Python, JSON-RPC, MCP, and local/remote CLI surfaces are
   aligned. Implementation plan:
   [`capability step updates`](historical/superpowers/plans/2026-07-26-capability-step-update.md).
+- Completed: foreach bodies now return through validated back-edges to their
+  immediate owner, with unique static control regions and fresh persisted
+  activation identities for every dynamic visit. Design:
+  [`foreach back-edge design`](superpowers/specs/2026-09-04-foreach-back-edge-design.md).
+  Fork/gather remains explicitly deferred.
 
 Agent evaluation cohort status and policy: