Complete Promptkit repository foundation

docs/roadmap/migration.md

@@ -2,7 +2,7 @@
 
 ## Status
 
-Accepted plan. Steps 1 through 4 are complete. Steps 5 through 9 remain
+Accepted plan. Steps 1 through 5 are complete. Steps 6 through 9 remain
 proposed and are not yet implemented.
 
 ## Objective
@@ -182,33 +182,31 @@ creation is next.
 
 ### Step 5: Create The Promptkit Repository
 
-Create the Promptkit repository and Go module as an explicit out-of-band
-operation.
+Promptkit was established as an independent repository and Go module through
+the out-of-band workflow recorded in the
+[Step 5 completion record](step5.md). Its foundation includes:
 
-Establish:
-
-- repository access, ownership, and branch protections;
-- the module path selected by the ADR;
-- baseline development, architecture, documentation, and release policies;
+- confirmed repository access, governance, origin, and default-branch tracking;
+- module `gitea.maximumdirect.net/eric/promptkit` at Go `1.25.5`;
+- a minimal root `promptkit` public package boundary with no placeholder
+  framework packages;
+- library-specific development, architecture, documentation, testing, and
+  release policies;
 - documented maintainer-run test, vet, build, formatting, documentation-link,
   and repository-hygiene validation;
-- a tag-based release procedure for source commits and semantic Go module tags,
-  without runnable binaries or binary packaging;
-- an initial package layout centered on a small public facade with internal
-  implementation packages;
-- a local development workflow for coordinated Promptkit and Scriptorium
-  changes, using a workspace or temporary uncommitted module replacement where
-  appropriate.
+- source-commit and semantic Go module tag releases without runnable binaries
+  or binary packaging; and
+- temporary workspace and uncommitted replacement workflows for coordinated
+  development without committed repository coupling.
 
-Do not commit local filesystem `replace` directives to release branches.
 [ADR 0003](../adr/0003-use-maintainer-run-validation-and-tag-only-releases-for-promptkit.md)
 records the controlling Promptkit validation and release decision.
 
-**Gate:** The Promptkit repository exists, is accessible to maintainers, has
-documented maintainer-run validation and tag-based release procedures, has the
-required policy scaffolding, and can receive the extracted framework. Do not
-begin cross-repository extraction until this out-of-band work is confirmed
-complete.
+**Gate status:** Complete as of 2026-07-28. Promptkit passed its documented
+validation independently, all maintained links and repository-hygiene checks
+passed, and no workspace, replacement, CI configuration, binary, tag, command,
+or placeholder package was added. Framework extraction and stabilization in
+Step 6 is the next gate.
 
 ### Step 6: Extract And Stabilize Promptkit