InstallReadiness is not really necessary. It's only used in one place (the BrowserController) and even then, it's just a relatively thin wrapper around Package Manager's StatusCheckTrait.
Merge InstallReadiness into BrowserController and remove it as a service.
Closed: won't fix
2.0
Code
Refactors an existing API or subsystem for consistency, performance, modularization, flexibility, third-party integration, etc. May imply an API change. Frequently used during the Code Slush phase of the release cycle.
📌 Too slow to validatePackageManager() on every page Needs review has identified a reason to keep InstallReadiness around, so I think I can close this out.