Fix release destination handling and verification example

docs/roadmap/remediation.md

@@ -1,5 +1,25 @@
 # Release Workflow Review Findings
 
+Status: both findings addressed. The original findings below are retained as
+review history until normal release-preparation retirement.
+
+## Resolution and verification
+
+- Publication, fetch, and recovery now use the same validated named `origin`.
+  Pushes retain exact refspecs and disabled implicit tags, and override the
+  remote's mirror default for that invocation only. No new gate was introduced.
+- A disposable-Git regression failed against the original publisher and passes
+  with the fix for normal publication and lost main/tag push responses. It also
+  checks that broad push defaults do not publish or delete unrelated refs and
+  that the rewrite destination receives no refs.
+- Optional consumer verification explicitly initializes the selected version.
+  Executing the documented block with a local Go stub verified the exact module
+  argument with both an initially unset and an initially stale version variable,
+  without network retrieval.
+- Focused publication tests passed. Final validation passed: Bash syntax,
+  whitespace review, and the Go 1.25.14 release checker (race suite including
+  documentation links, full vet, and both Linux target builds).
+
 Reviewed implementation through `3d0093e` against the release roadmap and
 completed implementation plan. The ordinary Go 1.25.14 release checker passed
 (offline race suite, full vet, Linux amd64/arm64 builds), as did Bash syntax