Consolidate Woodpecker delivery templates

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # ReleaseKit audit implementation plan
 
-Status: Stages 1–9 complete; Stage 10 next.
+Status: Stages 1–10 complete; Stage 11 next.
 Baseline: `e4be7fa` (2026-10-06). The [audit](audit.md) records the evidence,
 product goals, and selected direction. This document owns implementation order
 and completion criteria for that work.
@@ -510,6 +510,20 @@ matching remote content. The bootstrap shim proves template wiring, not
 published-module availability. Record that distinction and retain real
 installation/live Woodpecker verification as deployment work.
 
+**Completed:** Source-only and binary consumer delivery now share one
+profile-driven `tag-delivery.yml` using versioned `go run ... ci-deliver`; the
+duplicated templates were removed. ReleaseKit's separate first-source workflow
+still builds its CLI from tagged source and then uses `ci-deliver`. CLI workflow
+tests extract and execute the maintained command blocks with matrix
+substitution, Woodpecker dollar escaping, local Git/HTTP fixtures, and a Go
+bootstrap shim. Both profiles deliver successfully twice, preserving matching
+pages and binary assets. The shim validates command wiring but does not prove
+published-module availability. Consumer and maintainer guidance now covers
+bootstrap requirements, credentials, Go compatibility, caches, dependency
+preparation, and pin upgrades. Real pins and live integration remain deployment
+work. The full offline suite, API boundary check, and documentation whitespace
+checks pass.
+
 ## Stage 11 — Validate representative adoption and close the sprint
 
 **Covers:** audit-wide acceptance and adoption evidence. **Primary owners:**