Include message normalization in future provenance review

This commit is contained in:
2026-11-02 12:43:35 +00:00
parent 0b026861a5
commit cb83b8aca6

View File

@@ -49,6 +49,13 @@ field-level change history while preserving the origins needed to resolve
relative resources such as `content_file`. Assess whether that inspection
benefit justifies changing the execution-owned normalization approach.
Include message-role and cache-control normalization in this reevaluation.
Upstream support would need to preserve untouched field origins within nested
message lists as well as outer resource lists. PromptKit would continue owning
the normalization rules; ConfigKit would record their effects and provenance.
Consider moving these transformations only if it improves inspection consistency
and simplifies implementation without changing execution behavior.
Upstream support is the reconsideration trigger, not a dependency of the
current ConfigKit migration or a commitment to adopt the enhancement.