Skip to content
Shipper

shipper auto-ship clear-halt

shipper auto-ship clear-halt

Section titled “shipper auto-ship clear-halt”

Usage: shipper auto-ship clear-halt

Clear the persistent Auto-ship repository halt

Arguments

Section titled “Arguments”
ArgumentRequiredDescriptionChoices
None---

Flags

Section titled “Flags”
LongShortValueDefaultDescriptionChoices
None-----

Examples

Section titled “Examples”

Release the persistent repository halt without enabling Auto-ship.

Terminal window
shipper auto-ship clear-halt

Exit Codes

Section titled “Exit Codes”
CodeWhen
0The halt is cleared or none was recorded.
1Repository identity or desired-state storage fails.

Constraints

Section titled “Constraints”
  • Takes no options and acts only on the current checkout. It changes only the halt; enablement, worker count, safety stop, and checkout registration remain exactly unchanged.
  • Reports whether the halt changed or was already clear. Clearing an already-clear halt succeeds as an explicit no-op.
  • This is the halt-specific recovery gesture and is distinct from shipper auto-ship resume, which recovers an engaged safety stop only. Neither gesture performs the other.
  • Clearing releases repository-control checkpoint Stops that a supervisor has not yet consumed. It never restarts already-stopped runs, restores withdrawn queue entries, or replays prior work; only ordinary Auto-ship eligibility selects later work, and the command reports no observed retraction.
  • The command starts or contacts no supervisor and returns immediately. Enabled means requested rather than dispatching; a cleared halt does not by itself enable Auto-ship.
  • 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.