Two new usage-limit notices are registered, tied to menu rows behind an off gate.
Notice ids register at startup but the surrounding menu gate defaults false.
What's wrong with this entry?
Session start registers two new usage-limit notice ids, one high priority and one medium, matching the new actionable and already-spent rows in the usage-limit menu. Their labels are looked up at runtime, so the source does not spell out the offer. No named flag sits on the registration itself, though the surrounding menu reads a separate gate that defaults to false.
juniper-tide-spent
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.236
Extra-usage panel now shows for team and enterprise accounts
Both mention usage limit
-
v2.1.236
Wrap-up hint near the usage limit is now per-plan and once per window
Both mention usage limit
-
v2.1.236
Visible notice when approaching the 5-hour usage limit
Both mention usage limit