Read blueprint/40-pruebas.md and follow it. The procedure lives there, not here.
The simulator writes like a contact and shows what the agent replies. It runs with the provider
demo, which is not a fake transport: it replays recorded deliveries, the same raw bytes and the
same signature header. It does not ask for credentials and what happens here counts.
Three things to look at:
pasosbrings six elements. If it brings five, the cycle was cut short and the output does not validate.- With the mode in
borrador, steps 3, 4 and 5 remain insin-confirmarand do not write anything. - The offered times come from
disponibilidad. One that is not there is a failure.
When the case passes, run /revisar. A case in green is not the gate in green.