What
The bridge:projects feature, which mounts an MCP (Model Context Protocol) server for a cloud 'project thread' reply, now retries its connection attempt on failure using a backoff schedule (waiting longer between each successive retry) instead of giving up after a single failed attempt. It logs a message when retries are exhausted, and reports separate telemetry while a connection is still retrying versus when it has failed for good.
Why
A single transient failure no longer permanently breaks the connection; the mount now has a chance to recover on its own. When retries do run out, the mount stays as-is until the underlying binding changes, and the new logging makes that state easier to diagnose.