Woodpecker Ci Rate Limits

Woodpecker publishes no rate limits and emits no rate-limit signal. Live responses from the reference instance carry no X-RateLimit-*, no RateLimit-* and no Retry-After header on either a 200 or a 401. There is no rate-limiting section in the server configuration documentation. This is consistent with the deployment model — the API is served by an operator's own single-tenant server, so throttling is whatever the operator puts in front of it. An agent integrating with a Woodpecker server therefore has no runtime backpressure signal at all and must implement its own pacing. Recorded as an honest zero.