Buddy: a steer into Buddy's turn gets upstream's page-context projection, not the Czech page block #150

What happens

A steer into Buddy's running turn reaches Hermes with upstream's projection of the page context, not the overlay's Czech page block.

• A normal turn on the buddy instance projects through LazurioBuddyPrompt.projectComposerContextForProvider (apps/server/src/orchestration-v2/ProviderTurnStartService.ts:762 on the v0.1.5 rebuild head 2d22c87f35).
• A steer projects through upstream's projectComposerContextForProvider from @t3tools/shared/composerContextReferences (apps/server/src/orchestration-v2/ProviderTurnControlService.ts:369, imported at :1), whatever the instance.

So when a person steers Buddy's turn with a page chip attached, Hermes gets upstream's <t3_context> form of the records instead of the Czech page block it gets on every other turn. Since steer is the default for a message sent while Buddy works (#138), this is the common path, not an edge case.

Not introduced by the rebuild

The v0.1.3 line already did this: the v0.1.4 message of the Buddy prompt row records that "the prompt-command and steer projections stay upstream's as before". The independent check of the v0.1.5 rebuild (#148, PR #149) found it again; it is filed here so the rebuild does not widen its scope.

Proposed fix

Route the steer's text through LazurioBuddyPrompt.projectComposerContextForProvider with instanceId: run.providerInstanceId, as the turn start does, and add a test that steers Buddy's turn with a page chip and asserts the Czech block reaches the provider (it fails on today's code). The other upstream projection in the turn start (ProviderTurnStartService.ts:523) only feeds the provider-auth prompt-command check and never reaches the provider, so it can stay.

🤖 Generated with Claude Code