docs(integration): correct channel claim and flag UDP port collision (#21)

SpaceGame's v1.0.0 evaluation (SpaceGame docs/rendezvous-eval.md @ 8eb5607) found the pilot doc asserting ChannelsCount=3 as current SpaceGame fact — their source uses LiteNetLib's single-channel default, and a peer mismatch fails connections silently, so the doc now states the requirement as agreement rather than a count. The compose file also gains a loud warning that host UDP 9050 collides with common game-client defaults during same-machine evaluation.
2026-08-22 23:21:10 +02:00
parent e3b687c903
commit 13382531ce
2 changed files with 9 additions and 2 deletions
@@ -31,8 +31,11 @@ must be repeated from the public feed.

 ## Proven local path

-The SpaceGame host and client each create one caller-owned `NetManager`, set its
-three gameplay QoS channels before `Start`, and give the same manager and
+The SpaceGame host and client each create one caller-owned `NetManager`,
+configure any additional gameplay QoS channels before `Start` (the pilot
+harness used three; current SpaceGame source uses LiteNetLib's default single
+channel — both peers must simply agree, because a `ChannelsCount` mismatch
+fails the connection silently), and give the same manager and
 `RendezvousNetListener` to the coordinator. Rendezvous authenticates discovery,
 join authorization, host presence, mediation, and connection outcome reporting.
 After traversal, SpaceGame performs a separate audience-bound admission exchange