Complete the public facade adapter boundary

docs/roadmap/migration.md

@@ -2,7 +2,7 @@
 
 ## Status
 
-Accepted plan. Steps 1 through 3 are complete. Steps 4 through 9 remain
+Accepted plan. Steps 1 through 4 are complete. Steps 5 through 9 remain
 proposed and are not yet implemented.
 
 ## Objective
@@ -125,8 +125,8 @@ is accepted and records the required ownership and coordination decisions.
 Strengthen or add contract-focused tests where needed so extraction can be
 verified without relying on package placement.
 
-The accepted implementation scope and intended completion state are in the
-[Step 3 framework-characterization roadmap](step3.md).
+The completed Step 3 gate records the accepted implementation scope and
+intended completion state.
 
 Preserve coverage of:
 
@@ -172,6 +172,12 @@ implementations.
 **Gate:** The CLI and HTTP adapters use only the public framework API for
 framework behavior, and all tests and documented smoke commands pass.
 
+**Gate status:** Complete as of 2026-07-28. CLI `run`, `render`, and `serve`,
+the HTTP handler, and prepared-run formatting use the public facade; the
+restricted HTTP reader is injected through the public extension point. The
+dependency guard, full tests, vet, build, race checks, maintained examples, and
+configuration smoke checks passed. Step 5 repository creation is next.
+
 ### Step 5: Create The Promptkit Repository
 
 Create the Promptkit repository and Go module as an explicit out-of-band