Hiding it from the whole x86 web helper got it past tier0 (message loop,
BrowserCreated) but then Chromium trapped on the status descriptor it
opened itself, now a memfd copy - which is the other reason the shim
leaves the web helper alone. With BL_WEBHELPER_HIDE_TRACER=1 only opens
called from libtier0_s.so get the copy; Chromium's get procfs.
Traced per process through FEXServer: every x86 web helper read
/proc/self/status (the string sits in libtier0_s.so) and died of SIGTRAP
right after. proot is a tracer, so tier0 believes a debugger is attached
and breaks into it with int3 on the first failed assertion. The arm64
build only issues a stray svc there, which is why the session shim leaves
the arm64 web helper reading the real TracerPid. BL_WEBHELPER_HIDE_TRACER=1,
set by bannerlator-steam-x64, serves the x86 one TracerPid 0 as well.
Lifts Bannerlator's Linux/gamescope runtime out into an app of its own: the
Wayland compositor, the proot session, the runtime installer, the fake-evdev
controller path and the PulseAudio server, with none of the Wine, container or
store machinery around them.
One activity installs the runtime from the same winlator-contents catalog and a
second one runs the session: compositor on a SurfaceView, gamescope and Valve's
native arm64 client under proot, a physical pad republished into the fake-input
rings, and the session's milestones on screen until the first frame arrives.