This all sounds to me like we are trying to fix PVP by adding errors. I'm ok to declare
PVP bankruptcy. If it's too hard to be practically used, we need to find a different solution.
But this problem to me sounds more like we rather need some automation? What we
seem to essentially want to achieve is guarantee that component integration is not
faulty? It all sounds to me like what we really want is an automated solution that flags
packages that were broken by changes in their dependencies. And then be trivially able
to address those (and open PRs). Though I guess you'd also need to deal with
version bounds, the inverse of missing-fields would be overspecified fields, and thus
the library that depends on something that added more fields, now needs a hard lower
bound after adding the fields?
automation. Maybe reboot hackage matrix in some form? Can someone point me in
the right direction?
Best,
Moritz