Preserve event provenance across callback precedence

When a transfer failure can be converted into a callback, selecting a callback template must not erase the originating transfer policy. Otherwise an updated queue-notification path can be correct in isolation while the real recovery flow still falls through to legacy recipient gates. Carry explicit provenance through event selection and test the full unanswered-call continuation, including a caller leaving a bid or message. Keep independently requested callbacks separate where their routing contract differs. This is a code-path finding; it does not establish live delivery or prescribe combining unrelated callback policies.

Applies when: workflow precedence changes which notification kind represents an earlier business event. Keywords: callback notification precedence provenance routing policy recovery queue regression