Enhancing Codenotch's utility by enabling direct navigation to active AI agent sessions within developer tools (Terminal, iTerm, Cursor, VS Code, Codex) interacting with AI agents (Claude Code, Codex, Antigravity).

## Problem

Codenotch can already tell me that an agent is waiting, name the live session, show where it is running, and say what it needs. The last step is still manual: I have to search through Terminal, iTerm, Cursor, VS Code, or Codex windows to find that session.

This is especially costly when several agents are running at once. The notch has already answered “which session needs me?” but cannot yet take me there.

`TASKS.md` already carries this as an unfinished M4b item: `Click a session to focus its terminal window`.

## Proposed behavior

- A live session row in the provider tooltip looks clickable when Codenotch can resolve where it came from.
- Clicking it activates the owning application and focuses the best matching window or tab.
- Waiting sessions remain first in the list, so the agent asking for input is the shortest click away.
- If an exact target cannot be resolved safely, the row stays informational rather than pretending the click will work.
- Clicking a session must not toggle the notch's pinned state or refresh provider usage.

An initial provider set could be Claude Code in Terminal/iTerm and sessions owned by Cursor, VS Code, or the Codex app. Other monitors can add focus support independently when they expose enough identity.

## Permission tradeoff

Bringing an application forward is straightforward, but choosing an exact terminal window or tab may require Apple Events or Accessibility permission depending on the host application. I would prefer th...