fix: interrupt stream mode values

[casparb]

This PR improves the consistency of interrupt streaming.

• when streaming with stream_mode values, the stream chunk now contains the entire state alongside the interrupt:

class State(TypedDict):
    robot_input: str
# at this point in time robot_input is already set to  "beep boop i am a robot"
app.stream(..., stream_mode="values")
# before
{"__interrupt__": (Interrupt(value="interrupt",))}}
# after
{"robot_input": "beep boop i am a robot", "__interrupt__": (Interrupt(value="interrupt"))}

• when streaming with stream_mode=["values", "updates"], interrupts are surfaced in both an update stream chunk and the value stream chunk, when previously we keep interrupt in values only if we request values mode only

class State(TypedDict):
    robot_input: str
# at this point in time robot_input is already set to  "beep boop i am a robot"
app.stream(..., stream_mode=["values", "updates"])
# before (interrupt would only emit on update chunk, there would be no values chunk)
("updates", {"__interrupt__": (Interrupt(value="interrupt",))}})
# after
("updates", {"__interrupt__": (Interrupt(value="interrupt",))}})
("values", {"robot_input": "beep boop i am a robot", "__interrupt__": (Interrupt(value="interrupt"))})

For housekeeping: this PR improves on this revert: #6141

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
langgraph-docs-preview	Ignored	Preview		Nov 20, 2025 8:32pm

[sydney-runkle]

I'm a little confused, if we only have one stream mode, why is the result a tuple now?

[casparb]

I'm a little confused, if we only have one stream mode, why is the result a tuple now?

@sydney-runkle incorrect example, updated

the tuple in the test is because we have two stream modes but in the pr desc it shouldn't have been a tuple