Here’s what I ran into:
1. The ADB proxy in WSL through the Windows host doesn’t work, and web-ext doesn’t support ADB proxy at all.
2. web-ext can’t recognize WSL’s odd folder naming in file paths.
3. Third thing, maybe the most frustrating issue is that most of the documentation for setting up the development flow on Windows is outdated. The screenshots are misleading, the text is conflicting with each other, which made AI chatbots pretty useless in this case.
But long story short, I finally got it working by forking the final build of the add-on to a Windows path and running web-ext directly on Windows to connect to my Android device via ADB. The workflow is still a bit broken, though.