The workspace's private networks with member rosters

Your workspace's private networks: each with its name, id, address prefixes, and member roster (node name, that node's stable mesh addresses, its dns_name <node>.givemeanode.internal - resolvable from inside member containers - while placed its region/zone, and its data_plane, which is up, converging, not_placed, or unavailable as attach_network describes). Stopped members still appear - membership and addresses survive stop/wake; a stopped member just drops traffic until something wakes it (mesh traffic never does - a wake is always an explicit command).