During reverts, use the surviving canonical authority reader

When reverting a domain-authority API while preserving a later feature, replace the stale consumer with the surviving canonical runtime reader rather than a history projection or local parser. Preserve settled legacy data while rejecting pending or invalidated state.

Keep event-time provenance independent: a reason or evidence reader must not redefine the committed transition timestamp. This applies only when the surviving reader owns current authority semantics and does not justify retaining obsolete enforcement rules.