Give delivery facade ownership of builds

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # ReleaseKit audit implementation plan
 
-Status: Stages 1–5 complete; Stage 6 next.
+Status: Stages 1–6 complete; Stage 7 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.
@@ -329,6 +329,17 @@ on success and failure. Extend existing mutation/cancellation coverage where
 needed. Preserve prebuilt retry, digest conflict, note conflict, and source
 eligibility coverage. Confirm the two facades' dependency boundaries.
 
+**Completed:** `Deliver` now owns optional managed builds, page-only requests,
+and explicit prebuilt artifact delivery behind the public facade. Managed output
+uses temporary storage outside the checkout and is cleaned after success,
+failure, and cancellation; source and note checks precede compilation, and
+eligibility is rechecked before hosted writes. Prebuilt files remain
+caller-owned. Consumer and internal package guides describe these paths.
+Facade-level consumer and HTTP tests cover managed upload, page-only delivery,
+preflight and build failures, checkout mutation, cleanup, cancellation, and
+prebuilt ownership. The full offline suite, API boundary check, and
+documentation whitespace checks pass.
+
 ## Stage 7 — Route ordinary CLI delivery through the facade
 
 **Covers:** the CLI portion of F5. **Primary owners:**