shipper monitor
shipper monitor
Section titled “shipper monitor”Usage: shipper monitor [options] [issue]
Continuously monitor durable Shipper workflow changes
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| [issue] | no | Shipper issue ID, gh: | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —include-progress | - | - | false | include ordinary forward workflow progress | - |
| —jsonl | - | - | false | write canonical newline-delimited JSON records | - |
| —stop | - | never | stopping policy: never, stage_end, or merge | never, stage_end, merge |
Examples
Section titled “Examples”Continuously observe repository workflow changes.
shipper monitorObserve one issue through its current stage attempt as canonical JSONL.
shipper monitor S#42 --include-progress --jsonl --stop stage_endExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The target is reached or the operator interrupts monitoring. |
| 2 | Workflow regresses through bounce, failure, or orphaning. |
| 3 | Durable state requires human action without workflow regression. |
| 4 | Monitor integrity or replay continuation fails. |
Constraints
Section titled “Constraints”- Read-only and continuous by default; polls durable state every two seconds.
stage_endandmergerequire a single issue filter;neveris the default.--jsonlemits the canonical attachment, event, and result contract unchanged.- See Workflow monitoring for taxonomy, recovery, liveness, snapshots, and streaming and stopping semantics.