Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Usage & LimitsArea: what it touches
New FeaturesKind: in v2.1.248,
What probably matters to youSection of the release
A /limit-reset action and interrupt path are wired in, driven entirely by a server-fetched status block.
What
A new interrupt reason is threaded through the turn abort paths so the limit-reset offer can stop work in progress, and a new command kind entry marks /limit-reset as an action. The status block driving it is fetched from the server, so whether it ever appears depends on what the server returns.
Details
The reason joins three interrupt/abort classification switches, and the two menu states join the queue-state switch.
Status fetches that return a fieldless or non-object body are warned about rather than treated as data.
A limits comparison now also checks that the stored reset time matches the wall reset time.
Evidence
[juniper-tide] status fetch returned a fieldless or non-object body (in-band error)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
