CONNECT-IP server lacks overload limits and tenant isolation checks #991

The CONNECT-IP server from #954 has no binary or deployment yet. Before anything exposes it to the internet, it needs four fixes that did not block the review.

1. Any client can open unlimited sessions and admission calls, because no limit sits ahead of admission.
2. Unauthenticated clients get a probe packet before admission runs.
3. One full tunnel device tears down other tenants' sessions.
4. Routes are checked against each other but not against other tenants' ranges.

Lease fencing on the datapath is tracked in #976, and overload limits are a #970 criterion. Done when each item is fixed or the wrapper that exposes the server handles it. The detail is in the first comment.

Related to #954, #970, #976

Galactic Edge integration (#992)

Implement this milestone as a consumer of the Galactic Edge provider contract. #992 owns provider authorization, host attachment lifecycle, shared-state fencing and maintenance, independently enforced forwarding expiry, prefix conflict arbitration/publication, and gVPC traffic policy. MASQUE owns client authentication, connector /96 assignment and retention, session packet checks, transport behavior and its provider adapter. Use the foundation's versioned contract and existing provider helpers; do not introduce a second host-networking controller, lease store or BGP publisher. Any required foundation change must be tracked and qualified under #992 before this milestone claims integrated acceptance.

Integration disposition and acceptance

This issue is an exposure gate for #980/#981, with #984 supplying subsequent load qualification. #992 provides foundation gates and route arbitration; it does not automatically fix CONNECT-IP admission or queue behavior.

• Implement the HTTP/3 CONNECT-IP edge service #980/Implement HTTP/2 CONNECT-IP fallback over TLS #981/Enforce resource limits and qualify connector capacity #984 bound unauthenticated connections, streams, in-flight admission, sessions and queued bytes before allocating work; authentication precedes MTU probes on both transports.
• Integrate MASQUE with Galactic Edge provider attachments #975/Enforce delegated-prefix ownership and bidirectional traffic policy #979 isolate backend state by tenant attachment and session; TUN backpressure cannot terminate unrelated sessions or serialize unbounded work behind a shared lock.
• Implement admission, credential expiry and access revocation #977/Implement /96 connector addressing and aggregate return routing #978 validate client route authority against trusted grants and use Implement authorized prefix routing #998 for foundation prefix conflicts. Enforce delegated-prefix ownership and bidirectional traffic policy #979 verifies library packet checks and explicitly handles unsupported IPv4.
• Integrate connector ownership with Edge claims and independent expiry #976 integrates independent foundation gates and session authority before the raw TUN backend is reachable. Session cancellation alone is insufficient fencing.
• Address all six findings in the first comment with linked fixes/tests or evidence-backed current-path dispositions; rerun them for HTTP/2 as well as HTTP/3 and retain negative packet evidence in Add reproducible end-to-end feature acceptance tests #985.