OP_CAT + OP_CHECKSIGFROMSTACK: how to prevent cross-UTXO signature reuse?

Wait 5 sec.

Following up on #130598.I built a CAT + CSFS oracle-style script on signet (commit, reveal):OP_CAT OP_SHA256 OP_CHECKSIGFROMSTACKWitness: [sig, PART1, PART2]Message: SHA256(PART1 || PART2)Since CSFS only checks the message, the same (sig, PART1, PART2) appears to be reusable across multiple UTXOs with compatible scripts.For price oracles this is usually acceptable. But if the goal is single-use authorization (i.e., the signature should only be valid for one specific UTXO):Is committing to the outpoint inside the message the only general approach?Or is there a script-level pattern that avoids requiring the oracle to wait for the UTXO to exist before signing?