They specifically address areas where the default to pre-commit review, for the reason you just called out:

We switch to pre-commit reviews instead of the usual post-commit review flow if the potential errors/mistakes are costly and can cause significant problems. Some examples of such cases are:

    Touching code which deals with privacy and anonymity of users.
    Touching a core abstraction since a lot of other code might depend on it.
    Touching some parts of the infrastructure where mistakes can cause a downtime.