You have to manually configure the wired part of CAP client before CAPsMAN takes over provisioning the wireless part. CAPsMAN only does what you currently have under /interface wireless …
For testing purposes you can configure wireless part manually and transition it to CAPsMAN later. As to the wired part: did you study (thoroughly) the VLAN bible?
The wireless config shown in post #1 is almost fine (master wireless interfaces lack vlan-id=XX vlan-mode=use-tag and all wireless interfaces should be tagged member ports of bridge … tagged for corresponding VIDs that is).