As the architecture has evolved, most of MIDIHub’s original responsibilities have found more natural homes in AROS: BLE MIDI in the Bluetooth stack, network MIDI in CAMD devices, mDNS/DNS-SD in Bonami, and dynamic endpoint support as a CAMD evolution. What is essentially left of MIDIHub now is MIDIHub.prefs, the persistent MIDI router, and the software synth/SoundFont support. One important role of MIDIHub.prefs is to expose these modern MIDI capabilities through a coherent interface while still presenting them in a way that fits the legacy CAMD model. Would it make more architectural sense for the router and software synth to also become CAMD/AROS components of their own, leaving MIDIHub mainly as the preferences/integration UI — or is there still value in keeping these three pieces together as a MIDIHub subsystem?