#742 swamp issue bug times out posting to the Lab while swamp-club.com returns HTTP 200

Summary

swamp issue bug --title ... --body ... --json repeatedly fails with:

{
  "error": "Request to https://swamp-club.com timed out. Is the server running?"
}

…even though https://swamp-club.com is reachable and fast, and the session is authenticated. The Lab issue-submission API endpoint appears to time out / hang independently of the marketing site, and the CLI surfaces a generic, misleading "Is the server running?" error.

Environment

• swamp 20260621.225920.0-sha.b2d542b2 (confirmed up to date)
• macOS (darwin 23.6.0)
• Authenticated: yes (swamp auth status shows a logged-in user on https://swamp-club.com)

Steps to reproduce

1. swamp auth status → logged in.
2. swamp issue bug --title "<title>" --body "<long markdown body>" --json
3. Observe the timeout error. Reproduced on two consecutive attempts within the same minute.

Actual

CLI output:

{ "error": "Request to https://swamp-club.com timed out. Is the server running?" }

Meanwhile the host is clearly up:

$ curl -sS -o /dev/null -w "HTTP %{http_code} connect=%{time_connect}s total=%{time_total}s\n" https://swamp-club.com
HTTP 200  connect=0.150638s  total=0.717780s

In the same session, registry-backed operations were also unusually slow (an extension·auto-resolve registry search took ~15s before returning), suggesting backend slowness on the swamp.club API tier rather than a client/network problem.

Expected

When the API endpoint (not the host) is the unresponsive component, the CLI should:

1. Surface a more precise, actionable error — distinguish "Lab API endpoint timed out" from "host unreachable," and avoid "Is the server running?" when the server demonstrably is.
2. Include the actual endpoint/URL it attempted and the configured timeout value.
3. Use a longer and/or configurable submission timeout, ideally with a bounded retry/backoff.
4. Offer or auto-suggest the --email fallback on timeout so a drafted report isn't lost.

Impact

A user with a complete, ready-to-file report cannot submit it, and the error message points them at the wrong thing ("Is the server running?" — it is).