shipper issue recover-blocked-comment
shipper issue recover-blocked-comment
Section titled “shipper issue recover-blocked-comment”Usage: shipper issue recover-blocked-comment [options]
Inspect uncertain Blocked delivery or authorize one duplicate-risk retry
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| yes | Shipper issue ID, gh: | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —group | - | - | unresolved Blocked mirror group | - | |
| —attempt | - | - | current positive attempt token from inspection | - | |
| —retry | - | - | - | authorize one retry with —accept-duplicate-risk | - |
| —accept-duplicate-risk | - | - | - | accept that another attempt may duplicate a Blocked comment | - |
Examples
Section titled “Examples”Inspect uncertainty and safely recover a known receipt or marker without posting.
shipper issue recover-blocked-comment S#42Authorize one retry of the currently inspected attempt.
shipper issue recover-blocked-comment S#42 --group <id> --attempt <token> --retry --accept-duplicate-riskThis Blocked-restricted compatibility wrapper uses the same recovery engine and flags as shipper issue recover-comment. Non-Blocked selections are refused.
Exit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | Inspection, safe recovery, durable authorization, retirement, or live-stage deferral succeeds. |
| 1 | Options, identity, or the attempt token are invalid, stale, or consumed. |
Constraints
Section titled “Constraints”- The earlier attempt may already have posted. Authorizing another attempt can create a duplicate Blocked comment.
- Without flags this command never POSTs. Safe receipt/marker discovery runs again under the issue lock before authorization; incomplete discovery consumes no token.
- Supply all four authorization options together. Attempt tokens are positive safe integers and authorize one unresolved boundary; replay and stale tokens are refused.
- Current Blocked work becomes ready once; obsolete, unblocked, or tombstoned work is retired without recreating its body. Store-only policy performs no GitHub recovery.
- A running stage defers recovery without consuming authorization. Nothing was recorded; rerun this command after the stage finishes.
- Unmarked legacy linkage is not ownership. Body, heading, account, saved ID, and hash alone never authorize changing a Blocked comment; unverifiable old copies may require manual removal.