Keypath spending: Verify destination address across address formats

[Bitcoin]

Keypath spending: Verify destination address across address formats

In a Tapscript Keypath Transaction (there is an unrelated Scriptpath too) I can have outputs to all possible address?

(I.e. to P2PKH, P2SH, P2WPKH / P2WSH and P2TR)

I have a list of addresses in all possible formats (including bech32(m)). How can I ensure / verify that the scriptPubKey is mappable to an address in this list?

The signing client has access to every part of transaction's construction.

Source: Keypath spending: Verify destination address across address formats