# Real-app proof driver

Both checkouts used fresh T3 homes, no production seed, the same synthetic repository with one staged README change, and Grok 1.0.77 (50ca579fa996), signed out through the seed script's isolated HOME and GROK_HOME. The wrapper executes the real CLI and supplies no ACP replies.

For each side, after the dev server listens:

1. `node apps/server/src/bin.ts project add <scratch>/commit-demo --title 'Commit demo' --base-dir <scratch>/<side>`
2. `node apps/server/src/bin.ts thread start <scratch>/commit-demo 'Show the staged documentation update.' --title 'Commit demo' --provider devReplay --model multi-turn --wait --json --base-dir <scratch>/<side>`
3. In T3's preview browser, open the startup pairing link and wait for authentication. Open the returned thread at `/<environmentId>/<encoded-threadId>`.
4. Set the browser viewport to 1280x800 CSS pixels and dark appearance. Screenshots have device scale factor 2.
5. Hide only the private host label before recording, through the same CSS on both sides: `[aria-label^="Run context:"] { visibility: hidden !important; }`. No error text is modified.
6. Start recording. Click the button with accessible name exactly `Commit` in the `Git actions` group. Wait for the error toast. Capture a still; take a second screenshot more than 500 ms later and confirm ImageMagick's absolute pixel difference is 0. Stop recording.

The replay provider only supplies a free conversation fixture. Commit-message generation uses the real signed-out Grok binary selected in settings.

Observed base: `Text generation failed in generateCommitMessage: Grok ACP request failed.`
Observed head: `Text generation failed in generateCommitMessage: Grok authentication is required.`

An independent real-CLI ACP probe returned `{"code":-32000,"message":"Authentication required","data":"no auth method id provided"}` from `session/new`.
