You'll notice
Useful3 Signal3
Hitting your plan cap while publishing an artifact now stops immediately instead of retrying in the background.
What's wrong with this entry?
Anonymous. No account, no email.
What
A 429 from the publish endpoint used to always trigger backoff and retry. The body is now inspected first, and if the rejection is a plan cap the attempt stops immediately. A related path shows a rate-limit message ending with an instruction to try again after the reset.
Evidence
try again after the reset.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.