feat(wallet): tick the balance up when a scanned bill is claimed

[bmc08gt]

Put in Wallet dismissed the bill and left the user on the scanner. The money they had just taken only showed up the next time they opened the wallet, already counted.

The button now takes them to the wallet tab and the balance rolls up on arrival.

Why there's a coordinator for this

The roll needs a "before" to start from, and there isn't one by the time the wallet opens. tokenCoordinator.add credits the account when the bill is grabbed, several taps before the claim, so every flow the wallet reads has already moved.

WalletRevealCoordinator carries the pre-credit picture across that gap:

1. CodeScanDelegate captures the totals immediately before the credit.
2. claimReceivedFunds() arms the snapshot and dismisses the bill. It's a separate BillOperations method rather than a branch inside dismissBill(PutInWallet), because that same result also covers a grab timeout, a cancel, and a swipe-away, none of which is the user asking to see their wallet.
3. The wallet opens on the snapshot, holds it for 450ms, then releases to live values.

The header and each card's balance already draw through AnimatedNumberText, so the roll itself is just the rendered string changing. The claimed token's own card balance is held back too, so its number rolls in step with the total above it instead of sitting there already updated.

The hold is timed from the wallet reporting itself drawn, not from the tap, so a slow tab doesn't spend the window behind the loading spinner. A reveal nobody collects releases itself after 3s, which also means there's no logout or reset wiring to keep in sync.

Only scanned bills route

A cash link is claimed from a link rather than from the scanner, so nothing is captured for it. arm() returns whether there was a snapshot, claimReceivedFunds() passes that back, and the decorator navigates only on true. The cash link confirmation dismisses where it stands, as it did before.

New card entry

A claim in a currency the wallet didn't hold is withheld from the deck for the same beat, then passed to TokenCardStack as enteringMint. The deck opens a slot from 0 to the full fanned reveal and the card fades in over the first half of that.

The caller names the entering card rather than the stack diffing its own token list. The case that most needs the animation, a wallet that held nothing so the stack was never composed, is exactly the one a diff can't see. The entry offset is read in the placement phase alongside scrolledPast, so it only re-places cards, and the measured height stays the full fanned height so the list's scroll range doesn't move.

Tests

WalletRevealCoordinatorTest covers the capture/arm/hold/release cycle: a capture is consumed once so a second tap can't replay it, arming with nothing captured publishes nothing and reports false, a redraw part way through the hold doesn't extend it, and an uncollected reveal times out. CodeScanDelegateTest asserts the ordering the whole thing rests on, that the snapshot is taken before the credit. BillPresentationDelegateTest covers both claim paths and checks the other PutInWallet dismissals leave the reveal alone.