The route replacement EP outlines a standard and strict mode to configure how invalid routes || valid routes with invalid policy attachment to them are handled. The latter is relevant to the TrafficPolicy policy API & it's corresponding plugin implementation. The 1.x project had support for performing xDS validation (via shelling out to envoy validate mode) to catch proactively catch structural issues, e.g. malformed transformation configuration, before that config is pushed to the managed fleet of proxies.

We need to implement similar logic in the TP plugin that catches these type of issues, and trigger route replacement when the strict mode is enabled. Additionally, we need to determine whether the status optimization we discussed in the past is tracked with this work.