inputbooster

Two of our classes broke a Mixin rule:

The helper that calls the accessor mixins (MixinAccess) was inside the package declared by inputbooster.mixins.json. Mixin never loads anything from a mixin package unless it is a mixin itself. The three accessor mixins (GuiAccessor, KeyMappingAccessor, MinecraftClientAccessor) were declared as abstract classes. Mixin only treats a mixin as a loadable accessor when it is an interface, so the class form could never have been called either. The Could not read every key binding; using vanilla defaults for the rest warning you saw at startup was this same failure, already swallowed. What we changed MixinAccess moved to dev.inputbooster.access. The three accessors are now interfaces, which is the form Fabric API itself ships (KeyMappingHelper and ScreenAccessor work the same way). A swallowed failure in the key-binding reader is now logged with its cause instead of being reduced to a silent fallback. New tests fail the build if a non-mixin class is added to the mixin package, if a runtime-called accessor is not a loadable interface, or if any class outside the mixin package references one that Mixin cannot load. The corner HUD fix from 3.1.6 is included and now works.