It said that it's not against the consensus rues but the transaction was indeed non-standard that's why nodes are rejecting it.
that is really messed up! every single documentation that i have ever seen has always said "it must not be compressed or it will not be mined". now i went back and checked the out, they are all are ambiguous about it!
take BIP143 for example:
https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki#restrictions-on-public-key-typeAs a default policy, only compressed public keys are accepted in P2WPKH and P2WSH. Each public key passed to a sigop inside version 0 witness program must be a compressed key: the first byte MUST be either 0x02 or 0x03, and the size MUST be 33 bytes. Transactions that break this rule will not be relayed or mined by default.
from bitcoincore.com:
https://bitcoincore.org/en/segwit_wallet_dev/#creation-of-p2sh-p2wpkh-addressP2SH-P2WPKH uses the same public key format as P2PKH, with a very important exception: the public key used in P2SH-P2WPKH MUST be compressed, i.e. 33 bytes in size, and starting with a 0x02 or 0x03. Using any other format such as uncompressed public key may lead to irrevocable fund loss.
the orange parts are the ambiguity! why did they do this?!
It's not at all ambiguous, it states it exactly how it is.
It was the wish with segwit to prohibit the use of uncompressed keys. But there was a concern that problem's like OP's would arise from incompetent buggy software-- potentially involving really large funds losses. In an abundance of caution these the rule was made initially standardness-only. It has turned out to be less of an issue than had been feared (the OP's is the only sizable case I've heard of, at least).