Environment for every capture: Linux x86_64; independently installed pinned worktrees;
T3 Code development servers started with T3CODE_DEV_SEED=0 vp run dev.
Each server created its own fresh database. The fixture is an empty synthetic project.
Installed CLIs: Grok 1.0.77, Pi 1.5.2, OpenCode 1.19.5.

Web stills: Chromium, dark appearance, 1280x1000 CSS viewport, devicePixelRatio=2.
Original PNGs are 2560x2000. Identical crops on both sides:
Grok: CSS x608 y210 width576 height340 => 1152x680 physical pixels.
Pi: CSS x608 y210 width576 height410 => 1152x820 physical pixels.
Each retained crop had zero differing pixels between screenshots at least 500ms apart.
The crops omit the environment name and model catalog to protect operational metadata.

Terminal recordings: real GNOME Terminal under headless-desktop/Xvfb; 1280x800 pixels,
15 fps, light terminal theme, identical geometry and run-case.sh on both sides.
These record real authenticated server RPC and T3 CLI commands, not tests or replay.
Web status stills supplement the live server/CLI recordings.

Procedure: install executable wrappers exposed at ~/bin/grok and ~/bin/pi, delegating
to the installed authenticated CLIs. For Grok, then Pi, configure the home-relative
wrapper, refresh detection, and start a thread asking for PATH_OK. Repeat each using
the same wrapper's absolute path. Both commits use the same wrapper files and prompt.
The driver prints filtered live RPC results, CLI outcome, matching server cause, and
wrapper invocations during the turn. Server error excerpts preserve original messages.
A later UI pass restores both home paths and inspects Settings > Providers.

Observed:
Base: home-relative Grok and Pi are not found; neither wrapper is invoked for its turn.
Head: both detect as authenticated; Pi completes with PATH_OK; Grok launches and answers
ACP initialize but then fails because its CLI does not advertise xai.api_key authentication.
Absolute control: Pi completes on both; Grok reaches that same authentication mismatch
on both. Grok path expansion and process launch are verified; successful authenticated
Grok session creation and turn completion are not verified.
OpenCode already expands home-relative paths on base and has no source changes in this diff.

Reproduction scripts: run driver.mjs with checkout plus seed once per fresh server.
Then run capture-terminal.sh CHECKOUT base or CHECKOUT head under headless-desktop.
PROOF_SIDE selects the corresponding private server log for cause extraction.
Keep driver, run-case.sh, capture-terminal.sh, and base-server.log/head-server.log in
one scratch directory. Wrappers are generated in scratch/bin; expose them under the
server account's ~/bin before running. No credentials are printed or embedded.

AI-assisted; verified with the tests and tools listed above.