Since foreman-maintain is not available on Debian (and I personally don’t use foreman-maintain) I’d prefer for it to live in the foreman-proxy package. That also ensures it’s kept in sync with the codebase. The settings.yml is not an interface and if we ever make changes, it’d be horrible to try and detect it in foreman-maintain. It’s also not aimed at end-users but rather developers who try to debug issues.
That’d be trying to add too much logic into it. There’s an example piping it to Redirecting to jqlang.github.io which can also do filtering and in general is much better for that. The unix philosophy is the right one here 