kyzn(deep): improve auto — health 98 → 98

[bokiko]

kyzn Improvement Report

Health Score: 98 → 98 (→ 0)
Mode: deep | Focus: auto
Cost: $0.6552492000000001
Run ID: 20260318-011058-20096b55

Changes

 desktop/src/api_client.py  |  3 +++
 desktop/src/cli.py         |  2 ++
 desktop/src/ping_tester.py | 17 ++++++++++++++++-
 3 files changed, 21 insertions(+), 1 deletion(-)

Verification

• Build: ✅ Passed
• Tests: ✅ Passed

---

To approve: kyzn approve 20260318-011058-20096b55
To reject: kyzn reject 20260318-011058-20096b55 --reason "..."

Generated by kyzn — autonomous code improvement

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 19eb2db615

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Don't misreport malformed server entries as timeouts

When test_server() raises on bad server metadata (for example, the API/defaults omit ip or location), this fallback turns that exception into packet_loss=100.0. Both the CLI and GUI render any packet_loss >= 100 as a normal timeout/unreachable server (desktop/src/cli.py:134 and desktop/src/gui.py:797-800), so a backend/config regression gets presented as network data and can change which region is recommended. Please preserve a distinct error state instead of classifying these exceptions as packet loss.

Useful? React with 👍 / 👎.