loopsmith v0.1.2

Fixed

• The PyPI launcher exec-looped instead of running. ensure_binary() had a
  "reuse a loopsmith already on PATH" shortcut, and pip installs this package's
  console script as loopsmith on PATH — so shutil.which("loopsmith") found the
  very script that was running and execv re-entered it forever. The symptom was
  the worst kind: no output, no error, no traceback, just a command that never
  returns. The shortcut is gone, because telling our own console script apart from
  a cargo-installed binary means comparing argv[0], the interpreter's script
  directory, and the symlinks between — all to save one download that happens once
  per version. __main__ also refuses outright if the binary it resolved is the
  launcher itself, since that failure mode has no useful symptom to debug.

Only the PyPI wrapper was affected. loopsmith-cli 0.1.1 on PyPI is unusable;
0.1.2 is the version to install. The npm wrapper resolves a fixed path beside
itself and never had this bug.

Everything else is byte-for-byte 0.1.1. The version is bumped across all four
registries rather than only on PyPI, so one number means one thing everywhere.