Handle macOS TCC Accessibility permission grants and failures when driving other apps' UI via the AXUIElement API

Steps

1. Check trust status at runtime with AXIsProcessTrusted() before attempting any AXUIElement calls, since untrusted calls fail or return errors without prompting on their own
2. Use AXIsProcessTrustedWithOptions with the trusted-check prompt option to trigger the system consent dialog on first run, directing the user to System Settings > Privacy & Security > Accessibility
3. Know there is no supported programmatic way to add an app to the Accessibility list — only the user can grant it manually, so setup instructions should point users to that pane explicitly
4. Re-grant Accessibility access after every rebuild of an unsigned or ad-hoc-signed development binary, since macOS ties the grant to the binary's code signature and path
5. For CLI tools invoked from Terminal, grant Terminal (or iTerm) itself Accessibility access, since the permission attaches to the actual parent process making the AX calls