Indeed, it needs a "I provide only Settings components" module-type, such as "settings".

I do not condone this module, I think it belongs in stripes-core because it is inherently part of the platform and consumed by other modules. If it is to exist, it breaks the convention of no client-side inter-module coupling so we need to establish APIs and conventions for that. And it probably needs a module type other than 'app'?

I'm not going to write more hard-wiring code into stripes-core to make the Organization settings available, I'm going to fix the general case – .

I have created and pushed a do-nothing module. At this stage it's quite a good template for creating new modules from, as I noted in a new section of the Developer Guide at https://github.com/folio-org/stripes-core/blob/master/doc/dev-guide.md#modules

In the mean time, I have done a shameful thing:
https://github.com/folio-org/stripes-core/commit/ed64153da4c0410e3e3e44c4bcd0ec6aa8e6068d