Defining expected music metadata behavior

[elfalem]

I don't even think it needs to be a plugin. If the default setting matched the historical choices, then upgrades would incur no change.

Yes, that logic specifically doesn't need to be a plugin. But the code that provides the metadata from a specific source (whether online or local) should be a plugin. That would enforce a clear boundary. And default/popular plugins such as MusicBrainz can be shipped with the core server.

I'm not sure that protecting users from a "hostile" admin is an achievable design philosophy. I think it blocks not only this change but also many possible improvements.

 I agree. It's impractical for this to be per-user. It should remain as a global configuration that the admin manages.