CLI plans

[duckinator]

Rough idea: jwl will continue to be for managing a specific project, and jwlx will be for running commands from a gem.

# jwl commands (working with a specific project)
jwl build       # build a gem from source
jwl clean       # clean up all build artifacts
jwl doc         # build documentation
jwl new         # create a new gem 
jwl init        # create a new gem, in an existing directory
jwl run         # run a binary from the gem
jwl test        # run the test suite
jwl bundle      # installs all the dependencies for the project (to `.bundle/`)
jwl release     # publish both to a gem registry and/or other services

# jwlx commands (akin to `pipx`)
jwlx install GEMNAME # fetch and install GEMNAME in an isolated way
jwlx run GEMNAME ... # fetch, install to a temporary location, and then run GEMNAME
jwlx upgrade GEMNAME # upgrade an gem installed via `jwlx install`

[duckinator]

i also realized: this could be an opportunity to drop gemspecs in favor of something like TOML, and finally address both the problem where gemspecs run arbitrary code and the problem where gemspecs pretend that there's only a single source of truth for gems.

taking cues from pyproject.toml and Cargo.toml:

[project]
name = "some-project"
version = <TODO>
authors = [
    {name = "Ellen Marie Dash", email = "me@duckie.co"},
]
description = "..."

[sources]
gem-coop = "https://gem.coop"
rgo = "https://rubygems.org"
gh-duckinator = "https://rubygems.pkg.github.com/duckinator"

[dependencies.gem-coop]
example-gem = "0.1.2"

[dependencies.rgo]
some-other-gem = "1.2.3"

[dependencies.gh-duckinator]
jwl = "1.0.0b4"