Refactor materialization operations to use MaterializeOp model

[jfrench9]

Summary

Refactors the materialization operation logic to use a dedicated MaterializeOp model, replacing inline/ad-hoc parameter handling with a structured, typed approach. This aligns materialization operations with the existing pattern used by other graph operations (e.g., UpgradeTierOp).

Key Accomplishments

• New MaterializeOp model: Introduced a dedicated Pydantic/data model (materialize_op.py) that encapsulates all parameters and validation logic for materialization operations, improving type safety and maintainability.
• New UpgradeTierOpNewTier model: Added a supporting model for the upgrade tier operation's new tier representation, further strengthening the type system across graph operations.
• New DatabaseHealthResponse model: Added a structured model for database health responses (93 lines of new model code), replacing loosely-typed response handling.
• Simplified op_materialize.py: Reduced the materialization operation module by ~100 lines by delegating parameter construction and validation to the new MaterializeOp model, significantly improving readability and reducing duplication.
• Updated graph_client.py: Adjusted the graph client to work with the new model-based approach for materialization calls.
• Exported new models: Updated models/__init__.py to expose the new models as part of the public API.

Breaking Changes

• API surface change: Consumers that previously constructed materialization operation parameters inline will need to migrate to using the MaterializeOp model. The method signatures in the graph client have been updated accordingly.
• Model imports: New models are now available via robosystems_client.models; any code importing directly from internal modules may need path updates.

Testing Notes

• Existing materialization tests (test_materialization_client.py) have been updated to reflect the new model-based interface.
• Verify that all materialization workflows (create, update, delete) function correctly end-to-end with the new MaterializeOp model.
• Validate that the DatabaseHealthResponse model correctly deserializes health check responses from the API.

Infrastructure Considerations

• No new dependencies introduced; the new models follow existing patterns and frameworks already in use.
• Downstream services or CI pipelines that depend on the materialization client interface should be validated against the updated method signatures.
• This is a stepping stone toward a consistent model-driven pattern for all graph operations, making future operation additions more straightforward.

---

🤖 Generated with Claude Code

Branch Info:

• Source: refactor/additional-graph-ops
• Target: main
• Type: feature

Co-Authored-By: Claude noreply@anthropic.com