consider short codes

Currently all subcommands name their arguments with long-form CLI options e.g. --name NAME. It can be convenient for interactive use to have short options e.g. -n NAME. We could implement this by, say, defining some CLI-wide short codes (e.g. name -> n and description -> D) and then walking the clap::Command tree to add those short codes for any matching long options. There are some pros and cons:

Short options require less typing for users.

Conversely long options are more explicit and more evident in both command history and in shell scripts. The options map directly to the API which makes programmatic automation a simpler translation. They're less error-prone as people are less likely to be confused. Autocomplete can mitigate the typing penalty of long options.

cc: @leftwo

Start by reviewing the CLI's clap::Command tree and existing long-option definitions. Evaluate the proposed CLI-wide mappings such as name -> n and description -> D against the stated typing, explicitness, scripting, and autocomplete trade-offs; done means the short-option policy and its scope are agreed.