fix: use ComponentPropsWithoutRef for intrinsic HTML elements

[markimbriaco]

Summary

Replaces with for all intrinsic HTML element type annotations across 6 component files.

Problem

includes the property in its type. When used with , this creates a duplicate ref type since already manages refs via its first generic parameter. This can cause incorrect type inference in strict TypeScript configurations.

Changes

• input.tsx — with
• textarea.tsx — with
• breadcrumb.tsx — non-ref components with
• pagination.tsx — mixed and non-ref components
• chart.tsx — components with
• sidebar.tsx — 20 intrinsic element type annotations

Component types (, , etc.) are intentionally left unchanged since is correct for extracting component prop types.

Impact

• Zero functional changes
• No breaking changes
• Aligns with React TypeScript best practices and shadcn/ui conventions

[vercel]

@markimbriaco is attempting to deploy a commit to the Anniversary Team on Vercel.

A member of the Team first needs to authorize it.

[markimbriaco]

Hey! Noticed the component type annotations for intrinsic HTML elements were using instead of . This causes a duplicate ref type when paired with since the ref is already handled by the first generic parameter.

This is a pure type-level fix across 6 files — zero functional changes, just aligns with React best practices and the shadcn/ui convention.

The Vercel check failure is just the deploy authorization gate for external contributors, not a code issue.