fix: correct pagination limits for getLedgers and getTransactions in OpenRPC spec

[miguelnietoa]

The pagination limit descriptions for getLedgers and getTransactions reference a maximum of 10,000, but the actual defaults in https://github.com/stellar/stellar-rpc/blob/1a9a97b3f533f91c509661094e71b269d33b735a/cmd/stellar-rpc/internal/config/options.go are:

• getEvents: max 10,000, default 100 (correct in docs)
• getLedgers: max 200, default 50
• getTransactions: max 200, default 50

Confirmed empirically against both testnet (soroban-testnet.stellar.org) and mainnet (soroban-rpc.mainnet.stellar.gateway.fm) - requesting limit=201 returns "limit must not exceed 200".

[Copilot]

Pull request overview

This PR corrects the pagination limit parameter descriptions in the Stellar RPC OpenRPC specification so they match the actual server-enforced defaults and maximums for getLedgers and getTransactions.

Changes:

• Update getLedgers pagination limit description to max 200 / default 50.
• Update getTransactions pagination limit description to max 200 / default 50.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ElliotFriend]

Hey, @miguelnietoa! thanks so much for helping to fix this! The file you've modified will actually be over-written at build-time. the "source" of this OpenRPC specfile lives in the /openrpc/src/stellar-rpc directory of this repo. looks to me like you'll want to

1. modify only this schema file,
2. and then run yarn rpcspec:build && yarn rpcspec:validate from the repo's root directory
3. commit the "bundled" OpenRPC specfile (which will probably actually be identical to the change already in your PR), and the modified schema file.

If you run into any trouble with steps 2 or 3, i'd be happy to help out by pushing some changes for you, too.

Thanks again!

[miguelnietoa]

Hi @ElliotFriend 👋🏻
Thanks for pointing me the right direction. I updated the source files instead of editing the generated output directly. However, I replaced the shared Pagination schema/contentDescriptor with method-specific ones (PaginationEvents, PaginationLedgers, PaginationTransactions) since each method has different limits.

Lmk if it needs further changes!

[ElliotFriend]

@miguelnietoa thanks so much for those changes!

This is probably a bit of a nitpick, but I'd prefer to see these Pagination* content descriptors and schemas grouped together into a single file, similar to how we have a few *Hash schemas in this file.

Everything else looks right to me, though. And, I'm not actually gonna "die on that hill" about putting things in a single file. Let me know what you think!