Despite almost everything being in one big repo, it has silos. Not everyone has read access to everything. Some code, like the important bits of Search, is only available on a need-to-know basis.
So what happens if search adopts your internal library and your update to it breaks search? Do you need to get someone from the search team to go investigate? How is that prioritised?
The tooling is such that you will know if a change will break something in a silo before it is submitted. You then work with the affected team. It’s not a big deal.