API-235: document global --limit/--page pagination flags in nansen schema

[gulshngill]

Problem

buildPagination(options) in src/cli.js reads --limit/--page at six shared call sites (smart-money, profiler, token, perp, points, prediction-market), plus a local copy in src/commands/research.js for the historical-* commands — but schema.json globalOptions never listed either flag. Agents consuming nansen schema (the machine-readable CLI contract) could not discover pagination at all, nor the API-side fact that profiler endpoints and general endpoints have different per_page rules.

Change

Docs-only: adds limit and page to globalOptions in src/schema.json.

• limit → pagination.per_page. Description states the split verified against the live OpenAPI spec at docs.nansen.ai: general endpoints (PaginationRequest) default 10, max 1000; profiler address endpoints (ProfilerPaginationRequest) default 20, max 100. It also names the commands that declare their own limit with different semantics (search, token top-tokens, trade limit-order list), the endpoints that reject/ignore pagination (token ohlcv, profiler perp-positions, historical-token-flow-summary), and the CLI-side per_page: 100 default on profiler labels.
• page → pagination.page, 1-based, default 1.

No runtime code touched — nansen schema --full and nansen schema <cmd> already render globalOptions, so the entries surface automatically. Changeset included (patch).

Not a duplicate of #491, which adds command-specific options (alerts/batch/screener) and does not touch globalOptions. Related: ECINT-6899 tracks the API side; this PR is the CLI side.

Validation

• npm test: 2031 passed, 2 skipped
• npm run lint: clean
• node src/index.js schema --full exposes both new entries with descriptions
• Independent Codex code review: APPROVED after fixing one finding (the description originally claimed trade commands ignore --limit, contradicting trade limit-order list)

🤖 Generated with Claude Code

[nansen-pr-reviewer]

pr-reviewer Summary for #9ccf8a2

✅ No issues found

The code review completed successfully with no findings.

Review effort: 1/5 (Trivial)

Summary

This PR adds limit and page to globalOptions in src/schema.json, making global pagination flags discoverable via nansen schema. No runtime code is touched.

The descriptions are accurate: the endpoint-type split (general default 10/max 1000 vs. profiler default 20/max 100), the carve-outs for commands with their own limit semantics (search, token top-tokens, trade limit-order list), and the non-supporting endpoints (token ohlcv, profiler perp-positions, historical-token-flow-summary) all match the implementation in src/cli.js and src/commands/research.js. The limit entry correctly omits a default (since API-side defaults differ by endpoint) and page correctly carries default: 1 consistent with buildPagination. The changeset names the right package and uses an appropriate patch bump. No findings.

---

Token usage: 1,284 input, 3,137 output, 263,263 cache read, 23,501 cache write | Usage Guide

New pushes are reviewed automatically with a 10-minute cooldown between reviews. To request a review at any time, comment @nansen-pr-reviewer re-review.

[nansen-pr-reviewer]

Auto-approved

This PR was automatically approved because:

• Claude recommends approval
• Claude assessed this as a minimal effort change
• The effort level is within the auto-approval threshold of 2
• No high or critical issues were detected

If you have any concerns, please request a manual review.