feat(arg-parsing): accept comma-separated project slugs

[betegon]

Summary

sentry issue list acme/web,api currently requests the concatenated slug and 404s. This lets issue list and project list accept a comma-separated project selector after the org (<org>/a,b). Parsing is enabled per command via parseOrgProjectArg(target, { allowProjectList: true }); every other command keeps today's semantics, including comma-containing project names in project create.

issue list <org>/a,b resolves each slug to its numeric ID with the same cache-first lookup a single <org>/<project> target uses (fetchProjectId), in parallel, then issues a single SDK request with the IDs through the repeated project query parameter. Sorting, --limit, and cursor pagination stay server-side and share the org-all code path.

• Unknown slugs fail with a ResolutionError before the request; the issues endpoint would otherwise answer with a 403 that reads like a permissions problem.
• Lookups are strict: if one fails, the command errors instead of sending a slug, since self-hosted releases before 26.6 reject non-numeric project values.
• Aliases for the ALIAS column are stored without a DSN fingerprint, so sentry issue view <ALIAS> works from any directory.
• The cursor context key uses the sorted slugs, so -c next still works when the slugs are retyped in another order.

project list <org>/a,b looks up each project directly and preserves input order, reporting slugs that do not exist separately from slugs excluded by --platform. Lookup errors other than 404 propagate like org-all instead of rendering as "no projects found".

A plain <org>/<project> target is unchanged in both commands (same handlers, hints, and cursor behaviour as main).

Implementation notes

• listIssuesPaginated/listIssuesAllPages take projects?: ReadonlyArray<number | string> instead of a single projectId; existing callers pass [id].
• resolve-target.ts adds resolveProjectIdsInOrg (strict, for issue list) and findProjectsInOrg (404 as missing, for project list); fetchProjectId gains { strict } to re-throw non-404 failures.
• Selectors are looked up slug by slug rather than through the org catalog: the cost follows the number of slugs instead of the org size, and a project is never reported missing because the catalog stopped at the pagination cap.
• formatProjectTarget and explicitProjectSlugs in arg-parsing.ts keep titles, hints, and cursor context keys formatted identically.

Test plan

• sentry issue list <org>/web,api --json resolves both IDs without a catalog request and sends one SDK request with both project IDs
• unknown slugs fail before querying issues (one keeps the single-project error with suggestions; several produce one combined error that keeps each slug's suggestions); a failed lookup errors instead of falling back to slugs
• selector aliases resolve with a DSN fingerprint present; stale aliases are replaced even on an empty page
• -c next resumes when the slugs are retyped in another order
• comma selectors trim empty entries, de-duplicate, reject display names, and validate each slug
• <org>/a,b targets render the multi-project footer tip and -c next/prev hints with the full selector
• sentry project list <org>/web,api looks up each project directly and preserves input order; non-404 errors propagate
• project listing distinguishes missing projects from --platform filtering
• single-project issue list / project list targets and comma-containing project create names behave as before
• Manually against SaaS: in an org with ~1,000 projects the selector makes 2 project lookups cold and none warm (previously 11 sequential catalog pages); with a lowered pagination cap, a project beyond the first pages is still found; sentry issue view <ALIAS> resolves from a directory whose .env contains a DSN

[vercel]

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

Project	Deployment	Actions	Updated
cli	Ready	Preview	Sep 29, 2026 3:35pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Sep 29, 2026 3:35pm UTC

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[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.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 27ad430. Configure here.}