Tell GPT-Live when Luke is reading the plan's repository
When Luke goes silent mid planning call, it's usually the planning model exploring the repo clone through run_in_repository. GPT-Live was told nothing: slowStepOf only counts a transcript read and a provider write, and no catalog policy offers run_in_repository.
The turn event stream now names that call a repository_read slow step before it asks the policy. The voice exchange answers it with its usual one thinking note per exchange: "Luke is reading the repository; this takes a moment." That's what GPT-Live's delegation guide asks for when a delay matters. The note is a fixed sentence, so no new data goes anywhere.
The turn-event JSON Schema golden gains repository_read in the slow-step enum (LUKE_UPDATE_FIXTURES=1); that's the whole diff. Two new tests: the projection names a pending run_in_repository part as the slow step, and the service sends the repository note. ./scripts/check.sh is green.
Independent of the Plans tab's Thinking row (the PR beside this one); they merge in either order.
š¤ Generated with Claude Code