A developer's first integration run should not depend on a paid mistake
A new teammate runs a README example without knowing whether it creates a real order. Introduce a SimAggregator integration through a local training flow with a clear boundary between demonstration and live action. Do not call your own test harness a platform sandbox.
Provide synthetic inputs, the expected screen, and a sanitized log example. Let the newcomer follow the path from user action to result, then restore it after a restart. Understanding the project structure matters more at this stage than receiving a real SMS.
Document the separate move to a live environment: who authorizes the test, which tasks are permitted, where configuration belongs, and how to stop execution. Secrets should not appear in training examples or shared presentations.
Ask someone who did not write the guide to follow it. Add any explanation they otherwise need verbally. Finish with a short synthetic failure investigation: the newcomer describes the observations, remaining uncertainty, and appropriate next step. That demonstrates understanding better than a successful run guided by the original author.