Some more guidance

vlan interfaces are just a linux kernel way to allow for traffic through the "parent interface" (sometimes referred to as "master", "physical", "underlying" or "base" interface") to be tagged on egress, and selected and untagged on ingress. This allows the Linux networking stack to treat frames received from and sent to an interface in a standard way (without the tag). In your case, bridgeLocal is the "parent interface" and this interface does not add or remove frames itself.

When the "virtual switch" personality of the bridge is operating in vlan-aware mode (i.e. vlan-filtering=yes) it can be aware of vlans that do not have any associated vlan interface. The vlan interface is the what the "routing block" running on the CPU uses to connection to a specific vlan in the virtual switch. So in the CAP01 config export, even though the "virtual switch" is aware of the different vlans (20,30,99,60,150), there is a connection to the CPU block via vlan 99 (and the default vlan 1 via the bridge interface), so the CAP01 cAPGi can be connected to. And vlan 99 vlan-mgmt interface gets it ip address via dhcp on vlan 99.

I don't now how capsman connects, whether by untagged or tagged. I will leave that discussion to someone that knows.