shipper auto-ship disable

Usage: shipper auto-ship disable

Turn Auto-ship enablement off and drain automatic work at safe checkpoints

Arguments

Argument	Required	Description	Choices
None	-	-	-

Flags

Long	Short	Value	Default	Description	Choices
None	-	-	-	-	-

Examples

Turn Auto-ship enablement off for the current repository.

shipper auto-ship disable

Exit Codes

Code	When
0	The repository is recorded as not enabled, including an explicit no-op.
1	Repository identity or desired-state storage fails.

Constraints

Acts only on the current checkout and changes only enablement; worker count, repository halt, safety stop, and checkout registration remain unchanged.
Disable turns enablement off and drains current automatic work until Auto-ship is enabled again. It is distinct from a repository halt, which is a persistent operator hold that survives disabling and enabling and ends only through shipper auto-ship clear-halt.
Reports whether enablement changed or was already not enabled. A supervisor observing the disabled state requests repository-control Stops for running automatic Ships at their next safe checkpoint.
Re-enabling retracts only unconsumed repository-control requests. It does not relaunch a run that already stopped, restore a withdrawn queue entry, or override an explicit per-run Pause or Stop; ordinary future dispatch determines later eligibility.
The durable write returns immediately and does not prove dispatch has stopped. Use shipper status to confirm; a running supervisor normally observes an external write within roughly five seconds.
The command starts or contacts no supervisor. Enabled means requested rather than running, and holder evidence follows the same alive-only PID/acquisition rule as the other gestures.
Every Auto-ship record mutation first classifies the retained bytes under the shared lock. A future schema is retained unchanged and refused with its path and a request to reconnect with a current Shipper client or re-run the Shipper installation. A valid record for another canonical repository is retained unchanged and refused with both identities and a request to resolve the file outside Shipper. Neither conflict has a Shipper repair, reset, or discard gesture, and refusal output makes no dispatch-holder or mutation-success claim. Corrupt replaceable records can still be recreated, versions 1 and 2 migrate losslessly to version 3, and successful output reports core applied/unchanged outcomes plus any migration.