**BROKEN** anchor: could not afford fee 0sat from change 330sat, reducing fee

I noticed this error message in my log when my node force-closed a channel about which its peer claimed to have no knowledge.

```
2025-05-22T00:28:23.656Z UNUSUAL 03…00-chan#255689: Peer permanent failure in CHANNELD_NORMAL: channeld: received ERROR channel 01…7e: Unknown channel for WIRE_CHANNEL_REESTABLISH (reason=protocol)
2025-05-22T00:28:23.656Z INFO 03…00-chan#255689: State changed from CHANNELD_NORMAL to AWAITING_UNILATERAL
2025-05-22T00:28:23.673Z DEBUG 03…00-chan#255689: We have 3 anchor points to use
2025-05-22T00:28:23.683Z DEBUG 03…00-lightningd: peer_disconnect_done
2025-05-22T00:28:23.683Z DEBUG 03…00-connectd: Will try reconnect in 300 seconds
2025-05-22T00:28:23.684Z DEBUG plugin-funder: Cleaning up inflights for peer id 03…00
2025-05-22T00:28:23.684Z DEBUG 03…00-connectd: peer_downgrade
2025-05-22T00:28:23.712Z DEBUG 03…00-chan#255689: Low-priority anchorspend aiming for block 899788 (feerate 253)
2025-05-22T00:28:23.723Z **BROKEN** 03…00-chan#255689: anchor: could not afford fee 0sat from change 330sat, reducing fee
2025-05-22T00:36:43.296Z DEBUG 03…00-chan#255689: Got UTXO spend for 7e…01:0: 65…b7
2025-05-22T00:36:43.297Z UNUSUAL 03…00-chan#255689: Peer permanent failure in AWAITING_UNILATERAL: Funding transaction spent: onchain txid 65…b7 (reason=onchain)
2025-05-22T00:36:43.298Z UNUSUAL 03…00-chan#255689: Not dropping our unilateral close onchain since we already saw 65…b7 confirm.
2025-05-22T00:36:43.298Z INFO 03…00-chan#255689: State changed from AWAITING_UNILATERAL to FUNDING_SPEND_SEEN
```

Is that `**BROKEN**` message anything to worry about? If not, then it shouldn't be logged at the `BROKEN` level.

This happened on CLN 25.02.2.