You'll notice
Useful3 Signal3
Plan mode no longer flags a false mismatch just because JSON keys were ordered differently.
What's wrong with this entry?
Anonymous. No account, no email.
What
Plan mode compares a stored copy of its decision limits against the current ones. Both sides are now parsed and canonicalised before comparing, so an identical payload with different key order or spacing no longer counts as a mismatch. If parsing throws, it falls back to comparing the raw strings.
Evidence
capsJson
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.235
Very large plans cannot be approved
Both mention plan mode
-
v2.1.235
Plans over 200,000 characters cannot be approved
Both mention plan mode
-
v2.1.239
Resuming a session that was in plan mode puts you back in plan mode
Both mention plan mode