If that happens again, the first oracle reporting the new price will be filtered out. Once more oracles start reporting a similar price, the mean will get closer to this price, and any new oracle reports close to the new price will no longer be filtered. The same check is implemented in the oracle client here, and the behaviour should be the same.
Currently, if the price deviation check fails, the oracle client will not send a report for that assigned block but should not stop reporting completely. The oracle client will stop reporting if the new price trips the circuit breaker.
There’s also another proposed change for an on-chain circuit breaker that would have halted mento trading in this situation. Maybe Moola would benefit from this also, but I think all protocols should have protections in place when using oracles.