Record completed remediation and final verification

docs/roadmap/remediation.md

@@ -1,6 +1,7 @@
 # ReleaseKit implementation review and remediation
 
-Status: In progress. Resolution notes record completed fixes and verification.
+Status: Complete. R1–R10 are resolved; resolution notes record the fixes and
+verification.
 
 Date: 2026-10-06
 
@@ -30,7 +31,7 @@ The prepared workflow syntax was also compared with the official Woodpecker
 Live CI, live Gitea delivery, consumer migrations, and measured consumer code
 reduction remain intentionally deferred; their absence is not a finding.
 
-## Architecture assessment
+## Initial architecture assessment
 
 One Go module exposes two supported packages. The root `releasekit` package
 owns `Check`, `Publish`, `Build`, `Deliver`, and their public request/result
@@ -394,12 +395,31 @@ helper-to-controller imports, and internal-to-facade imports remain rejected.
 Positive and negative dependency fixtures and the actual compiled repository
 boundary checks pass.
 
+## Completion verification
+
+The final uncached offline suite passes with `go test -count=1 ./...`, using
+`GOWORK=off`, `GOPROXY=off`, `GONOPROXY=none`, `GOSUMDB=off`, and
+`GOTOOLCHAIN=local`. `go run ./internal/apicheck` passes against the completed
+facades and dependency graph. All ten findings have resolution notes and
+focused behavioral evidence. Changed documentation's local links and fragments
+and prose whitespace validate. Each implementation unit and follow-up fix was
+committed separately with a plain English message; every commit is nonempty.
+
+The current root facade contains declarations, explicit conversions, callback
+adaptation, and forwarding. Filesystem and artifact mechanics are internal;
+`buildinfo` retains its lightweight runtime boundary. The new source-eligibility
+fact records ordinary pre/post-build observations and adds no attestation or
+concurrency-proof snapshot guarantee. Hosted content remains immutable, and
+source publication remains independent of asynchronous delivery.
+
+All verification used local Git and HTTP collaborators. No real source release,
+hosted delivery, consumer migration, or live CI activation was performed.
+
 ## Remediation boundaries
 
-Address these findings before treating the initial implementation as complete
-for the maintainer's next-step decisions. The work should repair the selected
-behavior and ownership boundaries, with focused regression checks for the
-reproduced defects. It should preserve the two facades, selected publication
+The completed work repairs the selected behavior and ownership boundaries,
+with focused regression checks for the reproduced defects. It preserves the
+two facades, selected publication
 standard, immutable hosted contents, lightweight runtime dependency graph,
 source-only hosted pages, and separate publication/delivery status.