shortcuts cause error when used with Neovide, but only if it is initialised from the command line

To reproduce:

1. Install Neovide via Homebrew (https://neovide.dev/)
2. Start app, run shortcuts, works
3. Run `brew services stop skhd` to stop background process
4. Run `skhd` in a new terminal window to view any errors encountered
5. Start Neovide GUI from terminal (`$ neovide .`)
6. Run skhd shortcuts from your config
7. You should see the following error: `could not locate the window to act on!`

From time to time, skhd shortcuts just don't work with certain apps, usually iTerm. This is one use-case that is reproducible.

EDIT: I don't think this is an issue with `yabai`, because if I run my `yabai` commands manually they work fine with the window in question. When I try to trigger the commands with `skhd` shortcuts they don't work.

EDIT: Strangely, after stopping the background process, running the process manually, and restarting the background process a couple of times it is now working with the aforementioned window. _However, if I close the window, and instantiate a new one via the `$ neovide .` command then the issue reoccurs_.

If I instantiate the Neovide app using `open -a Neovide` then I don't experience this issue, however, the `open` command just triggers the same process as is triggered by double clicking an app in Finder.

Versions:
`yabai`: yabai-v4.0.1
`skhd`: 0.3.5

Reproduce the failure by running skhd manually, launching Neovide with `$ neovide .`, and triggering the configured shortcuts; compare this with launching Neovide through `open -a Neovide`. Start from the reported `could not locate the window to act on!` error and verify that shortcuts work for newly created Neovide windows without regressing the working launch path.

Written by the indexing model from the issue text.