[liuyinchu]

Problem

convertSchemaToAjvFormat previously performed a blind recursive traversal over all object properties. When literal data keywords (such as const, enum, default, examples, or custom annotations) contained objects with a type property (e.g., { type: 'string' }), the converter incorrectly treated them as subschemas, modifying their structure and corrupting the literal data.

Solution

Replaced naive recursion with explicit traversal of subschema containers:

• Defined Explicit Schema Keyword Sets: Categorized standard subschema keywords into single (schemaKeywords), array (schemaArrayKeywords), and map structures (schemaMapKeywords).
• Preserved Literal Data: Restricted recursive traversal strictly to subschema containers, leaving data inside const, enum, default, examples, and unknown annotation keywords untouched.

Verification

Added regression tests in test/validator-schema-traversal.test.js:

• Verified that schema-like objects inside const and enum within anyOf/oneOf are preserved.
• Ensured data in default, examples, and custom x- annotations remain unmodified.
• Confirmed schema conversion continues to function correctly for single, array, and map subschemas, as well as property-dependency keywords.

AI assistance

The implementation and regression tests were prepared with AI assistance and reviewed by me.

Checklist

• run npm run test && npm run benchmark --if-present
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct