[cppla]

Summary

• Add a real loopback H3 reconnect contract test covering cold connection, another stream on that connection, and a replacement physical QUIC connection.
• Verify both peers' TLS state, certificate validation, disabled 0-RTT, and fresh connection-bound proxy authentication after reconnect.
• Cover native cached resumption, native nil-cache/tickets-disabled controls, and the default fixed Chrome profile with cache/tickets-disabled controls.
• Document that the fixed H3 Chrome profile does not support TLS session resumption, and distinguish this from connection reuse and the H2 resumption implementation.

Validation

• Go 1.26.8 make check passed.
• Targeted race test passed; race test repeated 30 times passed (150 cases).
• Native cached cold/reuse/reconnect DidResume was [false, false, true], with real cache store/load events. All full-handshake controls were [false, false, false].
• Every case retained TLS 1.3/h3, certificate verification, no 0-RTT, and two fresh proxy bootstraps across the two physical connections.
• git diff --check passed.

Evidence boundary

Only tests and documentation change. No production behavior, fingerprint profile, dependency, capture configuration or statistical gate changes. No remote capture or browser comparison was run for this PR. The current fresh-profile browser calibration does not test controlled warm reconnects, so this contract test does not establish a browser-similarity advantage or deficit.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-08T09:00:21.678801Z	b49e91c	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.