feat(client): print runtime diagnostics snapshots

The client now builds ClientDiagnostics snapshots from the connected session,
known TAP state, route-pinning status, and tunnel counters. Windows prints one
snapshot after TAP and relay-route setup, then repeats snapshots while bridging
so frame/datagram counters and drops are visible during manual phase-1 tests.

Non-Windows builds print the same relay and QUIC diagnostics with TAP fields
marked unknown before waiting for Ctrl-C. TAP IP remains unknown until a later
Windows adapter IP inspection slice wires that source of truth.

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

Refs: PLAN.md

This commit is contained in:

ddidderr

2026-05-21 20:16:32 +02:00

parent e8d7cf7ff5

commit 2afdae44c6

4 changed files with 124 additions and 1 deletions

Cargo.lock

Generated

View File

@@ -474,6 +474,7 @@ dependencies = [
  "lanparty-client-route",
  "lanparty-client-tap",
  "lanparty-ctrl",
  "lanparty-obs",
  "lanparty-proto",
  "tokio",
 ]