Make delivery asset outcomes disjoint

docs/consumers/delivery.md

@@ -46,9 +46,19 @@ settings, and file hashes before making a remote request.
 
 The result reports `complete`, `partial`, `conflict`, `unknown`, or
 `not_attempted`, along with matching, uploaded, pending, conflicting, and
-uncertain assets when known. Exit status 3 means a remote write could not be
-resolved; inspect the same version and retry only after the remote state is
-understood. The command does not run candidate checks or publish tags.
+uncertain assets when known. These are disjoint current observations: an asset
+appears in at most one category, and early failures may leave some declared
+assets unreported. `Matching` means existing content matches; `Uploaded` means
+an upload was confirmed during this invocation; `Pending` means known missing
+work; `Conflicting` means different hosted content was found; `Uncertain` means
+the remote state could not be resolved.
+
+Fix local or preflight failures before retrying. For partial delivery, fix the
+reported cause and retry the same version. Resolve an unknown remote outcome
+before retrying. Investigate conflicts and use a new version if the source or
+published content needs correction. If rebuilding could change bytes already
+on the server, retain the original build output and retry with `--assets DIR`.
+The command does not run candidate checks or publish tags.
 
 ## Go API