ci(track-a): run canonical runtime v6 after bounded-wait repair

[blakinio]

Track A RUNTIME v6 — one fresh canonical bootstrap/Gate-B attempt

Task: existing OTC-20260816-track-a-canonical-runtime-e2e.
Base: exact trusted main@9e3634c1d822ffc6e74d8e42da63a4e8c60ea3e1 after bounded-window fix #395 and archive #396.
Execution: serialized physical synology-otclient-01 only.

All previously observed deterministic blockers are now terminal on trusted main: canonical transition, toolroot layout, contained x11vnc, absolute /usr/bin/xkbcomp with isolated Xvfb socket proof, and the nested client-window wait that caused v5 worker_timeout.

This phase permits exactly one no-credential bootstrap/Gate-B attempt. It re-fences the exact trusted base, support root and xkbcomp, reads current canonical registration/lease state, refuses duplicate creation, acquires current lease authority, invokes trusted-main bootstrap, requires immediate same-generation Gate B, persists only sanitized authoritative registration evidence, releases controller authority and leaves the canonical X11/VNC/client runtime idle on success.

Any new fail-closed discriminator terminates this phase. No blind retry, account credentials, login, gameplay, Track B mutation, historical #303 surface reuse or owner-funded Codex/OpenAI API/paid quota is authorized.

[blakinio]

OTCLIENT-TIBIA-RE-COORD disposition: RETURN_FOR_EVIDENCE / ACCEPT_BLOCKED_CHECKPOINT. Exact physical run 31957502867/job 95190252936 passed fresh admission governance, trusted worker wait contract, support root, exact xkbcomp, WARP, Xvfb and VNC; it reached the exact client start and kept the launched PID alive through the correct bounded ~30s wait, then failed closed at client_window_missing. No registration was published, Gate B was not reached, no credentials/login were used, and the one-shot workflow is removed. Final head 9370835 has governance SUCCESS, CI / Required SUCCESS and zero review threads. Promote this checkpoint as the canonical blocker state; next evidence must be a separately admitted ephemeral-isolated window/process/startup diagnostic, not another bootstrap 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.