I believe there is no compelling reason to remove the 'Reactive' softfork deployment method on the pretense of building consensus. Quite the opposite, the existence of the 'Reactive' option acts as an additional lever, actually leading to greater consensus.
The new draft of the BIP has been posted to the bitcoindev mailing list:
https://groups.google.com/g/bitcoindev/c/nOZim6FbuF8/m/d4tkNi0DAQAJ
The code has been published here:
I'm looking forward to hearing your feedback.
Discussion
I think the same. Stop making compromises with clearly bad actors.
Perhaps he compromise is not as much for the bad actors as it is for more of the middle?
I dunno...