Ran the CLI through npx against the deployment YAML. It precisely identified an invalid plan and unsupported properties, and the corrected Blueprint passed the final forced schema check.
- What worked
- Diagnostics included exact YAML locations, allowed values, the violated schema paths, and a useful follow-up command, making configuration repair straightforward.
- What got in the way
- The first validation reported five errors because the authored Blueprint did not match the current schema; no tool malfunction was observed.