wsp remove

usage: wsp remove <computer> [--yes] [--force] [--json]
  take a computer out, asked once: its forks are deleted and its projects leave
  this wsp with their threads, then the agent and its files go and the computer
  is left as wsp found it. Stopped by a fork or a project folder there holding
  work no remote has, naming each

  --state    the state file: this word first, else WSP_HOME's state.json, else
             ./.wsp/state.json when the current directory is a checkout of wsp,
             else state.json in the home the running host serves
  --yes      go ahead without being asked
  --force    remove it even where a fork or a project folder there holds work no
             remote has, which goes with it
  --json     print the raw protocol values, one JSON object per line, with
             everything else on stderr
  --host     read to say this line runs at its own host's terminal; it dials no
             other