Function stack_needs_named_subnets_at_setup 

pub fn stack_needs_named_subnets_at_setup(stack: &Stack) -> bool

Whether any sandbox in the stack forces setup to name subnets.

A restricted sandbox routes session egress through a VPC connector, and neither generator can enumerate the account default VPC’s subnets, so that mode leaves the connector without any and it fails at create. Callers that render an artifact want restricts_network_mode instead: this one answers for the declaration, which on a Kubernetes target is not what gets emitted.