ci(track-a): discriminate client window ownership in isolated runtime

[blakinio]

Track A RUNTIME — bounded ephemeral-isolated discriminator

Task: OTC-20260816-track-a-client-window-ownership-discriminator
Base: exact trusted main@05d4a7136e234b874f7f112ad8c92f01b0aabd51.
Execution: one task-owned ephemeral_isolated startup diagnostic on synology-otclient-01; no canonical lease/registration mutation.

Canonical v6 #397 proved WARP/Xvfb/VNC/client start succeeded and the exact launched client PID remained alive for the correct 30-second wait, but no visible ^Tibia$ window owned by that PID was found. This diagnostic will reproduce the same startup environment in a unique high-display sandbox, then collect only bounded non-secret evidence needed to distinguish: no visible window, different title, child-process window ownership, or pre-window startup blocking.

No account credentials/login/gameplay, canonical registration/lease/session, Track B, BattlEye internals/bypass, owner-funded Codex/OpenAI API/paid quota or broad process cleanup is authorized. Every diagnostic process/display/network helper is task-owned and removed before exit.

[blakinio]

OTCLIENT-TIBIA-RE-COORD disposition: ACCEPT. Final semantic discriminator run 31958546334/job 95192878995 passed in a uniquely admitted ephemeral-isolated namespace with no canonical-state access. Exact client remained alive through 35s while visible X11 window count was 0 at t+5/t+15/t+35; no marker-owned descendant was observed; sanitized startup log directly reports XCB/QRhiGles2 failure to create OpenGL/offscreen contexts because neither GLX nor EGL is enabled, while asset loading and HTTPS startup activity proceeded. Cleanup completed, no credentials/login/gameplay/canonical registration were used, and all one-shot workflows are absent from final diff. Exact head ef97a36 has both Track A governance jobs SUCCESS, CI / Required SUCCESS and zero review threads. Promote as terminal discriminator evidence; next work is hosted-only graphics-stack compatibility research/fix, not another physical retry.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.