app-screenshot-debug

# Screenshot-driven UI debugging (AppleScript + screencapture) The loop for *seeing* a termio UI change instead of guessing from code: ``` (rebuild if code changed) → drive app into the target state → capture the window → Read the PNG → judge / iterate ``` You cannot evaluate spacing, alignment, overlap, ghosting, or "this looks ugly" from source. Get a real screenshot, Read it, then decide. ## Prerequisites - The app must be **running** and built. If you just changed code, run the `macos-rebuild-dev` skill first. The process name for System Events is `termio` and the main window's title is `termio`. - These calls need macOS **Accessibility** + **Screen Recording** permission for the terminal / Claude Code host. If `System Events` errors with `-25211` or the capture is black, that permission is missing — tell the user to grant it in System Settings → Privacy & Security. - termio is a single-window app (sidebar + terminal panes); there is **no Settings window**. Everything you need is in `window 1`. ## The two helper scripts (in `scripts/`) Run them with bash; they take the app name from `$TERMIO_APP_NAME` (default `termio`). 1. **`capture-window.sh [out.png]`** — screenshot *just* the frontmost termio window (`-o` no shadow, `-x` silent), reading its live bounds first. Prints the window origin + size. Captures the region 1:1 in points, so **a point you read off the resulting image is window-relative**: image (dx,dy) == screen (originX+d...