Corestack Rate Limits

CoreStack publishes NO API rate limits. The External APIs guide covers authentication, HTTP verbs, response codes, data types and pagination but says nothing about throttling. A full-text search of the documentation index (1,132 entries, every guide and every one of the 800+ reference pages) turns up no rate limit, throttling, quota or 429 page. The published 2.3MB specification declares 429 on zero of its 838 operations and declares no RateLimit-*, X-RateLimit-* or Retry-After response header anywhere. An integrator therefore has no published ceiling and, more importantly, no runtime signal: there is no header to read, no documented status code to catch, and no back-off guidance. Combined with the absence of idempotency (see conventions/), this leaves a client with no safe retry story at all — it cannot tell that it is being throttled, and it cannot safely retry the write if it is.