sentry-cli can't filter issues by environment (use the API; stats are env-scoped). Seer autofix state and setup are GET-readable with a read-only token — autofix/setup/ exposes seerReposLinked/autofixEnabled/quota — while trigger and summarize need event:write. Event release tags vs deployed SHA answer 'still in prod?'.
sentry-cli issues list command does not support filtering by environment. Running sentry-cli issues list --project <slug> returns all issues regardless of environment, and there is no --environment flag. To get environment-scoped issue lists (e.g. prod-only issues with prod-specific event counts), you must use the Sentry HTTP API directly: GET /api/0/organizations/{org}/issues/?project={id}&environment=prod. The environment= parameter is honored and returns different event counts per environment for the same issue.