Align completed forge roadmap status records

docs/roadmap/forge-boundary.md

@@ -1,6 +1,7 @@
 # Roadmap: forge delivery boundary and credential preflight
 
-Status: accepted; implementation has not started.
+Status: implementation complete; review corrections are tracked in
+[remediation](remediation.md).
 
 The [implementation plan](implementation.md) owns stages, concrete design
 choices, task sequencing, and verification.
@@ -23,10 +24,11 @@ backends remain future implementation work. The boundary should express the
 operations used by the current delivery workflow and allow refinement when a
 second backend supplies concrete requirements.
 
-## Current baseline
+## Historical planning baseline
 
-The source baseline is `ac78e7d`, following the published v0.5.0 module migration
-and the subsequent token-file and forbidden-file changes.
+The original source baseline was `ac78e7d`, following the published v0.5.0
+module migration and the subsequent token-file and forbidden-file changes.
+The following describes that revision, before implementation of this roadmap.
 
 - [delivery.go](../../delivery.go) exposes `GiteaDestination` through
   `DeliveryRequest.Destination` and converts it into `gitea.Destination`.
@@ -50,8 +52,8 @@ and the subsequent token-file and forbidden-file changes.
   request boundary. There is no dedicated authenticated credential preflight.
 
 The [Gitea integration guide](../integrations/gitea.md) and public Go declarations
-document the baseline contracts. Current behavioral tests provide regression
-coverage to assess against those contracts. The
+now describe the implemented contracts. Behavioral tests provide regression
+coverage for the selected behavior. The
 [architecture policy](../policy/architecture.md) governs facade ownership and
 dependency direction.