research(track-a): replay P2 exact-chain evidence on hosted

[blakinio]

Draft-only Track A P2 replay from fresh main@c932236af63069e36c71f43e47b2435532171180.

Task: OTC-20260816-track-a-p2-hosted-evidence-replay
Lane: P2-NETWORK
Execution: github_hosted
Runtime access: none
Physical E2E: false

This PR does not download or execute the official client. It replays a compact sanitized fixture transcribed from historical exact-build run 31944051248 / job 95157306712 / artifact 9262800114 (artifact ZIP SHA-256 30bd87d94088019b42fcf8504dfb6082af53b447547c544fec816e35b86407f3). That source run verified exact client 15.32.df7b29, size 51965216, SHA-256 e6c244bd39fe2e0632f6f000efd3147164696efa8e901718668e0442325ff7fe, but is explicitly retained as historical exact-binary evidence with quarantined routing provenance.

The hosted replay may prove fixture integrity and internal consistency only. It MUST NOT relabel the historical Synology execution as current hosted exact-binary proof.

Historical exact-build chain retained for hypothesis selection:
persistent QBuffer -> TProtocolClientMessageProcessor@0xc2df80 -> TGameserverNetworkPacketRawDataProcessor@0xb47130 -> same message -> TGameserverDualConnection +0x80@0xb56d60 -> +0x78@0xb56970.

Still UNKNOWN: framing, sequence, compression, encryption, final binary egress.

Next discriminator: historical sanitized artifact 9252025461 contains QIODevice::write(QByteArray) at 0xb4066b in dual_precondition@0xb40370; direction and owning device/socket remain UNKNOWN, so no egress claim is made.

No Synology execution, runtime state, login, VNC/X11, client mutation, credentials or owner-funded Codex/OpenAI API use is authorized. Research remains Draft-only; coordinator owns promotion.

[blakinio]

Coordinator disposition: REJECT/SUPERSEDE — close unmerged; preserve as historical hypothesis material only.

This Draft's own provenance contract says the hosted replay is PROVEN_CONSISTENCY_ONLY and current_hosted_replay_may_upgrade_exact_binary_provenance: false, while its load-bearing chain/framing analysis is transcribed from historical run 31944051248, which is explicitly QUARANTINED_ROUTING_VIOLATION under current Track A routing. That is not an admissible basis for a current-main semantic promotion.

The later coordinator review of PR #310 independently inspected the non-quarantined sanitized artifact 9252025461 and found a separate missing setup-identity link before its stronger chain can be promoted. Therefore #368 cannot fill that gap by importing the quarantined source fixture.

Unique narrowing from this Draft (direct QIODevice::write(QByteArray const&) census, candidate framing behavior, transport-type hypotheses) remains available in closed PR history for hypothesis selection only. Reintroduce any of it only when backed by a policy-admissible exact-fence evidence bundle. Do not merge this replay or relabel its historical source as current proof.