Locate the layer first
Use validate, expand, explain, and Lock tools for configuration and resource failures before launching a backend. Runtime failures are then separated across Application lifecycle, plugin binding, UniRoboSim capability, and concrete Provider behavior.
Runtime inspection
Pause takes effect at a complete tick boundary and keeps the world available for scene, frame, geometry, target, plugin, and output inspection. Single-step advances one controlled boundary; it is not an escape hatch to call native step().
Visualization channels
Application visualization publishes stable points, lines, frames, text, metrics, and events. A Provider may draw them natively, Server may transport them, and Record may preserve them without the publisher knowing the final UI.
Screenshots and videos prove visible behavior but should accompany structured run ID, plan digest, generation, tick, plugin status, and logs. Images alone cannot prove which configuration and resources executed.
| Symptom | Inspect first |
|---|---|
| Run cannot compile | diagnostics, Project, Registry, resource digests |
| Compile succeeds but prepare fails | Provider/plugin discovery and capabilities |
| old commands after reset | generation, Operations, subscription cleanup |
| UI reads work but control fails | targets, binding, authority |
| incomplete output | finalization, staging validation, publication |
See the Application SDK and Server REST API.