Summary
Baseline tests pass, but Selection and SelectionList emit Pydantic warnings because tuple-typed values fields sometimes serialize from list-shaped data. The warnings signal model-shape friction that is not yet a failure but could become one on a future Pydantic version upgrade.
Category
Severity
medium
Evidence
src/ssvc/decision_points/ (Selection, SelectionList classes)
Impact if Ignored
A future Pydantic upgrade may turn these warnings into validation errors, breaking serialization at runtime. The friction also makes it harder to add new decision-point types with confidence.
Suggested Action
Audit the values field type on Selection and SelectionList. Consider using List instead of Tuple where order is not semantically significant, or add explicit validators to coerce list input to tuples.
Summary
Baseline tests pass, but
SelectionandSelectionListemit Pydantic warnings because tuple-typedvaluesfields sometimes serialize from list-shaped data. The warnings signal model-shape friction that is not yet a failure but could become one on a future Pydantic version upgrade.Category
Severity
medium
Evidence
src/ssvc/decision_points/(Selection,SelectionListclasses)Impact if Ignored
A future Pydantic upgrade may turn these warnings into validation errors, breaking serialization at runtime. The friction also makes it harder to add new decision-point types with confidence.
Suggested Action
Audit the
valuesfield type onSelectionandSelectionList. Consider usingListinstead ofTuplewhere order is not semantically significant, or add explicit validators to coerce list input to tuples.