What's true now. When a signature has a History input, the system message lists it as an input field and shows [[ ## history ## ]]\n{history} in the structure template. The history is actually sent as earlier chat turns, so that section never appears in the request.
This comes from DSPy: Adapter.format builds the system message from the full signature and removes the history field only from the user message (dspy/adapters/base.py, DSPy 3.2.1). Imp inherits the same untrue statement.
Target. A History field is left out of the field list and the structure template, because it arrives as messages.
Done when.
- A captured request with a history input no longer lists it or shows its section.
- The parity differentials record the difference with its reason.
- The tests fail without the change.
What's true now. When a signature has a
Historyinput, the system message lists it as an input field and shows[[ ## history ## ]]\n{history}in the structure template. The history is actually sent as earlier chat turns, so that section never appears in the request.This comes from DSPy:
Adapter.formatbuilds the system message from the full signature and removes the history field only from the user message (dspy/adapters/base.py, DSPy 3.2.1). Imp inherits the same untrue statement.Target. A
Historyfield is left out of the field list and the structure template, because it arrives as messages.Done when.