# Late ACP load model-switch proof

Environment for both recordings: Linux web client, Chromium, 1280 x 800 CSS viewport (device scale 2), light theme. Each commit ran its own real development server, fresh T3 home and synthetic demo repository. No real provider account or database was used.

Use prepare.py with a new T3 home. Keep controlled-acp.mjs beside it. Run the checkout's dev server with that home and T3CODE_DEV_SEED=0; add the generated demo directory through `t3 project add`, then run:

```sh
t3 thread start "$DEMO" 'Save a conversation.' --title 'Late session controls' --provider grok --model grok-build --wait --json --base-dir "$TEST_HOME"
```

Stop and restart the complete development server on the same home. Pair the browser and open the returned thread by its environment/thread link. Dismiss the Grok catalog warning (the controlled agent intentionally has no global model catalog). The settings include Model Alpha and Model Beta as custom model choices; initialize deliberately supplies no session configuration.

The same browser interaction on both sides:

1. Type `Load the saved session and continue.` into the conversation composer and press Enter.
2. The fixture immediately replays history, stays quiet, and returns its final session configuration 3200 ms later. ACP v2 calls this wire method `session/resume`; T3's load operation reports it as session/load.
3. Wait until `Late load finished. Ready for a model switch.` appears. That reply waits for the final configuration response, so selection cannot precede the late response.
4. Open `[data-chat-provider-model-picker-label]`, choose the option containing `Model Beta`, then press Escape.
5. Inspect whether a model-switch-capability error appears.
6. Send `Confirm the selected model.` and inspect the agent's actual selected model.

Base: the picker reports `Could not apply model selection` and `The active ACP session does not expose a model-switch capability.` A subsequent message recovers and reaches Beta; the bug shown is the rejected immediate in-session selection, not a claim that subsequent turns remain broken.

Head: no picker error; Model Beta is accepted and the next reply confirms it. Native request logs also show the head adopting the final load response after provisional replay-idle readiness, then accepting session/set_config_option.

The before still is a repeated selection attempt in the same late-loaded state, captured before sending another message, after dismissing the catalog warning. Each still was checked against an identical screenshot taken 500 ms apart. Recordings show the full original interaction, including the later base recovery.

Not covered: concurrent newer choices, superseded sessions, actual provider CLI behavior, and visible reasoning-control restoration. The fixture supplies reasoning options but Grok's UI did not expose them in this setup.
