Preserve page creation outcomes through recovery

docs/roadmap/remediation.md

@@ -96,6 +96,8 @@ cleanup. The offline suite and public boundary checks pass.
 
 ### R2 — High: Some successful page writes are reported as not attempted
 
+Status: Resolved.
+
 Category: Failure handling and recovery-state correctness.
 
 **Evidence:** [EnsureRelease](../../internal/gitea/release.go), at the
@@ -121,6 +123,12 @@ unknown. Retain the selected bounded reconciliation and immutable-content rules.
 its matching and conflicting follow-up lookups, and a recovered create followed
 by asset-inspection failure. Assert both request counts and returned state.
 
+**Resolution:** Semantic create-response failures now use one reconciliation
+lookup. Recovered page results retain create-request history, preserving partial
+progress on later asset-inspection failure. Local HTTP tests cover matching,
+conflicting, and unavailable lookups; a CLI fixture verifies recovered creation
+followed by failed asset inspection. Both affected suites pass.
+
 ### R3 — Medium: Read-only asset failures are classified as unknown writes
 
 Category: Divergence from the selected outcome contract.