Inconsistent API error results for chain reports

If I try to request the chain report for chain 13, I get the following structure of error message:

{
    "success": [
        false
    ],
    "msg": [
        "This report is no longer available"
    ]
}

As far as I know, this used to be the shape of all error results from the chain report API, so you could check for failure by looking if there is a "success" field set to false.

However, now, if I try to request the chain report for chain 1300000000, I instead get the following structure of error:

{
    "code": [
        6
    ],
    "error": [
        "Incorrect ID"
    ]
}

It seems really strange that the API should report errors with two different structures of error message, so I have to try two different things to check if there was an error. This must be something that was overlooked in changing the chain report API at some point, right? I'd really like it if error results had consistently named fields...

My problem isn't really that they are different error messages - that makes sense - but that the names of the fields in the error message are different, so there's no clean way to check if I got an error back - there is no one field that is guaranteed to exist whenever there was an error.

The change I'd suggest is that either both errors have the structure "success" / "message" or both have the structure "error" / "code" - I think the latter is more consistent with how the API gives errors for other things, but the most important thing is I think to be consistent.

In fact, the most consistent thing would be to have it return not

{
    "chainreport": {
        "code": [
            6
        ],
        "error": [
            "Incorrect ID"
        ]
    }
}

but

{
        "error": {
                "code": 6,
                "error": "Incorrect ID",
        },
}

since that is how an Incorrect ID error appears for every other API endpoint.