Lying about what they are doesn't change the underlying issue:
> they're integrity errors, a query is putting the db in an invalid state and thus rejected. Because the state is invalid, I'm not sure how the db would progress to get more errors.
I agree with you that it's logically insensible to consider them "errors" because the resolution of the current constraint may change the downstream interpretation.
However it's a tremendously useful development tool.
> they're integrity errors, a query is putting the db in an invalid state and thus rejected. Because the state is invalid, I'm not sure how the db would progress to get more errors.