test_planner_trigger
Dry-run the Dynamic Planner's escalation judge: would these messages be offered a
step-by-step plan? Use it after editing the agent's task, since the task text is the
business-domain gate — a vague task lets out-of-domain requests through, a narrow one
turns real customers away.
messages: the user's turns in order; the LAST one is treated as the current turn and the rest
as that user's earlier messages (same window the live judge sees). samples>1 re-runs the judge
to show stability (it is a probabilistic call). expect: pass true/false to get `matched`.
Nothing is stored — no session, no enrollment. Tokens count toward the tenant quota (kind=planner).
Returns {triggered, samples, goals[], domain, matched}. Reads the judge only: whether the user
then ACCEPTS the offer is a separate, user-controlled step.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent | Yes | ||
| expect | No | ||
| samples | No | ||
| messages | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |