ci(track-a): isolate Xvfb startup failure on dedicated runner

[blakinio]

Track A bounded Xvfb-only discriminator

Task: OTC-20260816-track-a-isolated-xvfb-startup-discriminator
Base: exact main@917b8ab943fd9aa1fded50c9a0b8b4e1dfeb5cbb.
Execution: one ephemeral-isolated synology-otclient-01 support-process test.

Canonical bootstrap #386 passed the completed contained-toolroot preflight, acquired lease generation 3 and generated its canonical-owned WARP profile, but then failed closed at TRACK_A_CANONICAL_SESSION_ERROR=xvfb_socket_missing before client launch, VNC registration or Gate B. The one-shot bootstrap workflow was removed; no retry is authorized.

This task reproduces only the trusted worker's Xvfb invocation on a high task-owned free display, with the same contained Xvfb binary, library paths, XKB root and arguments. It records:

• Xvfb realpath and missing dynamic-library count;
• whether the process exits or its X11 socket appears;
• bounded Xvfb stderr/exit status.

It never launches x11vnc, xdotool actions, WARP, official client, canonical lease/registration, game network/login or credentials. Cleanup kills only the task-owned Xvfb process and removes only its own stale display lock/socket after ownership checks. No owner-funded Codex/OpenAI API/paid quota is used.

[blakinio]

COORDINATOR ACCEPT. The one Xvfb-only experiment was correctly ephemeral/isolated, created no canonical/client/VNC/network/login state and cleaned itself. Exact run 31954834760 / job 95183766554 proves the contained Xvfb binary has zero unresolved shared libraries but exits rc=1 before socket creation because it invokes missing absolute /usr/bin/xkbcomp; captured stderr and upstream Xorg XkbBinDirectory semantics support that discriminator. The one-shot workflow is removed. Exact final head 31da485 has Track A governance 31955007090 = SUCCESS and repository CI 31955007280 = SUCCESS; review threads/material findings = 0. Accepted for promotion as sanitized infrastructure evidence.

[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.