issue list caps at ~50 results — no pagination, --limit >50 silently ignored

[q-soriarty]

Summary

copia-cli issue list returns at most ~50 issues and does not paginate. Passing --limit greater than the server's per-page maximum (≈50) is silently capped, so the command reports an incomplete set without any warning.

Reproduce

On a repository with more than 50 issues (e.g. 72):

copia-cli issue list -R my-org/my-repo --state all --limit 300 --json number | jq length
# => 50   (expected: 72)

Expected

All matching issues are returned — either by honoring --limit across multiple pages, or via an explicit --paginate flag.

Actual

Only the first page (~50, the Gitea API per-page maximum, ordered by updated_at) is returned. The remaining issues are silently omitted. There is no --paginate flag, and --limit > 50 has no effect beyond the first page.

Impact

Silent data loss. Any script or migration that trusts issue list as the complete set gets a truncated result and a false sense of completeness. (Hit this during a real issue migration — 22 of 72 issues were missing.)

Suggested fix

Auto-paginate in issue list (loop page=1,2,… until an empty page), honoring --limit as the total cap. The same likely affects pr list, label list, and other list commands. Consider a shared paginating helper.

Workaround

Manual paging via the raw API:

copia-cli api "repos/my-org/my-repo/issues?state=all&type=issues&limit=50&page=N"

Environment

copia-cli version 1.1.2