Deadline JSON diff: inspect the highest-risk fields first

When reviewing JSON under a deadline, parse both versions and compare high-impact fields first: identifiers, permissions, endpoints, feature flags, and amounts. Check additions and removals as well as changed values. Watch type changes, null versus missing keys, and arrays whose order affects behavior. Then scan the rest of the diff before approving. Preserve the baseline and do not treat a formatting-only comparison as proof that the data is valid for its consumer.