feat(list): add pagination and consistent target parsing to all list commands (#262)

## Summary

Extends the pagination and flexible target parsing pattern introduced in
#221 for \`project list\` to all remaining list commands: \`issue
list\`, \`team list\`, \`repo list\`, \`trace list\`, and \`log list\`.
Also introduces a shared \`dispatchOrgScopedList\` infrastructure that
all four list commands now use.

## Changes

### Shared infrastructure

- **\`src/lib/arg-parsing.ts\`**: Added \`validateLimit(value, min,
max)\` — shared limit validation, replaces duplicate implementations in
\`trace/list.ts\` and \`log/list.ts\`
- **\`src/lib/resolve-target.ts\`**: Added \`resolveOrgsForListing()\`
(deduplicates identical logic from \`team/list.ts\` and
\`repo/list.ts\`), \`resolveOrgProjectTarget()\`, and
\`resolveOrgProjectFromArg()\` — replaces local
\`resolveTraceTarget\`/\`resolveLogTarget\` in trace/log commands
- **\`src/lib/api-client.ts\`**: Added \`listIssuesPaginated()\`,
\`listTeamsPaginated()\`, \`listRepositoriesPaginated()\`,
\`listProjectTeams()\` using \`orgScopedRequestPaginated()\` for
cursor-based pagination with Link header support
- **\`src/lib/org-list.ts\`**: New shared dispatch infrastructure —
\`ListCommandMeta\`, \`OrgListConfig\`, \`ModeHandlerMap\`,
\`dispatchOrgScopedList\` — all list commands use this
- **\`src/lib/list-command.ts\`**: Shared Stricli parameter constants
and \`buildOrgListCommand\` factory for simple org-scoped commands

### Command changes

| Command | What changed |
|---|---|
| \`issue list\` | Added \`--cursor/-c\` flag; org-all mode now uses
\`listIssuesPaginated\` and returns \`{ data, hasMore, nextCursor? }\`
in JSON output |
| \`team list\` | Full rewrite: 4-mode handler via
\`dispatchOrgScopedList\`, \`--cursor/-c\` flag, project-scoped team
listing via \`listProjectTeams\` for \`org/project\` mode |
| \`repo list\` | Full rewrite: 4-mode handler via
\`dispatchOrgScopedList\`, \`--cursor/-c\` flag, org-scoped fallback
with note for \`org/project\` mode |
| \`project list\` | Migrated to \`dispatchOrgScopedList\` with mode
overrides (no behavior change) |
| \`trace list\` | Replaced local \`resolveTraceTarget\` +
\`validateLimit\` with shared versions from \`resolve-target.ts\` /
\`arg-parsing.ts\` |
| \`log list\` | Replaced local \`resolveLogTarget\` + \`validateLimit\`
with shared versions from \`resolve-target.ts\` / \`arg-parsing.ts\` |

### Tests

- \`test/commands/team/list.test.ts\`: Covers all 4 modes including
project-scoped team listing and bare-slug project search
- \`test/commands/repo/list.test.ts\`: Covers all 4 modes including
bare-slug project search with org-scoped fallback
- \`test/lib/org-list.test.ts\`: 36 tests covering the shared dispatch
infrastructure
- \`test/e2e/issue.test.ts\`: Updated org-all JSON output assertion to
match new \`{ data, hasMore }\` shape

## Behavior notes

- **\`issue list\` org-all JSON output shape changed**: was a plain
array \`[...]\`, now \`{ data: [...], hasMore: bool, nextCursor?: string
}\` — consistent with \`project list\`
- **Target parsing convention**: org-all mode requires a trailing slash
(\`<org>/\`). A bare slug (no slash) is always treated as a project slug
and triggers a cross-org project search via \`findProjectsBySlug\` —
consistent across \`project list\`, \`issue list\`, \`team list\`, and
\`repo list\`
- **\`team list org/project\`**: fetches teams scoped to that project
(via \`listProjectTeams\` endpoint)
- **\`repo list org/project\`**: repos are org-scoped; shows all repos
in the org with a note that the project part is ignored
- All 1874 unit tests pass; typecheck and lint clean

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Author: BYK

AGENTS.md

@@ -319,6 +319,20 @@ import type { SentryContext } from "../../context.js";
 import { getAuthToken } from "../../lib/config.js";
 ```
 
+### List Command Infrastructure
+
+Two abstraction levels exist for list commands:
+
+1. **`src/lib/list-command.ts`** — `buildOrgListCommand` factory + shared Stricli parameter constants (`LIST_TARGET_POSITIONAL`, `LIST_JSON_FLAG`, `LIST_CURSOR_FLAG`, `buildListLimitFlag`). Use this for simple entity lists like `team list` and `repo list`.
+
+2. **`src/lib/org-list.ts`** — `dispatchOrgScopedList` with `OrgListConfig` and a 4-mode handler map: `auto-detect`, `explicit`, `org-all`, `project-search`. Complex commands (`project list`, `issue list`) call `dispatchOrgScopedList` with an `overrides` map directly instead of using `buildOrgListCommand`.
+
+Key rules when writing overrides:
+- Each mode handler receives a `HandlerContext<T>` with the narrowed `parsed` plus shared I/O (`stdout`, `cwd`, `flags`). Access parsed fields via `ctx.parsed.org`, `ctx.parsed.projectSlug`, etc. — no manual `Extract<>` casts needed.
+- Commands with extra fields (e.g., `stderr`, `setContext`) spread the context and add them: `(ctx) => handle({ ...ctx, flags, stderr, setContext })`. Override `ctx.flags` with the command-specific flags type when needed.
+- `resolveCursor()` must be called **inside** the `org-all` override closure, not before `dispatchOrgScopedList`, so that `--cursor` validation errors fire correctly for non-org-all modes.
+- `handleProjectSearch` errors must use `"Project"` as the `ContextError` resource, not `config.entityName`.
+
 ## Commenting & Documentation (JSDoc-first)
 
 ### Default Rule

plugins/sentry-cli/skills/sentry-cli/SKILL.md

@@ -194,9 +194,10 @@ List issues in a project
 
 **Flags:**
 - `-q, --query <value> - Search query (Sentry search syntax)`
-- `-n, --limit <value> - Maximum number of issues to return - (default: "10")`
+- `-n, --limit <value> - Maximum number of issues to list - (default: "10")`
 - `-s, --sort <value> - Sort by: date, new, freq, user - (default: "date")`
-- `--json - Output as JSON`
+- `--json - Output JSON`
+- `-c, --cursor <value> - Pagination cursor — only for <org>/ mode (use "last" to continue)`
 
 **Examples:**
 
@@ -433,25 +434,27 @@ Update the Sentry CLI to the latest version
 
 Work with Sentry repositories
 
-#### `sentry repo list <org>`
+#### `sentry repo list <target>`
 
 List repositories
 
 **Flags:**
 - `-n, --limit <value> - Maximum number of repositories to list - (default: "30")`
 - `--json - Output JSON`
+- `-c, --cursor <value> - Pagination cursor (use "last" to continue from previous page)`
 
 ### Team
 
 Work with Sentry teams
 
-#### `sentry team list <org>`
+#### `sentry team list <target>`
 
 List teams
 
 **Flags:**
 - `-n, --limit <value> - Maximum number of teams to list - (default: "30")`
 - `--json - Output JSON`
+- `-c, --cursor <value> - Pagination cursor (use "last" to continue from previous page)`
 
 **Examples:**
 
@@ -581,9 +584,10 @@ List issues in a project
 
 **Flags:**
 - `-q, --query <value> - Search query (Sentry search syntax)`
-- `-n, --limit <value> - Maximum number of issues to return - (default: "10")`
+- `-n, --limit <value> - Maximum number of issues to list - (default: "10")`
 - `-s, --sort <value> - Sort by: date, new, freq, user - (default: "date")`
-- `--json - Output as JSON`
+- `--json - Output JSON`
+- `-c, --cursor <value> - Pagination cursor — only for <org>/ mode (use "last" to continue)`
 
 ### Orgs
 
@@ -615,25 +619,27 @@ List projects
 
 List repositories
 
-#### `sentry repos <org>`
+#### `sentry repos <target>`
 
 List repositories
 
 **Flags:**
 - `-n, --limit <value> - Maximum number of repositories to list - (default: "30")`
 - `--json - Output JSON`
+- `-c, --cursor <value> - Pagination cursor (use "last" to continue from previous page)`
 
 ### Teams
 
 List teams
 
-#### `sentry teams <org>`
+#### `sentry teams <target>`
 
 List teams
 
 **Flags:**
 - `-n, --limit <value> - Maximum number of teams to list - (default: "30")`
 - `--json - Output JSON`
+- `-c, --cursor <value> - Pagination cursor (use "last" to continue from previous page)`
 
 ### Logs