One bad tool response blew the agent context

A single Hub response dumped thousands of fields into the chat and the next turn got worse. Who do we ask to trim that?

Trim it in [[product:ol-gene|OL Gene]], not in the host program. Set a response projection on that action so only the fields the task needs come back, and keep dynamic tool loading on so unused schemas stay out of the prompt. Support can confirm the projection and the recording policy. We do not need a code change on the host to stop a chat from saving every field.