recover
Re-derive the vault at an already-committed (unlockValue, leaf) parsed off an on-chain script, WITHOUT the LOCKTIME_THRESHOLD ceiling that gates new-vault creation.
Recovery must reproduce whatever unlock value the chain actually committed to — including observed on-chain vaults at 2^31-2 (2147483646), far above the nLockTime height/time split — so the recomputed locking-script bytes can be matched against the on-chain output to confirm ownership. Re-derivation locks no funds, so the height-misinterpretation risk the ceiling guards against does not apply here.