Weekly JSON formatting: preserve a stable canonical style

For recurring JSON files, choose indentation, key-order policy, newline style, and whether trailing newlines are required. Format from the source and compare parsed values before and after. Keep a small test with Unicode escapes, nested arrays, and nulls to catch accidental transformations. If the receiver cares about exact bytes—for signatures or hashes—do not reformat without understanding the impact. Consistent style helps reviews only when semantics and integrity remain intact.