Tracking: family-wide JSON-on-resource-reads policy alignment

[rianjs]

Tracking issue. Family-wide migration from "JSON on every resource-read" to the §2 stance: JSON is reserved for round-trip payloads (e.g., automation export) and control-plane envelopes (e.g., set-credential --json).

Why: §2 of docs/output-and-rendering.md — agent-first text output is the primary surface; JSON on resource reads gives agents two consumption paths to maintain (text + JSON) and incentivizes them to pick the verbose one. Only jtk holds this line today.

Affected CLIs (need child issues per CLI):

• slck — global -o json exposes JSON on every resource read
• sfdc — global -o json exposes JSON on every resource read
• nrq — global -o json exposes JSON on every resource read
• cfl — global -o json exposes JSON on every resource read (part of atlassian-cli true-ups parent issue)
• gro — per-command --json flags (e.g., gro drive drives --json)

Reference: jtk reserves JSON for automation export only — no global -o json flag registered.

Out of scope: Control-plane envelopes (set-credential --json, config show --json per §1.8 of working-with-secrets.md) are not "resource reads" and are NOT being removed. The §2 line is about reads-of-application-resources only.

Breaking change: Removing -o json will break downstream scripts. Needs deprecation cycle (warn-then-remove) across all 5 affected CLIs.

Source: docs/output-and-rendering.md §10, divergence catalog (PR #28 / commit e4d59c6).

[rianjs]

Filed per-CLI children:

• Remove resource-read -o json (cli-common output-and-rendering §2) slack-chat-api#173
• Remove resource-read -o json (cli-common output-and-rendering §2) salesforce-cli#44
• Remove resource-read -o json (cli-common output-and-rendering §2) newrelic-cli#108
• Remove per-command --json flags (cli-common output-and-rendering §2) google-readonly#144
• cfl: remove resource-read -o json atlassian-cli#392 (the cfl side; lives under the atlassian-cli parent #388)

This tracker stays open until all five close.