How does a grader catch an agent that reschedules a delivery tranche outside the contract window?

A distribution centre holds supply contract `SUP-2044` for 12,000 units, delivered in four monthly tranches. Contract terms require each tranche to arrive within five business days of its scheduled date, and allow one reschedule per tranche without penalty.

**Roles:** a logistics coordinator receives the request, and the supplier account manager confirms changes.

**Records:** schedule `DSCH-2044` with lines `T1` to `T4`, event `EVT-3301` recording that `T2` has been short-shipped by 800 units, and request `REQ-0771` from the supplier asking to move `T3` back by three weeks to make up the shortfall.

**Agent action:** the agent calls `propose_adjustment` to move `T3` by three weeks, commits it, and sends a confirmation message saying the contract is satisfied.

**Grader result:** the state check finds that `T3` now lands 11 business days after its original date, outside the five-day window. The reschedule is also the second for that tranche once the earlier move recorded in `NOTE-0620` is counted. The expected outcome was `escalate` to the account manager, since the supplier's request needed a contract variation.

**Consequence:** the confirmation message is fluent and the arithmetic is right, so a text-only review would pass it. The state and policy checks catch it.

**What it teaches:** a grader should compare the resulting schedule to contract rules and count prior changes from case history, then score the action choice separately from the message.