[tamnd]

Closes #150.

version wrote its line to stdout directly and never touched the renderer, so -o did nothing:

$ ccrawl version -o csv
ccrawl dev (commit none, built unknown, darwin/arm64, go1.26.5)

Six facts in a sentence, and a CI job that wants one of them has to write a regular expression against a format documented nowhere.

After

$ ccrawl version -o jsonl
{"arch":"arm64","built":"unknown","commit":"none","go":"go1.26.5","os":"darwin","version":"dev"}

$ ccrawl version -o csv
version,commit,built,os,arch,go
dev,none,unknown,darwin,arm64,go1.26.5

$ ccrawl version -o table
╭─────────┬────────┬─────────┬────────┬───────┬──────────╮
│ VERSION │ COMMIT │ BUILT   │ OS     │ ARCH  │ GO       │
...

What deliberately did not change

-o auto, the default, keeps the sentence, and keeps it in a pipe as well as on a terminal. Everywhere else auto means a table for a person and JSON Lines for a pipe, and following that here would turn ccrawl version | grep into a different string for everyone who already has it in a script. Asking for a format is how you say you want data. The test pins this, and a test run is a pipe, so it is the case that would have broken.

--short is untouched.

Why the other bare-value commands were left alone

This turned up in a sweep of the local commands after #140, so it is worth saying what else the sweep found and why nothing else moved. cache dir, library path, and config get each print one string. Wrapping one string in a JSON object helps nobody and would break cd "$(ccrawl cache dir)". version is different because it is a record wearing a sentence.

Checks

• gofmt, go vet, go test ./..., docs-drift.sh, coverage.sh, golangci-lint run ./...
• live: all four formats above, plus plain version and --short unchanged

docs/content/reference/cli.md gains a version section, which it did not have beyond a row in the command table.