Publish a public API rate-limit and quota documentation page

[Akatenvictor]

Problem / Context

Rate limits exist in code but are not documented anywhere a third-party integrator could discover them.

Proposed approach

Document current limits per route category (auth, upload, playback, general) in the API reference.

Acceptance criteria

• Every rate-limited route category is documented with its actual limit
• Kept in sync when limits change

[drips-wave]

@Akatenvictor This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets

[drips-wave]

@Akatenvictor This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets

[drips-wave]

@Akatenvictor This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets