Plan field-level configuration normalization

docs/roadmap/future.md

@@ -40,28 +40,9 @@ consumers.
 
 ### Field-Level Normalization With Preserved List Provenance
 
-Reevaluate normalizing resource fields directly in ConfigKit's effective
-configuration after upstream ConfigKit supports recording changes within a
-list without replacing the source attribution of unchanged fields.
-
-This could let configuration inspection show PromptKit-normalized values and
-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 normalization of roles and cache-control values in configured messages
-in this reevaluation. This could make inspection reflect the values used for
-execution and reduce separate normalization paths. 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. Caller-appended messages
-would still need request-time normalization because they do not pass through
-ConfigKit.
-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.
+Selected for planning following ConfigKit v1.1.0. The
+[field-level normalization roadmap](field-normalization.md) owns the target
+behavior, scope, and implementation stages.
 
 ## Entry Format