fix(web): prevent provider wizard footer overlap while loading - #18609

💭 Assessing object styles I need to evaluate a new style for the object regarding static overflow. The value is about dynamic holdHeight and whether it's clipping, so the height needs to remain dynamic. There shouldn’t be any violations. I’m thinking about including a final structure that outlines any mandatory conflicts in a straightforward way. A clear, one-line summary seems helpful here, like a concise overview of it all.

1. browse_code — apps/web/src/components/AnimatedHeight.tsx

2. browse_code — For apps/web/src/components/AnimatedHeight.tsx explain whether the changed overflow style on line 89 is determined by runtime holdHeight/isClipping state, and whether the change introduces any raw control, CSS rule, static inline style, or composer banner markup. Concise answer.

3. browse_code — Does the changed style object introduce any UI consistency rule violation under criteria: raw controls, new static inline styles replaceable with Tailwind, or composable component reuse? Answer only yes/no with brief justification.

4. browse_code — apps/web/src/components/AnimatedHeight.tsx

5. browse_code — apps/web/src/components/AnimatedHeight.tsx

6. browse_code — Confirm only changed lines in provided PR diff are overflow expression and object formatting in AnimatedHeight.tsx; is height value also runtime state? concise.

7. browse_code — apps/web/src/components/AnimatedHeight.tsx

8. browse_code — apps/web/src/components/AnimatedHeight.tsx

9. browse_code — Is inline overflow computed at runtime from holdHeight and state, rather than a newly added fixed static value? Answer briefly.

10. browse_code — apps/web/src/components/AnimatedHeight.tsx

11. browse_code — apps/web/src/components/AnimatedHeight.tsx

12. browse_code — apps/web/src/components/AnimatedHeight.tsx