feat(card): apply the tilt hover effect on the single-user page (#64)

[eeshsaxena]

Closes #64.

What

The Versus page wraps its card in TiltCard (the lean-toward-the-cursor plus specular sweep), but the single-user page - the more visited of the two - renders a bare PlayerCard. This applies the same effect there.

It reuses the existing TiltCard rather than duplicating the physics, and passes the same maskSrc={resolveCardTheme(card).bg} that DuelView uses, so the shine is clipped to the card's silhouette instead of painting a rectangle.

The one non-obvious bit: where the wrapper goes

TiltCard wraps the capture container, not the card:

<TiltCard maskSrc={resolveCardTheme(card).bg}>
  <div ref={captureRef} className="relative">
    ...glow...
    <PlayerCard card={card} />
  </div>
</TiltCard>

renderCardImage does node.cloneNode(true) on captureRef.current, so it exports exactly that subtree. Wrapping outside captureRef keeps TiltCard's hover-glass overlay a sibling of the captured node, so it can never end up in the downloaded or copied PNG. Wrapping inside (around PlayerCard alone) would have put the overlay into the export.

The tilt transform is likewise applied to the parent, and renderCardImage re-anchors the clone at the viewport origin, so it does not affect the exported image either. FlagPicker stays outside captureRef exactly as before.

Verification

• npx tsc --noEmit clean; npm run lint 0 errors; npx vitest run green (20 files, 217 tests).
• Confirmed the export path structurally: only the captureRef subtree is cloned, and the hover glass sits outside it.

An AI assistant helped implement this; I reviewed the change and ran the typecheck, linter and tests locally.

[eeshsaxena]

Closing this one - I could not verify the hover behaviour in a running browser on my side, and I would rather not land a visual change I have only reasoned about statically. Happy to leave #64 open for someone who can check it end to end. Thanks!

[Younesfdj]

@eeshsaxena I checked it in the browser across the result page, hover feels right.
Reopened it myself since the closing reason is covered now. Anything left on your side, or good to merge?

[eeshsaxena]

Sorry for closing this, it was closed by mistake during a cleanup. The PR looks good from my side, happy for it to be reviewed and merged whenever convenient.

[Younesfdj]

@eeshsaxena Im merging this now, thank you