{"version":"2.1.232","anchor":"plan-mode-no-longer-sees-a-false-mismatch-from-key-ordering","canonical_anchor":"plan-mode-no-longer-sees-a-false-mismatch-from-key-ordering","heading":"Plan mode no longer sees a false mismatch from key ordering","tier":"notice","area":"Plan Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/plan-mode-no-longer-sees-a-false-mismatch-from-key-ordering","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Plan mode no longer sees a false mismatch from key ordering\n\nPlan mode no longer flags a false mismatch just because JSON keys were ordered differently.\n\n**What**\n\nPlan 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.\n\n**Evidence**\n\n`capsJson`\n\n- Area: Plan Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}