Unable to run skhd directly after Sequoia upgrade

After upgrading to macOS Sequoia, I was prompted to re-grant `skhd` access to accessibility features. It was already enabled, and flipping the toggle off and on did nothing. To rid the prompt appearing when running `skhd --start-service` or `skhd --restart-service`, I had to:

1. Remove the `skhd` entry from the list of applications which have been granted accessibility access.
2. Run `skhd --restart-service`.
3. Grant access to the new entry through following the prompt once more.

However, I still cannot just run `skhd` directly in my terminal. I am constantly met with a prompt to grant accessibility access to either`skhd`, or `alacritty`. Both of these have been granted permissions, and all has worked fine until the upgrade.

All of this is to debug and test some broken features with Sequoia, specifically to interact with `yabai`, and more specifically, [this](https://developer.apple.com/forums/thread/763878?answerId=804374022#804374022), which seems to have broken every single keybind I have configured in `skhd`.

For clarity, even with `skhd` running as a service, none of my keybinds are working. Assumed due to the link above.

Start by reproducing the issue with `skhd --start-service`, `skhd --restart-service`, and direct `skhd` after checking the macOS accessibility permissions described in the report. Compare behavior with `yabai` and the linked Sequoia accessibility change; done means skhd starts directly and configured keybinds work without repeated permission prompts.

Written by the indexing model from the issue text.