Keep push recovery on captured endpoint
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# ReleaseKit audit implementation plan
|
||||
|
||||
Status: planned; implementation has not started.
|
||||
Status: Stage 1 complete; Stage 2 not started.
|
||||
Baseline: `e4be7fa` (2026-10-06). The [audit](audit.md) records the evidence,
|
||||
product goals, and selected direction. This document owns implementation order
|
||||
and completion criteria for that work.
|
||||
@@ -100,6 +100,12 @@ remote must find the intended object. Existing unchanged-endpoint success,
|
||||
absence, conflict, and unreadable-recovery tests continue to pass. Test the
|
||||
behavior through publication; avoid a second copy of the full recovery matrix.
|
||||
|
||||
**Completed:** Recovery now verifies the captured URL before its one tag query.
|
||||
The rewrite reproduction returns unknown, preserves the local tag and both
|
||||
errors, and confirms the object on the original remote. Focused publication
|
||||
tests, the full offline suite, API boundary checks, and documentation whitespace
|
||||
checks pass.
|
||||
|
||||
## Stage 2 — Own effective Go settings for validation and builds
|
||||
|
||||
**Covers:** F1, F3, Go-environment portion of F8. **Primary owners:**
|
||||
|
||||
Reference in New Issue
Block a user