Reporting a bug

Email help@groovecutter.app with the following. GrooveCutter keeps no log, so these are what we go on.

What you did, what you expected, and what happened. Include the exact command and the full error text.
Your version, your system (macOS, Linux or Windows) and your settings. The token stays masked. The app shows its version at the top right; on the command line:
```
groovecutter --version
groovecutter config show
```
The Discogs release link.
If cuts are wrong, the analysis, run on the same recordings. It writes nothing but this report:
```
groovecutter analyze --json --release 4570366 side-*.wav > report.json
```
Also send <first recording>.groovecutter.json from beside your recordings. It holds your edits. Tell us which track and roughly where the right cut is.

If it crashes, run the same command again with a backtrace and send all the output.

RUST_BACKTRACE=1 groovecutter ...         # macOS, Linux
$env:RUST_BACKTRACE=1; groovecutter ...   # Windows PowerShell

Please don't send your recordings or your Discogs token. These reports may show your file and folder names.