ci(track-a): inventory dedicated runner support layout

[blakinio]

Track A bounded physical infrastructure observation

Task: OTC-20260816-track-a-runner-support-layout-inventory
Base: exact main@67e5dc88ff4d6c241d90a046527dac4aa9f831d8.
Execution: one read-only synology-otclient-01 job using [otclient, synology].

RUNTIME #381 failed closed at toolroot_unavailable before WARP/X11/client. This task observes only fixed support-tool filesystem/package metadata needed to identify which prerequisite is absent/misplaced:

• the two trusted support-root candidates;
• fixed system paths for Xvfb, x11vnc, xdotool, XKB and libproxychains;
• dpkg installation/version metadata for xvfb/x11vnc/xdotool/proxychains4.

It does not inspect /proc, official-client files/processes, canonical registration/lease/session state, X11 display/window state, VNC listeners/endpoints, network/game/login state, credentials or Track B. No files are written outside the normal Actions checkout/task commit; no runtime mutation is authorized.

The workflow is one-shot and will be removed immediately after evidence capture. Its sanitized output will select a hosted-only repair or establish an external runner-image deployment blocker. No bootstrap retry follows without that disposition.

[blakinio]

COORDINATOR ACCEPT. The single physical job 31953830754 / 95181286228 was bounded to the declared support-path/package allowlist and did not inspect the official-client/canonical runtime surface. It proves the current split layout exactly: /work/_otclient_tibia_re_state/toolroot contains Xvfb/xdotool/XKB/libproxychains but lacks x11vnc; /usr/bin/x11vnc is present from installed package 0.9.16-10; the /home/runner/_work/.../toolroot candidate is absent. The one-shot workflow is removed. The initial deterministic-governance failure was metadata-only and is corrected; exact head 26741cb has Track A governance 31953980543 = SUCCESS and CI 31953980663 = SUCCESS, with 0 review threads/material findings. 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.