selecta-cratelisted

# selecta-crate A read-only report. **It never starts music and writes nothing.** If the user wanted music playing, that is the `selecta` skill instead. ``` "${CLAUDE_PLUGIN_ROOT}"/bin/selecta crate # what this repo sounds like "${CLAUDE_PLUGIN_ROOT}"/bin/selecta crate --history 20 # tracks, by commit "${CLAUDE_PLUGIN_ROOT}"/bin/selecta crate --path # where the file lives ``` Run it in the user's current directory. The repository is detected from there, so `cd` matters and a different repo is a different crate. ## What a crate is Every track selecta plays is stamped with the branch and the commit that were checked out at the time. So `--history` is a record of the work, not a playlist. "What was I listening to while I wrote the auth migration?" is answerable, and that is the whole idea. Crates are keyed by the repository's remote, so a clone on another machine and a fork of the same upstream share one crate. Repos with no remote are keyed by path. ## Output grammar The command formats itself. **Relay it unmodified** — do not re-rank, re-word, summarise the bars into prose, or convert the durations. It emits, in order: 1. A heading line naming the repository. 2. One line per source: title, a bar, listening time. Ordered by time listened, longest first. 3. A totals line: sources, tracks, total time. 4. A `selecta resume →` line naming what would play next. 5. A link to the project. `--history` instead emits commit headers (`abc1234 on main`) with