Config logic that turns on functionality (often a measurement plugin) only if a package is setup by EUPS used to be a common pattern for reasons I don't call. It's now widely regarded as an antipattern because it makes it easier to silently get a configuration you didn't ask for or expect.

We should audit all active meas_extensions_* packages, all obs_* packages, pipe_tasks setDefaults methods, and meas_modelfit for that kind of config logic and remove it.

Seems like a good Party Programming activity.