Upgrades break WSL integration

I sign git commits with 1Password in WSL2 as document, but every time 1Password pushes out an update (in Windows), this happens:

$ git commit -am'useful title'
error: 1Password: Access is denied. (os error 5)

fatal: failed to write commit object

And every single time I have to do this dance where I try to open 1Password from Windows's system tray, it disappears on me (main window may flash briefly), then I wait a couple minutes for the upgrade to happen and manually restart 1Password so I can log in and rerun my `git commit` command back in WSL.

This is a terrible upgrade experience. How did the pipe get closed if you haven't actually installed the upgrade? If you did install the upgrade, why did 1Password on Windows show briefly then close itself? And if the upgrade was being applied at that time, why did I have to restart it manually to get it to re-establish the pipe with WSL?

If 1Password is interested in an improvement, I'm happy to help here. I was the architect for the new(ish) Visual Studio setup, worked on WiX along with .NET and VS setups for over a decade and still freelance for a lot of teams' setups. Ideally upgrades are transparent. At the very least, po up a message that an upgrade is ready (as is more common with apps) but keep everything working and not just breaking seemingly random workflows. It's very disruptive.