OptionalEnforcesTrue when Reinvoke starts the turn under TaskContinuationParams.SecurityEnvelope exactly as an
agent node runs under its envelope: the same run scope, audience, bound parameters and tenant (on a
per-run user clone), starting tainted when the outcome is. The dispatcher posts a message instead of
reinvoking a graph whose envelope constrains anything when this is not true.
Posts the results into the conversation the graph answers.
OptionalReinvokeStarts the submitting agent a fresh turn carrying the outcome.
Optional: a host with no agent framework loaded (a worker, a test) legitimately cannot do
this, and the dispatcher degrades to PostMessage rather than dropping the completion.
Delivers a finished graph's outcome, per its
continuationmode.Abstracted for the same reason agent execution is: the dispatcher knows when a graph has settled and what it produced, but posting into a conversation and starting a fresh agent turn are host concerns. Injecting them keeps this package free of both the conversation layer and the agent framework — a dependency on the latter would be circular, since agents submit graphs.
A host that implements neither still gets correct behavior: the dispatcher logs the outcome and marks it delivered, so a graph never silently repeats its completion.