fix: pin datamodel-code-generator to 0.25.0 to match original generation

Issue: Models were originally generated with an unknown version of datamodel-code-generator
installed globally. When regenerated with v0.43.0, it introduced breaking changes:
- Enum → StrEnum (changes string comparison behavior)
- Field(...) → Annotated[type, Field(...)] (different syntax)

Investigation: Tested versions 0.25.0 through 0.35.0 and found v0.25.0 produces
output matching the original generation:
- Uses Enum (not StrEnum) - maintains backwards compatibility
- Uses Field(..., description=) syntax (not Annotated)
- Supports Pydantic v2 RootModel pattern

Changes:
- Pinned datamodel-code-generator==0.25.0 in pyproject.toml
- Removed --use-annotated flag from generation script
- Regenerated models with correct version
- All model tests now pass (46/46)

This ensures:
✓ No breaking changes for customers using EventType, Operator, etc.
✓ Consistent generation across environments
✓ Backwards compatible enum behavior (EventType.model != 'model')

✨ Created with OpenCode

Author: skylarmb

pyproject.toml

@@ -56,7 +56,7 @@ dev = [
     "pre-commit>=3.0.0",  # For git hooks
     "requests>=2.31.0",  # For docs navigation validation
     "beautifulsoup4>=4.12.0",  # For docs navigation validation
-    "datamodel-code-generator==0.43.0",  # For model generation from OpenAPI spec
+    "datamodel-code-generator==0.25.0",  # For model generation from OpenAPI spec (pinned to match original generation)
     "openapi-python-client>=0.28.0",  # For SDK generation
     "docker>=7.0.0",  # For Lambda container tests
 ]

scripts/generate_v0_models.py

@@ -98,7 +98,8 @@ def main():
         "3.11",
         "--output-model-type",
         "pydantic_v2.BaseModel",
-        "--use-annotated",
+        # Note: --use-annotated flag removed to match original generation style
+        # Original used Field(..., description=) not Annotated[type, Field(description=)]
     ]
 
     print(f"Running: {' '.join(cmd)}")