xmax before xmin in superset bbox

[mdsumner]

In this example I'm wondering why xmax (longitude) comes before xmin?

u="https://objects.eodc.eu/e05ab01a9d56408d82ac32d69a5aae2a:sample-data/tutorial_data/cpm_v253/S2B_MSIL1C_20250113T103309_N0511_R108_T32TLQ_20250113T122458.zarr/.zattrs"
curl -s $u | grep \"bbox\" -A 5
curl -s $u | grep \"bbox\" -A 5
        "bbox": [
            7.871918704100081,
            44.137996748196564,
            6.45686051699677,
            45.148073182871244
        ],
        "bbox": [
            7.871918704100081,
            44.137996748196564,
            6.45686051699677,
            45.148073182871244
        ],

In all contexts I assume bbox means xmin,ymin,xmax,ymax - except in the .zattrs/.zmetadata as above.

If I assume it's meant to be 6.45686051699677, 44.137996748196564, 7.871918704100081, 45.148073182871244 then that gives a slightly larger utm bbox than the one of the individual assets: 296577.1, 4887794.6, 413081.4, 5004299.4 vs the clean proj:bbox 300000, 4890240, 409800, 5000040, and I wonder why that discrepancy? Thanks!