Fake usage-limit states for testing ship in the build but every accessor returns nothing.
A rate-limit mock harness covering session limits, overage, seat-tier credits and fast-mode limits is bundled but hard-disabled.
What's wrong with this entry?
A component holding fake usage-limit states (session limit reached, overage exhausted, seat-tier zero credit limit, fast-mode limits, trial and overage payloads) is bundled in this build but cannot affect anything: every accessor that would read it returns null on its first line, leaving the real body unreachable.
seat-tier-zero-credit-limit
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Rate-limit prompts resolve model aliases to the model that actually answers
Both mention rate limit
-
v2.1.234
Quota rejections feed a new auto-resume controller
Both mention rate limit
-
v2.1.239
Spend and rate limit notices say when the limit resets
Both mention rate limit