Rule 5 of 8 · Chapter II — CLI & Automation
Output for the audience: table for humans, json for scripts.
Why this rule exists
Parsing table output in a script breaks on the next CLI release; eyeballing raw json wastes human time. Each consumer gets its own format.
In practice
Interactive: -o table with a --query for the columns you need. Scripts: -o json piped through jq, or --query with tsv for shell variables.