Correct. It’s not YAML’s fault that the parsers haven’t caught up to its fixes.
but it is YAML's fault that it introduced this silly mistake in the first place
No it's YAML's fault - the fact that type coercion was once part of the serialization spec and not part of an adjacent schema spec is a tragic mistake. Now there's a bunch of outdated parsers that exhibit the issue and some that have it fixed. Meaning even more inconsistency and frustration. In an ideal world, YAML just shouldn't exist.