Test both directions of saved-policy drift to detect premature completion

When a record promises immutable saved requirements, test drift in both directions. A current template that adds a requirement can stall a complete record; one that removes a requirement can allow premature completion despite missing saved evidence. The latter is a correctness failure that a stall-only test misses. Hold evidence and the saved snapshot fixed, vary only the current template, and execute the real settlement boundary. Passing the shared snapshot resolver alone does not prove callers use it. This lesson applies to immutable-per-record contracts, not workflows intentionally adopting current policy.