These assertions exist to detect double-deducting values when we update descendants. However, negative fees are possible with prioritisetransaction so it doesn’t make sense to check this.
Leave the check for sizes because those are never negative.
Fixes #34234