CoalesceRecovering After Being Offline
What your node checks when it starts back up.
Startup always re-checks whether the cluster is still open on-chain, even if you were offline when it closed.
If the cluster closed while you were away
If your node finds a recognized cooperative close, it reports the final settled payouts itself,
and bal shows those. Nothing further to do.
If it finds a spend it doesn't recognize
If startup finds a spend from the funding output that it can't recognize as a cooperative close
it knows about, it prints a WARNING and refuses send, propose, and coopclose until
that's resolved, rather than risk acting on stale balances.
Don't work around this warning by guessing
A WARNING at startup means something happened on-chain that your node can't explain from its
own state. Investigate what actually happened (check the transaction on a signet block
explorer, compare notes with other members) before doing anything else. Don't restart with
-enforce disabled to "get past it."