Perhaps add to your corollaries "use sane interface names". I now prefer the convention br.<vlan-id> (e.g. br.199 for vlan interface with bridge as parent, and vlan-id=199) because it provides more information (it has an indication of the parent interface and the vlan-id all in a compact notation).
- Don't create vlan interface with bridge as parent for vlan-id=1 (Don't tag vlan 1)
- Don't change the bridge's pvid (unless you really know what you are doing).
Another warning for users. If you change the pvid of the bridge, don't create a vlan interface for that same vlan-id as was specified by the bridge pvid.
e.g. don't set bridge pvid=199 and also create vlan interface br.199; doing so will cause problems.
Example of problem in the thread Question related to “RouterOS bridge mysteries explained” in these posts (#14, #15, and #16 - has router examples)
Update: @lurker888 pointed out in #17, that as long as frame-types=admit-only-vlan-tagged is set on the bridge, then the pvid of the bridge makes no difference. But you won't be able to use the bridge interface then, only vlan interfaces under the bridge.
Update 2: I still think it is best to not have the bridge pvid and have a bridge vlan interface for the same vlan-id. See Question related to "RouterOS bridge mysteries explained" - #21 by Buckeye for why.