The project uses @base-ui/react, whose Button has no asChild prop —
just a `render` prop that takes a React element to merge into. About
14 call sites across the routes still use the Radix-shaped
`<Button asChild><Link to="…">…</Link></Button>` pattern, which until
now was producing nested-button DOM violations and asChild leaking as
a DOM attribute.
Bridges asChild → render inside the Button wrapper:
<Button asChild><Link to="/login">Sign in</Link></Button>
…now renders as a single <a class="…btn classes…">Sign in</a> instead
of <button asChild><a>…</a></button>.
No call-site changes required; consumers keep the Radix ergonomic and
get correct DOM under the hood.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2a68389121