Frayt Rate Limits

FRAYT publishes no rate limits and emits no rate-limit signal. This was checked three ways and all three are negative: (1) the docs — the Swagger UI at /docs/api/v2.2 and its full info.description narrative contain no limits, quota or throttling section; (2) the OpenAPI — no operation declares a 429 response, and the strings "429", "RateLimit", "Retry-After", "throttle" and "quota" do not appear anywhere in the 106KB spec; (3) live responses — two unauthenticated calls (POST /api/v2.2/oauth/token -> 403, GET /api/v2.2/matches/{id} -> 401) returned no X-RateLimit-*, no RateLimit-* and no Retry-After header. An agent integrating FRAYT therefore has NO runtime backoff signal and must implement its own conservative retry policy. This is compounded by the absence of any idempotency key (see conventions/frayt-conventions.yml) — a blind retry of POST /matches can dispatch a second driver to a real pickup.