feat(client): show gateway peer in startup status

The relay welcome now carries the gateway peer id, but the first Windows client
startup line still only showed whether a gateway was connected. Surface the peer
id there when it is known so manual MVP testers can record it even before or
without relying on a later lifecycle catch-up line.

Keep the older yes/no text when a gateway is connected but the peer id is not
available, which preserves useful output for older welcome payloads.

Test Plan:
- cargo fmt --check
- cargo test -p lanparty-client-win gateway_status
- cargo clippy -p lanparty-client-win --all-targets -- -D warnings
- git diff --check
- git diff --cached --check

Refs: MVP manual validation
This commit is contained in:
2026-05-22 07:26:55 +02:00
parent 8deb7d1d60
commit edcd30f6bc
2 changed files with 20 additions and 2 deletions
+1 -1
View File
@@ -171,7 +171,7 @@ Expected client output:
```text
prepared TAP adapter ... MAC ... configured and media disconnected before relay connect
lanparty-client-win connected as peer ...
lanparty-client-win connected as peer ...; LAN gateway connected yes (peer ...)
relay event: LAN gateway connected as peer ...
relay route pinned before TAP ...
relay route verified after TAP activation ...