# Real-app reproduction

Run each commit in its own installed worktree with T3CODE_DEV_SEED=0 vp run dev. Use the same synthetic fixture generated by seed-picker.py, add it with `node apps/server/src/bin.ts project add <fixture> --base-dir .t3`, and start a thread with provider claudeAgent, model claude-haiku-5-5, title Color picker steer proof, message:

Call the mcp__picker__show_picker tool once, then reply only shown

Open the paired web client directly on the thread. Both evidence runs used Chromium, 1280x800 CSS pixels, light theme. Collapse thread details before recording to hide environment details.

1. Send: Run ./build.sh and wait for it to finish.
2. Wait for Running build.sh while the turn is active.
3. Click Pick blue in the inline picker app. The app acknowledges Picked; model context sent.
4. Fill the composer and press Enter with: Without calling any tools: what did the color picker app report to you? Quote it exactly, including any code. If you received nothing from the app, say exactly NO APP CONTEXT.
5. Observe Steer · waiting to be read becoming Steer. Wait for the completed reply.
6. Base reply: The color picker app returned exactly: "Picker shown." It included no code. Head reply: The color picker app reported: Color picker: the user picked BLUE-7731.

The after video concatenates the interaction recording with a second recording of the completed answer; no actions or responses were replaced. The base video is continuous.

Control on base: after completion, send the identical question as a new turn, without touching the picker again.
