Complete implementation handoff documentation

docs/roadmap/policy.md

@@ -1,8 +1,8 @@
 # Adopt the policy framework
 
-Status: Policy adoption complete. Source publication and its maintainer runbook
-are implemented; no ReleaseKit release has been published. Executable delivery
-remains pending.
+Status: Policy adoption complete. Source publication, its maintainer runbook,
+and prepared hosted note-page delivery are implemented; no ReleaseKit release
+has been published. Binary distribution remains deferred.
 
 Date: 2026-10-05
 
@@ -130,8 +130,9 @@ policy has separate defaults for applications and libraries.
 
 - [x] Adopt the general versioning, compatibility, integrity, immutability, and
   successful-tag-push completion rules.
-- [x] Select source only as ReleaseKit's initial deliverable in the release
-  policy. Supporting downstream cross-builds does not declare ReleaseKit binaries.
+- [x] Select the immutable source tag as the source-completion point and the
+  hosted note page as a separate asynchronous deliverable. Supporting downstream
+  cross-builds does not declare ReleaseKit binaries.
 - [x] Add `docs/release.md` alongside the first working publication command,
   documenting real prerequisites, authoritative remote, branch, validation,
   publication, and failure recovery.
@@ -145,8 +146,8 @@ policy has separate defaults for applications and libraries.
   separate. This task is deferred unless executable deliverables are selected.
 
 The publication command, its automated guards, offline candidate validation,
-and executable maintainer runbook are implemented. This adoption does not claim
-that a ReleaseKit version has been published.
+executable maintainer runbook, and prepared hosted-page workflow are implemented.
+This adoption does not claim that a ReleaseKit version has been published.
 
 ## Validation and completion
 
@@ -157,8 +158,8 @@ examples added later require appropriate execution checks.
 
 Adoption is complete when the tailored policy set, contributor navigation,
 documentation ownership, and licensing notices are coherent and verified. The
-release-path stage may remain pending until publication is implemented; record
-that status without documenting an unavailable command as usable.
+source-publication command and hosted-page delivery are implemented; actual
+publication and binary distribution remain outside policy adoption.
 
 Do not inherit PromptKit's or ConfigKit's extra release gates automatically.
 Select additional checks only for identified ReleaseKit risks, recording their
@@ -169,13 +170,14 @@ approval, and CI polling are not additional adoption or release gates.
 
 The seven policies, root agent orientation, developer reading guide, documentation
 ownership, project grant, attribution, license texts, source publication command,
-and maintainer runbook are in place. The product proposal lives at
-`docs/roadmap/releasekit.md`; `ideas.md` remains a navigation pointer. Executable
-delivery remains pending, and no ReleaseKit release has been published.
+maintainer runbook, and prepared hosted-page delivery are in place. The product
+proposal lives at `docs/roadmap/releasekit.md`; `ideas.md` remains a navigation
+pointer. Binary distribution is deferred, and no ReleaseKit release has been
+published.
 
 Verification covers local file and fragment links, per-policy source revision and
 base version, removed template adoption sections, attribution scope and pinned
 notice destinations, verbatim license bytes, and prose whitespace. The preserved
 ADR decision and relocated proposal are checked against their pre-adoption source.
-ReleaseKit's source publication command and runbook are implemented; executable
-delivery declarations remain pending under stage 4.
+ReleaseKit's source publication command, runbook, and hosted-page deliverable are
+implemented; binary delivery declarations remain deferred under stage 4.