The documentation implies that the data types text and varchar are equivalent, but this is not the case with this test in Postgresql version 16.
Fair point. But I'd rather further emphasize that char should just be avoided so this and other unexpected outcomes simply do not manifest in a real database scenario. Rather than try and document how odd it's behavior is when dealing with intra-textual type conversions.