The fold isn't a separate open/closed component swapped in on hover — it's one button whose front face is a hinged plate in 3D space. Tilt it back and whatever's underneath becomes visible. Here's the hinge, the three things that tilt it, and the bar that lives behind it.

The button sits in a perspective(800px) space. Its front face is a single element with transform-origin: top center, so rotating it on the X axis tips the bottom edge away from the viewer while the top stays pinned — like a flap hinged at the top:

Behind that face, at -z-[1], sits a back layer: a tint that's always there, plus a progress bar that's scaleX(0) until loading starts.

Three completely different triggers — a mouse hovering, a keyboard user tabbing in, a status prop flipping to "loading" — all resolve to the same rotateX(35deg). None of them know or care which of the other two is also true; they're just three selectors pointed at one transform.

Once the face is tilted, the back layer is doing one of two things. If you pass a progress number, the bar is determinate — it scaleXs from the left to that fraction. If you don't, it's indeterminate — a fixed 40%-wide segment sweeps across on a loop:

@keyframes progress-fold-indeterminate {
  0%   { transform: translateX(-100%); }
  100% { transform: translateX(250%); }
}

Both modes stay on the compositor: determinate is scaleX against a unitless CSS variable (progress / 100), indeterminate is a fixed-width segment translating left→right. No layout property moves.

Determinate progress can't just start transitioning scaleX the instant status becomes "loading" — the CSS variable would already be set to the target fraction, and the bar would jump there with no fill animation at all. The fix is a two-step state: snap the fill to 0 synchronously, then arm the transition one frame later with requestAnimationFrame:

const [armed, setArmed] = React.useState(false);
React.useEffect(() => {
  if (!isLoading) {
    setArmed(false);
    return;
  }
  setArmed(false);
  const id = requestAnimationFrame(() => setArmed(true));
  return () => cancelAnimationFrame(id);
}, [isLoading]);

"group-[&[data-determinate=true][data-armed=true]]:[transition:transform_0.25s_ease]";

Without data-armed, the transition rule is live from the first paint and the browser has nothing to animate from — the bar would render already full. With it, the first frame paints at scaleX(0) untransitioned, and only the second frame turns the transition on, so there's always a "from" state to fill away from.

One hinge, three triggers, a bar that's either counting up or just letting you know it's still working. Click it.