Add caching strategy documentation for API routes

[rogerSuperBuilderAlpha]

Path: lib/rate-limit-server.ts, app/api/*/route.ts
Size: S

Problem / Context: API routes have comment about revalidateTag() (line 465 of signup route) but caching strategy is scattered. Developers don't know cache TTLs.

Proposed scope:

• Create docs/API_CACHING.md
• Document: which endpoints are cached, TTL, revalidation strategy
• Explain revalidateTag usage (hack-a-sprint-2026 showcase, event signup)
• Link to Next.js caching guide

Acceptance criteria:

• Caching strategy documented for ≥10 API routes
• TTLs explicit (e.g., 30s cache + revalidateTag on mutation)
• Examples provided

---

This issue was filed as part of the Sports Hack 2026 contributor audit. Grab it if it looks interesting — merged PRs move you up the ranking for one of the 80 confirmed seats. Before starting, drop a comment so we don't double-assign.

[mrrCarter]

Opened PR for this: #1356