managed pluggable transports should be able to pause Tor's circuit-building?

Hooman with his Skypemorph transport (http://archives.seul.org/tor/dev/Mar-2012/msg00093.html) notes that when Tor first starts, and starts his transport, it takes his transport a minute or two to become ready. During that time, Tor tries to start a circuit to his configured bridges, times out the circuit, and marks his bridges down.

He can work around the problem in his experiments by starting Tor with "DisableNetwork 1" in the torrc, and when he's ready, remove the line and hup tor. That's not a good solution for real users though.

The problem would be less pronounced for him if Tor had better handling of when to mark a bridge down. There are a variety of tickets about that. But I think those issues are different from this ticket.

Perhaps the various proposals we've been writing recently have some opportunity to fit this in? Which ones are the best ones to look at?