Yep. The best way to pushback is to ask your manager, "We'll do it fast since you are asking for it. What is the plan for contingencies in case things break?"

*when things break

*if, it’s an increasing probably, not a guarantee

I’ve seen code with next to no verification turn out great.

I don’t think the manager needs a button to remember he’s responsible for the decisions, usually it’s the other way around, devs having to remember they’re not; I’ve been too many times the manager putting it on zero only to hear, “You can’t do that it has to be at least a nine !!!”.

Letting your hands type an error is a trust fall that nobody is willing to make in an environment without a much higher than usual amount of trust.

Did you put it in writing, in uncertain terms?

I’ve seen maybe one out of ten managers actually take responsibility when things go to shit.