Optional trajectory tests

A trajectory file is an optional engineering-owned test file for tool calls, tool order, arguments and backend evidence.

Trajectory checks are useful when engineering wants strict verification, but they are not required for business-authored acceptance testing. Trajectory tests can run with or without workflow tests.

What a trajectory check catches

The published card-block trajectory report checks the same journey the business team authored, but at the level of execution:

• which tools were called, and in what order;
• whether the arguments matched the entity the customer selected;
• whether the confirmation prompt accepted natural language, or demanded a rigid phrase.

That last check is the one that failed. The agent asked the customer to reply with an exact phrase — Reply "Yes" to confirm — which reads as reasonable in the transcript and is a usability defect in the trace.

None of that is visible from the final response alone.