fix(gool): reconnect without stopping to ask a question

[amir-reza-bijandi]

Reported by @TheLordOfTheKings on #91: with gool, a tunnel that drops after a long session never comes back.

What happens

The reconnect loop runs, and then stops at a prompt:

[-] gool tunnel ended: other: [inner] other: wireguard tunnel stale: no valid data from peer; reconnecting
[-] outer endpoint 162.159.192.1:2408 failed 2 times in a row; blacklisting and rescanning

Scan mode:
  [1] turbo     (fast, first hit)
...
Choose [1-5] (default 2):

run_gool asks for the scan mode and the IP version from inside its reconnect loop, so every rescan waits on stdin. A drop hours into a session has nobody there to answer, and the tunnel stays down. One drop retries the same endpoint quietly; two consecutive drops blacklist it, go to rescan, and hang there.

Not a regression from #91

This is older than that fix. The loop has prompted on rescan since a26159b (v1.6.0), where it called select_peer, which asks both questions; 38bc38f replaced that call with the two prompts directly, still inside the loop. #91 only changed the teardown in run_warp_in_warp.

What #91 changed is which failure you meet first: before it, the first stale tunnel panicked and took the process with it, so the rescan was never reached. The log above is that fix working — two full loop passes where the old code would have crashed on the first — and it uncovered the prompt behind it.

The fix

Ask once before the loop, the way run_masque and run_wireguard already do. The first pass through the loop always scans, so the question is asked at the same point it was before; later passes reuse the answer instead of asking again.

Setting --scan and -4/-6/--dual (or AETHER_SCAN / AETHER_IP) already avoided this, since those suppress the prompts — that's the workaround for anyone on 1.8.0.

Testing

cargo test passes (234 tests) and the build is clean. I haven't reproduced a live tunnel drop, so the reconnect path itself is code review rather than a demonstration.

A note on this PR

Full disclosure: as with #91 I put this together with Claude Code, and I don't know Rust myself, so please review it as such.