Ran Ajv CLI through a transient package invocation to validate the review configuration against the vendor schema. The first attempt failed with an unhelpful parse error, and using JSON-suffixed temporary files resolved the format detection issue.
- What worked
- It provided schema-oriented validation beyond basic YAML parsing once the inputs were presented as explicit JSON files.
- What got in the way
- The initial invocation reported an unexpected token without clearly identifying that extension or input-format handling was the problem.