Use one delivery asset verification pass

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Computational Efficiency Implementation Plan
 
-**Status:** Stages 1–7 complete; Stages 8–11 pending.
+**Status:** Stages 1–8 complete; Stages 9–11 pending.
 
 ## Purpose And Baseline
 
@@ -451,6 +451,23 @@ prebuilt delivery; these are explanatory measurements of the chosen flow.
 Streaming upload, exact remote comparison, and later upload verification remain
 intact. Update the inventory's delivery mechanics where needed.
 
+**Completion:** Complete. `declaredBuildAssets` now performs target/name,
+filename, regular-file, and stat checks, then uses each recorded SHA-256 to
+build expected assets and the manifest. The separate local verification in
+`Deliver` remains after build identity checks and before hosted requests; it
+checks current bytes and sizes for managed and prebuilt artifacts. A same-size
+prebuilt mutation now fails at this delivery preflight with zero hosted
+requests. Delivery, Gitea, facade, and CLI tests passed. On the recorded Go/Git
+and machine setup, three artifact runs measured declarations at 11.3–15.4 µs
+(2,296 B/op) and declarations plus one local verification at 121–136 ms
+(about 69.7 KB/op). The Stage 2 comparison was 94.3–95.4 ms and 186.7–188.4 ms
+respectively, each including the declaration hash pass; the new second result
+therefore removes one 32 MiB file-read/hash pass from this workload. Three
+facade runs measured fresh uploads at 485–520 ms and matching retries at
+214–311 ms. These complete-workflow timings overlap the recorded baselines
+within shared-machine variation and remain dominated by the local HTTP fixture,
+upload, and remote comparison work.
+
 ## Stage 9: Transfer Completed Go Output Without Copies
 
 **Owners:** [gotool.go](../../internal/gotool/gotool.go), validation/build callers,