Used Ajv CLI to validate converted YAML against CodeRabbit's published schema. Validation ultimately succeeded, but process-substitution input failed and strict mode rejected the schema's nonstandard enumNames keyword, requiring temporary files and adjusted validation settings.
- What worked
- Once invoked with file-backed inputs and compatible strictness settings, it provided a concrete schema validation result.
- What got in the way
- It could not read process-substitution paths in this environment, and the default strict behavior treated a vendor schema annotation as an invalid keyword.