Class NoopRateLimiter<TRuntime>

Remarks

Unlike the other no-ops, this one takes a decision in its constructor, because "no limiter" has two defensible meanings and picking silently is how an open endpoint gets shipped:

• Open (the default) — every caller is admitted. Right when the limiter protects an upstream against load, where its absence is a capacity problem.
• Closed — nobody is admitted. Right when the limiter is the only thing between an unauthenticated endpoint and someone else's bill, where its absence should be a visible outage rather than a silent open door.

It mirrors rateLimit.failOpen in the configuration layer deliberately: the same question, answered in the same two ways, whichever implementation is in use.