Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/web/app/`(marketing)/download/page.tsx:
- Around line 86-97: The SVGs inside the platform CardHeader blocks are
decorative and must be hidden from assistive tech; update each <svg> in the
CardHeader (e.g., the macOS card SVG in the CardHeader containing the h2
"macOS") to include aria-hidden="true" and focusable="false" so they're ignored
by screen readers, and apply the same change to the other platform SVGs in this
file (the other CardHeader SVGs for the other platforms).

In `@apps/web/app/`(marketing)/philosophy/page.tsx:
- Around line 161-164: The Link component's className in page.tsx still
hardcodes hover:bg-white/5 and hover:text-white; update that class string on the
Link (the element with className starting "inline-flex items-center...") to use
the design-system semantic tokens used elsewhere on the page (replace
hover:bg-white/5 with the matching hover:bg-* token and hover:text-white with
the corresponding hover:text-* token) so the hover state aligns with the
tokenized color system.

In `@apps/web/app/`(marketing)/pricing/page.tsx:
- Around line 99-100: Replace the hardcoded hex props passed to BorderBeam
(colorFrom="#8b5cf6" colorTo="#6d28d9") with design-token backed values (CSS
variables or shared semantic tokens) so the beam follows theming, e.g. use
var(--token-name) or your shared token constants instead of literal hex strings;
update the JSX where BorderBeam is used and ensure the BorderBeam prop types
(colorFrom/colorTo) accept CSS variable strings if needed so no runtime/type
errors occur.
- Around line 32-34: The page is rebuilding numeric price values from
proPricing.amountCents (monthlyPrice and annualPrice) and forcing decimalPlaces
for the annual path, duplicating pricing logic and risking incorrect displays;
instead, remove the manual amountCents/100 calculations and any hardcoded
decimalPlaces and use the formatted price labels provided by the product-config
pricing facade (packages/product-config/src/facade.ts) wherever proPricing is
consumed (replace usage in monthlyPrice/annualPrice and NumberTicker rendering
and the similar code around lines 109-131) so all display formatting comes from
the facade's canonical pricing fields.
- Line 1: Remove the top-level 'use client' directive from the pricing page so
the route remains a server component; keep client boundaries on the interactive
children (ensure NumberTicker, Accordion, BorderBeam remain as client components
with their own 'use client' directives) and continue using getProductConfig() on
the server to avoid shipping pricing config/static content to the client bundle.

In `@apps/web/app/globals.css`:
- Around line 83-138: Add a prefers-reduced-motion escape hatch: create an
`@media` (prefers-reduced-motion: reduce) block that targets the animation
utilities animate-shiny-text, animate-marquee, animate-marquee-vertical,
animate-shimmer-slide, and animate-spin-around and override them to disable
motion (e.g., set animation: none !important and reset transforms where
appropriate). Ensure you also neutralize any ongoing transform effects from
keyframes like marquee, shimmer-slide, and spin-around by setting transform:
none !important on the same selectors so users who prefer reduced motion do not
get forced animations.
- Around line 5-25: The CSS uses Tailwind v4 directives (`@theme`, `@utility`,
`@apply`) that Biome and Stylelint don't recognize; update lint configs
(biome.json and .stylelintrc.json) to accept Tailwind v4 syntax by adding the
appropriate parser/plugins or rules for Tailwind directives, or alternatively
add an explicit ignore/exclude for this CSS file in those configs so the linter
skips it; ensure you reference the Tailwind directive tokens (`@theme`, `@utility`,
`@apply`) when adding rules/plugins so the linter stops flagging them as errors.

In `@apps/web/components/FaqAccordion.tsx`:
- Around line 39-40: The AccordionItem is using the array index for both key and
value, which breaks stable UI state when items are filtered or reordered; update
the items.map in FaqAccordion.tsx to use a stable per-item identifier (e.g.,
item.id, item.slug, or a deterministic hash of item.question) for both the React
key and the AccordionItem value instead of `index` so open/closed state remains
tied to the same question (refer to the AccordionItem component and the
items.map call to locate where to change `key={index}` and
`value={`faq-${index}`}`).

In `@apps/web/components/landing/Hero.tsx`:
- Around line 47-53: The CTA currently nests a Link inside ShimmerButton
(creating a <button><a>), which is invalid; update the Hero CTA so the
interactive elements aren't nested: either move Link to be the outer element
wrapping ShimmerButton (render the button visuals inside an anchor) or add
asChild support to ShimmerButton so it can render as an anchor when used with
Link; locate the usage in Hero.tsx (the ShimmerButton + Link block) and adjust
the component composition so a single interactive element is rendered (use
ShimmerButton asChild prop or wrap ShimmerButton with Link) and ensure
keyboard/screen-reader behavior remains intact.

In `@apps/web/components/landing/WhyLocal.tsx`:
- Around line 21-39: The CellValue component renders Check/X icons for boolean
values without accessible text; update CellValue to include a readable text
equivalent for booleans (e.g., "Yes"/"No" or the positive/negative semantic) so
assistive tech can consume it: when typeof value === 'boolean' render the icon
plus either an aria-label on the icon (aria-label={`${positive ? 'Yes' :
'No'}`}) or a visually-hidden span (sr-only) containing the string, ensuring
existing string paths remain unchanged; reference the CellValue function and its
value/positive props when making the change.

In `@apps/web/components/magicui/animated-grid-pattern.tsx`:
- Around line 115-136: The inner decorative <svg> should be a translated <g>
element: replace the <svg x={x} y={y} className="overflow-visible"> wrapper in
the AnimatedGridPattern mapping with a <g> that uses transform={`translate(${x},
${y})`} (and keep className="overflow-visible") so the child motion.rects and
their props (width, height, x, y, key, onAnimationComplete ->
updateSquarePosition) remain unchanged; remove the invalid x/y attributes on the
wrapper and ensure the closing tag is </g> to preserve the same visuals without
adding an extra SVG.
- Around line 8-18: The prop repeatDelay declared on AnimatedGridPatternProps is
never used and currently leaks onto the outer <svg>; update the
AnimatedGridPattern component to destructure repeatDelay from its props (e.g.,
const { repeatDelay, ...rest } = props), remove it from the spread passed to the
outer <svg>, and include it in the motion transition config (e.g., transition: {
duration, repeat: Infinity, repeatDelay } or the existing transition object used
by the motion element). Ensure you reference the repeatDelay variable when
building the transition and do not pass repeatDelay through ...props to the svg.

In `@apps/web/components/magicui/animated-shiny-text.tsx`:
- Around line 22-31: The class list in AnimatedShinyText (in
apps/web/components/magicui/animated-shiny-text.tsx) uses hardcoded neutral
color utilities (`text-neutral-600/70`, `dark:text-neutral-400/70`); replace
those with the design token classes (e.g., `text-text-secondary` or
`text-text-muted` and the corresponding dark-mode token) within the same
className composition so the shine effect keeps its background/gradient classes
(the animate-shiny-text, bg-clip-text, bg-gradient-to-r, etc.) but uses
tokenized text color utilities instead of literal neutral values; update any
references to the component’s className composition to preserve ordering and
specificity.
- Around line 1-3: Remove the blank line separating the import groups so the
React imports (ComponentPropsWithoutRef, CSSProperties, FC) and the local
utility import (cn) are adjacent; update the top of the animated-shiny-text
component file to place the two import statements back-to-back with no empty
line between them.

In `@apps/web/components/magicui/border-beam.tsx`:
- Around line 90-95: The current animation ping-pongs because initial={{
offsetDistance: `${initialOffset}%` }} is always the same while the reverse
branch supplies a two-stop array; change the logic in the BorderBeam component
to compute start and end offsets once (e.g., start = reverse ? `${100 -
initialOffset}%` : `${initialOffset}%`, end = reverse ? `${-initialOffset}%` :
`${100 + initialOffset}%`) and use initial={{ offsetDistance: start }} with
animate={{ offsetDistance: end }} (a single target) so the beam starts at the
correct reverse position and moves in one direction rather than ping-ponging;
reference the initialOffset, reverse, and offsetDistance values when
implementing the fix.

In `@apps/web/components/magicui/marquee.tsx`:
- Around line 42-71: Clamp the incoming repeat value to a safe positive integer
before using Array(repeat) (e.g., coerce via Number.isFinite and Math.max(1,
Math.floor(...)) or clamp to an upper bound) to avoid crashes on negative/NaN
counts, and when rendering the duplicated tracks inside the map (the elements
created in the Marquee component where Array(repeat).fill(0).map(...) produces
child tracks) mark cloned tracks as hidden to assistive tech by adding
attributes like aria-hidden="true" and tabIndex={-1} (only keep the original
items accessible) so screen readers don’t announce duplicates; update the
Marquee props handling to perform the clamp and update the mapped divs to
include the accessibility attributes for clones.

In `@apps/web/components/magicui/number-ticker.tsx`:
- Around line 26-27: The span that renders the initial number must use the same
formatted initial value passed into useMotionValue so the first frame and
decimalPlaces formatting match; change the component to compute an initialSeed =
(direction === 'down' ? value : startValue), format it using the same formatting
logic/decimalPlaces used for the motion value, pass initialSeed to
useMotionValue (motionValue) as now, and use the formattedInitialSeed for the
initial DOM text instead of raw startValue; apply the same change to the other
mount points referenced (the blocks around the useMotionValue calls at the other
two locations).

In `@apps/web/components/magicui/shimmer-button.tsx`:
- Around line 11-12: The ShimmerButton props interface redundantly re-declares
className and children which are already provided by
ComponentPropsWithoutRef<'button'>; remove the explicit className?: string and
children?: React.ReactNode declarations from the ShimmerButtonProps (or
equivalent interface) and rely on extending ComponentPropsWithoutRef<'button'>
so that the ShimmerButton component's props come only from that extension plus
any truly custom props.

In `@apps/web/components/magicui/text-reveal.tsx`:
- Around line 8-12: The TextReveal implementation is dropping all div props from
TextRevealProps (which extends ComponentPropsWithoutRef<'div'>); update the
TextReveal function signature to accept the remaining props (e.g., add a rest
param like ...rest alongside className) and spread those onto the root div
element so id, style, data-*, ARIA attributes, etc. are preserved; apply the
same change to the other TextReveal occurrence mentioned so both
TextRevealProps/TextReveal usages forward all div props to the rendered element.
- Around line 57-63: The Word component's wrapper uses an invalid Tailwind class
"xl:lg-3" and the shadow copy span can be announced by screen readers; update
the wrapper className in Word (currently "xl:lg-3 relative mx-1 lg:mx-1.5") to a
valid spacing utility such as "relative mx-1 lg:mx-1.5 xl:mx-3" (or whichever
correct xl spacing you intend) and add aria-hidden="true" to the absolute shadow
span (the element rendering children before the motion.span) to hide the
duplicate content from assistive technologies.

In `@apps/web/components/Navbar.tsx`:
- Around line 139-140: The dropdown panel in Navbar.tsx is absolutely positioned
and uses the class mt-1 which creates a pointer gap under the Docs trigger;
remove the mt-1 from the panel div (the element with classes "invisible absolute
left-1/2 z-50 ... group-hover:visible") so the panel sits flush with the
trigger; if visual separation is still needed, replace mt-1 with a non-layout
transformation such as a small translateY (e.g., translate-y-0.5) or adjust
top/full positioning rather than using margin to avoid the dead zone.

In `@apps/web/components/ui/accordion.tsx`:
- Around line 46-48: Add missing CSS keyframes and utility classes for the
accordion animations referenced on AccordionPrimitive.Content
(animate-accordion-down and animate-accordion-up): update your globals.css to
define `@keyframes` accordion-down and accordion-up that animate height from 0 to
var(--radix-accordion-content-height) and vice versa, and add utility classes
(or Tailwind plugin utilities) animate-accordion-down and animate-accordion-up
that set animation: accordion-down 0.2s ease-out and animation: accordion-up
0.2s ease-out respectively so the data-[state=open]/[state=closed] classes on
AccordionPrimitive.Content work correctly.

In `@apps/web/components/ui/button.tsx`:
- Around line 31-35: The Button component currently inherits HTML's default
submit behavior; update the Button forwardRef signature to set a default type of
"button" (e.g., destructure type = "button" from props) and ensure that when
rendering the fallback 'button' element (Comp when asChild is false) the type
prop is passed through, while preserving asChild behavior (Slot should continue
to forward whatever type the child provides). Modify the Button component
(symbols: Button, asChild, Comp, buttonVariants, cn) so callers get
type="button" by default without changing existing Slot-as-child semantics.

In `@apps/web/components/ui/card.tsx`:
- Around line 22-35: CardTitle and CardDescription currently render as divs
which removes heading/paragraph semantics; update CardTitle to render a heading
element (e.g., h3 or appropriate level) and CardDescription to render a
paragraph (p), update their forwardRef generic types to HTMLHeadingElement and
HTMLParagraphElement respectively, keep the same className merging via cn and
spread {...props}, and preserve displayName values (CardTitle, CardDescription)
so consumers gain proper document structure and improved accessibility.

In `@docs/plans/2026-03-12-website-redesign-design.md`:
- Around line 109-112: Update the JetBrains Mono package name used in the
dependencies list: replace the string '@fontsource/jetbrains-mono' with the
variable-font package '@fontsource-variable/jetbrains-mono' so it matches the
rest of the repo (package.json, lockfiles, and imports); locate the occurrence
in the document where the bullet list contains '@fontsource/jetbrains-mono' and
change it to '@fontsource-variable/jetbrains-mono'.
- Around line 116-130: The fenced file-tree block in the document triggers
markdownlint MD040 because it lacks a language; update the triple-backtick fence
for the tree (the block starting with "apps/web/") to use a plain-text language
tag by changing ``` to ```text so the code fence is labeled and the file passes
MD040 while preserving the exact tree contents.

In `@docs/plans/2026-03-12-website-redesign-implementation.md`:
- Around line 438-452: The unlabeled fenced code block containing the
"Structure:" diagram (with symbols like DotPattern, AnimatedShinyText, h1, CTAs
row, Trust badges row, Editor screenshot) is missing a language tag and triggers
markdownlint MD040; add a language identifier (for example ```text or ```md) to
the opening fence so the block is labeled, keeping the rest of the block
unchanged.
- Around line 816-835: Expand the visual checklist to include accessibility and
interaction checks for the new components: test keyboard navigation and proper
tab order for the Sheet-based mobile nav (open/close via Enter/Space, focus trap
while open, focus return to trigger, and Escape closes), verify Radix Accordion
items (toggle via Enter/Space, aria-expanded states and focus-visible styles),
assert motion controls for ShimmerButton, BorderBeam, NumberTicker,
AnimatedShinyText and TextReveal respect prefers-reduced-motion and provide
non-animated fallbacks, ensure Marquee and DotPattern are dismissible/pausable
and not focus-trapping, and confirm Fumadocs and other pages expose correct ARIA
labels/roles and visible focus outlines for interactive elements.
- Around line 65-80: Before vendoring Magic UI components, add provenance and
MIT license attribution: record the upstream Magic UI version/commit/URL and
include the MIT copyright header in each new component file (e.g.,
animated-shiny-text.tsx, border-beam.tsx, dot-pattern.tsx, marquee.tsx,
number-ticker.tsx, shimmer-button.tsx, text-reveal.tsx,
animated-grid-pattern.tsx) and create a top-level LICENSE or NOTICE file
documenting the upstream source and license; ensure the original copyright and
license text is preserved in component headers and the LICENSE/NOTICE, and keep
the adapted imports (framer-motion and cn()/@/lib/utils) but do not remove or
alter the required attribution text.
- Around line 25-29: The font packages `@fontsource/inter` and
`@fontsource-variable/jetbrains-mono` are imported from app/layout.tsx and must be
installed as runtime dependencies; replace the dev-only install (pnpm add -D
`@fontsource/inter` `@fontsource-variable/jetbrains-mono`) with regular installs
(pnpm add ...) so they are present in production builds, and verify
app/layout.tsx imports still reference those package names.

---

Outside diff comments:
In `@apps/web/components/FaqAccordion.tsx`:
- Around line 108-113: The search input in the FaqAccordion component lacks an
accessible name; update the <input> (the one using value={search} and
onChange={e => setSearch(e.target.value)}) to include an accessible label—either
add a visible <label> associated via htmlFor/id or add an aria-label (e.g.,
aria-label="Search FAQs") so screen readers always expose the control purpose;
ensure the id on the input matches the label if you choose a visible label.