Recover publication against the captured endpoint

docs/roadmap/remediation.md

@@ -323,6 +323,8 @@ and unresolved publication 3. The focused wrapper test passes.
 
 ### R9 — High: Manual recovery inspects the fetch endpoint
 
+Status: Resolved.
+
 Category: Release recovery correctness and documentation gap.
 
 **Evidence:** [The runbook](../release.md), around line 82, prescribes
@@ -347,6 +349,13 @@ local tag.
 fetch/push repositories and confirm that a published tag is recognized. Include
 endpoint changes after an uncertain push when verifying retained recovery facts.
 
+**Resolution:** Failed publication output includes the captured endpoint. The
+runbook checks URL resolution and queries that exact endpoint, retaining tags
+on failed or unresolved checks. Local wrapper fixtures use separate fetch and
+push repositories; a lost acknowledgment changes the configured push URL, and
+recovery still finds the intended object at the captured endpoint while the
+fetch endpoint reports absence. Focused publication/wrapper tests pass.
+
 ### R10 — Medium: The boundary checker bans valid command-internal composition
 
 Category: Inadvertently strengthened architectural prohibition.