pull down to refresh

The specification and bitcoin core implementation has no sensible resource consumption limits on witness sizes. That's all it was. As a Go programmer, I am also very avid about keeping resources under control. It actually helps a lot with security as well. Resource exhaustion attacks can destroy peer to peer networks functionality.
Well yeah the Taproot BIP spec explicitly removes the previous sigop and witness stack size limits, only to be bound by the blocksize instead.
Hence I would consider the bugs as vulnerabilities as they left lnd in a semi-glitchy state.
I agree with all your other points though.