Issue with using op.exe within WSL for Ansible

Despite using 1Password, 1Password CLI and Ansible successfully in WSL on Windows 11, I've recently run into an issue.

The 1Password apps on my work device were not being updated, and I believe I was using version 8.8.8 of the main app and 2.17.0 of the CLI. (Not great, I know).

I had created a symbolic link for "/mnt/c/Program\ Files\ \)x86\)/1Password\ CLI/op.exe" to /usr/local/bin/op and everything was running fine. I could run 'op signin' and it would trigger my biometric authentication and 'op account list' would return my account as expected.

I could also, use the community.general.onepassword lookup within Ansible just fine. 
I had a script to retrieve my ansible vault password configured in my ansible.cfg and this worked fine:

#!/bin/bash

op read "op://Personal/ansible_vault/password"

After much cajoling, the support team have updated the 1Password applications on my device, I'm now running 8.11.2 of the Desktop app and 2.31.1 of OP CLI. 

Most of my environment works as before, 'op account list' triggers my biometrics and then returns the expected values and my ansible vault script above continues to work in the same way... however now the community.general.onepassword plugin is complaining that I'm not passing the required parameters (secret key, username, master_password, subdomain) ... but I shouldn't need to do this, as I am signed into 1Password. Again, this worked fine before upgrading the Windows OP CLI and App.

Is this expected? I guess I could add these security items into my Ansible vault but I thought the whole point of OP CLI was to be able to move away from static security info in files (even if it is encrypted) and using password managers?