shipper_resume_auto_ship
shipper_resume_auto_ship
Section titled “shipper_resume_auto_ship”Clear the active repository’s durable auto-ship safety stop in one atomic operation. Safety recovery does not clear an operator-requested repository halt; use shipper_clear_auto_ship_halt for that. This does not change enablement, worker count, halt state, or daemon availability.
When to use
Section titled “When to use”Use this state-changing local operation to clear the active repository’s durable auto-ship safety stop without changing enabled, workerCount, or haltRequested. The target is the canonical identity of the repository selected at server startup or by shipper_switch_repo. It performs one atomic core resume operation, does not pre-read state, register a checkout, or coordinate a daemon, and returns status: recorded after a clear and as a no-op when no stop is engaged. A future schema or valid foreign identity returns the successful protocol result status: refused with only repository and conflict; the retained record is unchanged and no supervisor or owner follow-up runs. Clearing a stop while auto-ship is disabled does not enable it, and safety recovery never clears an operator-requested repository halt; use shipper_clear_auto_ship_halt for that.
Behavior hints
Section titled “Behavior hints”- readOnlyHint: false — The tool intentionally clears durable local safety-stop state.
- destructiveHint: false — The tool clears only the safety-stop latch and does not delete repository or workflow artifacts or rewrite desired state.
- idempotentHint: true — Repeated calls after the first clear succeed with
outcome: "not-engaged". - openWorldHint: false — The tool writes only local machine state and does not contact GitHub or another external system.
Input schema
Section titled “Input schema”| Name | Type | Required | Default | Description |
|---|
Output schema
Section titled “Output schema”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| status | enum: recorded, refused | yes | - | - |
| repository | string | yes | - | - |
| outcome | enum: cleared, not-engaged | no | - | - |
| conflict | - | no | - | - |
Example call
Section titled “Example call”{}Example result
Section titled “Example result”{ "content": [{ "type": "text", "text": "Auto-ship safety stop cleared for repository owner/repo." }], "structuredContent": { "status": "recorded", "repository": "owner/repo", "outcome": "cleared" }}
No-op when no stop is engaged: { "status": "recorded", "repository": "owner/repo", "outcome": "not-engaged" }, with text "No auto-ship safety stop was engaged for repository owner/repo."
Compatibility refusal: { "status": "refused", "repository": "owner/repo", "conflict": { "kind": "unsupported-schema-version", "recordPath": "<retained path>", "retainedSchemaVersion": 4, "currentSchemaVersion": 3, "readableSchemaVersions": [1, 2, 3], "staleSide": "client" } }. It contains no outcome field and offers the current-client/install remedy, not a repair or discard gesture.Error modes
Section titled “Error modes”- Canonical repository identity unavailable: Could not derive a canonical repository identity for
. - Safety-stop persistence failure: <underlying filesystem, lock, or atomic-write error>