Ensure that the balancer is using Broflake in the way that Broflake ought to be used

Once a transport starts failing, the balancer won't use it again unless all the other transports are failing.

This makes it difficult (impossible?) to measure whether Broflake is working or not, since Broflake, as a p2p system subject to network churn, is expected to fail intermittently all the time.

I suspect what will happen in most cases is that the balancer will try to dial using Broflake for the first time -- the dial will fail, because the Broflake client hasn't yet acquired a peer connection -- and the balancer will never attempt to use Broflake again.

Start by tracing how the balancer selects transports after a dial failure, then inspect how Broflake reports or recovers from its initial lack of a peer connection. The issue provides no file or test names. Done should mean intermittent Broflake failures do not permanently exclude it, so its behavior can be measured under network churn.