In the password fields, I don't know how anyone either writing or using a password manager doesn't consider unambiguous glyphs to be critical. It's a password manager not a greeting card designer.
They think they have solved this by specifying the font to be monospace in the password fields (maybe notes too I don't remember).
I submitted an issue complete with pictures of passowords written in monospace fonts in KeePassXC where the characters are ambiguous.
It shouldn't even require pictures to convey the problem. Once someone says "the property "monospace" and the property "unambiguous" are two dufferent properties. It's an unsafe and in fact broken assumption.", you'd think that would shed all the light necessary.
But what more do you do when tbey don't see it even WITH pictures? Fork it yet again? Just to add a config option to let the user or desktop integrator select an arbitrary font for some display fields?
What really bugs me is, they didn't say "yeah that would be better but it's hard and we don't know when anyone might get to it" No, they think it's already done.
Failing to get that idea across really made me wonder about the parts of their work that aren't so visible.