In the export of the configuration of the client (the 941), I can see
set [ find default-name=wlan1 ] ssid=MikroTik
which means that the mode is set to station (default settings are not shown in export). But in mode=station, the header of the frames in the air only contains the source MAC address of the wireless interface, so bridging does not work (which may not matter much in this case unless you want to connect some wired clients to the same VLAN using ether1), but VLAN tagging most likely doesn't work either. So you need to change the mode of client's wlan1 to station-bridge.
Once you fix this, the next issue is this:
interface bridge port
add bridge=wan-Link frame-types=admit-only-untagged-and-priority-tagged ingress-filtering=yes interface=wlan1 pvid=1000
At the AP side (the 911), both VLAN 300 and VLAN 1000 are sent/expected over the air as tagged, hence you cannot set any of these as the bridge port's pvid at the client side.
So the other fix must be that you set the pvid in the row above to 1, so that frames with VID 1000 would be expected and sent tagged over the wlan1 port of bridge wan-Link, and that you change frame-types to admit-only-vlan-tagged.
Last, the action=masquerade rule refers to an out-interface which doesn't exist any more, so just remove the out-interface parameter from it, as you have the out-interface-list=WAN there; however, you have to make v1000 a member of interface list WAN instead of wan1.
Plus, if you really want ether1 to be an access port to VLAN 1000 on bridge wan-Link as the /interface bridge vlan row with vlan-ids=1000 suggests, you must add a row interface=ether1 bridge=wan-Link pvid=1000 to /interface bridge port. But the fact that you host just a /30 subnet in that VLAN suggests that the ether1 should rather be removed from that row in /interface bridge vlan.
So fix these first and let us know the outcome. If it is not enough, we may dig further.
I could imagine that adding wlan1 as an access port of VLAN 1000 on bridge1 at the AP side might make it possible to use mode=station at wlan1 at the client side, but I've never tested that, and even if it worked, you would lose the possibility to use VLAN 300 to manage the client's 941 device, and you would have to modify the rest of the configuration accordingly (attach the IP configuration to wan-Link rather than to v1000, or maybe remove the bridge wan-Link completely and attach the IP configuration directly to wan1.
Instead of writing novels, post /export hide-sensitive. Use find&replace in your favourite text editor to systematically replace all occurrences of each public IP address potentially identifying you by a distinctive pattern such as my.public.ip.1.