One would expect the class names related to the new screen input handling to be named consistently. The AbstractInput class is implemented by the MouseInput, KeyInput, and Click classes. All three are records, though the Click class contains a MouseInput record component. The CharInput class is entirely unrelated.
Some of these inconsistencies come from a somewhat poor conceptualization of user interface events, and other inconsistencies come from rigidly applying names from libraries that insist on following outdated low-level hardware ideas. Ideally, better names can be chosen.