Make delivery asset outcomes disjoint
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# ReleaseKit audit implementation plan
|
||||
|
||||
Status: Stages 1–4 complete; Stage 5 not started.
|
||||
Status: Stages 1–5 complete; Stage 6 next.
|
||||
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.
|
||||
@@ -277,6 +277,14 @@ pending assets. Assert category exclusivity and meaningful overall state at the
|
||||
upload boundary. CLI tests verify recovery meaning and exit classification
|
||||
without freezing full diagnostic wording.
|
||||
|
||||
**Completed:** Delivery asset categories now contain disjoint current
|
||||
observations, with later known-missing assets retained when an earlier upload
|
||||
stops work. CLI failures include state-based recovery guidance, while GoDoc and
|
||||
the delivery and Gitea guides describe category meaning and incomplete early
|
||||
observations. Upload and CLI tests cover reconciliation outcomes, recovery
|
||||
classification, and category exclusivity. The full offline suite, API boundary
|
||||
check, and documentation whitespace checks pass.
|
||||
|
||||
## Stage 6 — Give the facade ownership of build-and-deliver
|
||||
|
||||
**Covers:** F5. **Primary owners:** `delivery.go`, `internal/delivery/`,
|
||||
|
||||
Reference in New Issue
Block a user