Minting needs a signed-in browser on the same machine, so remote and unattended runs can't mint

[asabirov]

Original request

Moved from the archived private working copy of this skill (issue #3 there), with names of internal hosts, machines and local paths removed.

Problem

Minting needs a browser signed in to GitHub on the same machine that runs mint.sh: the orca driver needs an Orca session, and the chrome driver needs a signed-in Chrome profile. A worker on a remote host with no display or browser can't mint, and signing in needs a person, so unattended runs (orchestrated lanes, cron jobs, remote hosts) stop with exit 4.

A smaller fault found at the same time: scripts/drivers/chrome.mjs hardcodes its debugging port and profile path with no override. Two sessions running at once collide on the port, and the second exits 3.

Acceptance criteria

• A worker on a remote host with no display and no browser can turn a local PNG into a user-attachments URL, with nobody present when it runs.

Open questions

• How to meet this is open. The original report suggested keeping the signed-in session separate from the driver that uploads; that is a suggestion, not a decision. "Run login.sh once" does not count as meeting it.