test: add more edge cases for OP#12 (schema-vs-schema) validation

[Artifizer]

Summary by CodeRabbit

• Tests
  • Added comprehensive test coverage for schema validation scenarios, including enum modifications, property nullability changes, type widening, and constraint violations.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

The PR adds four new test classes to verify OP#12 schema validation behavior for enum value replacement, required property nullability changes, primitive type widening, and const-minimum constraint violations. The same four test classes appear duplicated in the file.

Changes

Cohort / File(s)	Summary
OP#12 Schema Validation Tests tests/test_op12_schema_vs_schema_validation.py	Adds four test classes covering enum value replacement, required property nullability, primitive type widening, and const-minimum violations. Each test class includes schema registration and validation steps. Notable: the test classes are duplicated in the file, which should be verified as intentional or removed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• tests: update the tests for OP#12 (validate schema -> schema) and finalize the required openapi.json #56: Both PRs modify OP#12 schema validation tests in the same file, with overlapping test scenarios and coverage areas.

Poem

🐰 Four validation tests now hop through the file,
Checking schemas with enum style,
Type widening, nullability, constraints galore—
But look! The rabbit sees duplicates galore! 🎭

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding new test cases for OP#12 schema-vs-schema validation edge cases, which matches the four test classes and validation scenarios introduced.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}