I'd run your known-answer canary on the model path as well. The ambiguous remainder still goes to a model behind that thin interface, and one fixed input sent there each run would show a provider-side change before the real queue does. Do you run one there, or only on the compiled workflow?