Windows test rig: launch and screenshot AbyssTracker on the PC with a live EVE character #51

Why

Nobody has run AbyssTracker in its real setting yet. On the MacBook Tkinter crashes, Arcanum has no display, and the ESI features only return real data while a character is logged in. The Windows PC runs the EVE client, so it's the only machine where all of that can be checked against reality.

Goal

An agent on the Windows PC can launch AbyssTracker, use it, and screenshot it, with a live EVE character logged in, and check that the ESI readings come back right.

How the agent gets to the desktop (settled in the grill)

The Claude desktop app with computer use runs on the PC and works on the real desktop. SSH from Arcanum is only for headless jobs (pulling the repo, running tests). It is not part of the rig, partly because a key-authenticated OpenSSH session can't read the ESI token from Windows Credential Manager.

Hard rules (not up for negotiation)

• Computer use may control: AbyssTracker, a terminal, and a browser. The browser may only open login.eveonline.com, the app's 127.0.0.1:8765/callback, and Gmail (see below).
• The agent never sends input to the EVE launcher or client: no clicks, no keystrokes, no window automation. CCP's EULA bans automating client input. If EVE has focus, the agent stops instead of clicking.
• The agent never types the EVE account password, and never handles authenticator-app codes. If the sign-in asks for either, it stops and hands over to the user.
• The agent may approve the ESI SSO sign-in itself: pick the character and click Authorize.
• Emailed verification codes: the agent may open Gmail and read only the newest CCP/EVE email with the code. It reads nothing else and archives, deletes or marks nothing. The moment it opens Gmail it sends the user a push notification, and its final report starts with a bold line saying it opened Gmail, when, and why.
• No undocking, no filaments, no Abyssal activation, ever. The character stays docked for the whole test.
• The rig never opens the real tracker.db. Every run sets ABYSS_TRACKER_DB to a throwaway file.
• Live screenshots stay on the PC, outside the repo. The repo is public, and they show the character name, wallet and location. The PR lists pass/fail for each check. Any image put in the PR has the name, portrait, wallet and location blurred first.

User's manual setup before a run

Log in through the launcher, dock the character, and put EVE in windowed or fixed-window mode, so the pocket window can sit on top of it.

Acceptance criteria

• The app starts on Windows from a fresh clone with a venv and requirements.txt. The release .exe is out of scope.
• The ESI token is obtained once through the SSO sign-in, then refreshes without further help.
• While docked, the location and run detection behave correctly (no false entry into the Abyss), and the wallet stat matches the client.
• Every page (Abyss, Incursion, History, pocket mode) is opened and screenshotted. The screenshots are kept locally and their pass/fail is listed in the PR.
• The pocket window stays on top beside the windowed EVE client.
• .claude/skills/run-windows/SKILL.md tells a future session exactly how to launch, check and screenshot the app on the PC, with the hard rules above at the top. .claude/worktrees/ is gitignored.

Out of scope

The live active-ship and cargo check moves to its own sub-ticket, blocked by #47 (Fetch from EVE for cargo).