lifecycle hook for when all targets are connected

Not 100% sure if this would be useful to other folks, or if a better pattern is available –but it would be super useful to have a callback for when all targets are connected.

That way one could begin to act on their targets without having to worry about whether their state is ready.

No file, test, or entry point is named. Start by tracing how Catalyst tracks target connection and state readiness, then determine whether a lifecycle callback fits that flow; done would mean consumers can reliably act after all targets are connected.

Escrito por el modelo de indexación a partir del texto del issue.