Prepare ReleaseKit hosted-page delivery

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # ReleaseKit staged implementation plan
 
-Status: In progress. Stages 1–16 are complete; later stages remain pending.
+Status: In progress. Stages 1–17 are complete; later stages remain pending.
 
 Date: 2026-10-05
 
@@ -882,7 +882,7 @@ Woodpecker runner, image pull, secret, or hosted delivery service was used.
 
 ## Stage 17: Prepare ReleaseKit's own hosted-page delivery
 
-Status: Pending. Depends on Stage 16.
+Status: Complete. Depends on Stage 16.
 
 1. Extend ReleaseKit's source-only profile with its Gitea destination and token
    environment name. Keep the build target set empty and retain its selected
@@ -905,6 +905,19 @@ requiring a receipt, or consulting a previously released tool. Delivery failure
 leaves source status unchanged. Workflow preparation requires no real tag,
 credentials, remote push, CI activation, or maintainer checkpoint.
 
+Evidence: ReleaseKit's root profile identifies its Gitea destination and
+`RELEASEKIT_GITEA_TOKEN`, preserves the offline default test suite, and declares
+no build targets. The repository-specific Woodpecker example remains under
+`examples/` and builds the CLI from the fetched, commit-checked tag before
+page-only delivery; the release procedure documents later activation and secret
+configuration, source-tag completion, and same-tag retry. A local integration
+test clones and tags a temporary copy of the repository, builds the CLI from
+that tag, and exercises delivery against a local HTTP server. It verifies a
+hosted-tag failure leaves the source tag intact, then checks page creation and
+an identical rerun without assets; the complete note body, including its three
+license links, is preserved. No real tag, push, credential, or hosted service
+was used.
+
 ## Stage 18: Complete the initial implementation and handoff documentation
 
 Status: Pending. Depends on Stage 17.