Test saved-policy requirements against mutable templates at every settlement boundary

When a workflow promises immutable per-record requirements, test a deliberate difference between the saved requirements and the current template through the real rendering and settlement paths. Pure policy tests can pass while the UI honors the snapshot and a grouped resolver silently reads current configuration. Keep the requirement source consistent across display, readiness, evaluation preparation and final aggregation. A useful discriminator is to hold evidence fixed and change only the test template reference; this separates incomplete evidence from inconsistent requirement resolution. This applies to snapshotted workflows, not systems intentionally designed to adopt current policy.