shipper output groom-draft
shipper output groom-draft
Section titled “shipper output groom-draft”Usage: shipper output groom-draft
Prepare a native grooming draft or record its actual answer
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| yes | - | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| None | - | - | - | - | - |
Examples
Section titled “Examples”Prepare a complete native capture or record the actual operator answer.
shipper output groom-draft .shipper/output/native-request.jsonExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The capture or answer was checkpointed. |
| 1 | The launch, request, or saved checkpoint is invalid. |
Constraints
Section titled “Constraints”- Available only from an authenticated attended grooming launch; does not deliver issues or advance workflow state.
- Request JSON is either { message, draft: { manifest, commentFile, files } } or { answer }. Shipper alone derives revision, digest, complete preview, comparison and approval provenance.
- Show the returned draft and changes word for word before obtaining the actual answer. Sole Approve materializes the captured output; feedback requires a new capture.