feat(issue): batch view and explain commands

[betegon]

Summary

sentry issue view and sentry issue explain now accept space- or newline-separated issue IDs with bounded parallel work and deterministic batch output.

Single-issue contracts do not change: view --json remains a flat issue object, while explain --json remains an array of root causes. Multi-issue view returns an array of those issue objects; multi-issue explain returns labeled envelopes (issue, org, issueId, rootCauses). Partial failures warn on stderr without changing the JSON shape, and all-failed batches rethrow the primary error.

issue view --web opens every requested issue up to a five-tab safety cap. --force bypasses the cap. -f remains the repository-wide --fresh alias instead of acquiring a second meaning.

The shared single-issue positional remains unchanged for plan, resolve, unresolve, archive, and events; batch commands use a separate variadic positional. issue list --expand remains out of scope for 1b.

Validation

• TZ=UTC pnpm exec vitest run test/lib test/commands test/types test/script — 9,819 passed, 17 skipped
• pnpm run typecheck
• pnpm run lint
• pnpm run check:fragments — valid; existing unrelated proguard upload coverage warning only
• Generated command docs, agent skill, and SDK
• Clean merge-tree against current origin/main

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
cli	Ready	Preview	Sep 28, 2026 9:16am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Sep 28, 2026 9:16am UTC

[BYK]

sentry issue view A B -w opens only A and warns that extras are ignored

I'd say it should open all up to a limit and the limit can be bypassed with -f

[BYK]

sentry issue explain A B is still single-id (shared positional untouched)

I'd also make this support multiple issues

[betegon]

Addressed both points from @BYK:

• issue view A B -w now opens both. The default safety cap is 5 tabs, and --force opens all requested issues. I kept -f bound to the shared --fresh flag used across read-only commands, so the override is long-form --force rather than giving -f two meanings.
• issue explain A B now batches too, with the same space/newline input, concurrency bound, partial-failure behavior, and single-invocation compatibility guarantees as issue view.

The cleanup also fixed the CI trace nullability error, extracted issue formatting from the command, and centralized issue-batch orchestration.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 5cd800a. Configure here.}