feat/discovery

text-brand-electric-violet utility class is not defined — Hazlo-ahora link will render colorless

apps/platform/src/components/discovery/GuidedTour.tsx:258

The diff introduces `text-brand-electric-violet` on the "Hazlo ahora" button. Checked packages/ui/src/styles/components.css — only `.bg-brand-electric-violet`, `.text-brand-heliotrope`, and `.bg-brand-heliotrope` are defined; `.text-brand-electric-violet` is absent. TailwindCSS v4 silently skips unknown utilities, so the link renders with no color (inherits default text color instead of the intended accent). Fix: add `.text-brand-electric-violet { color: hsl(var(--brand-electric-violet)); }` in components.css alongside its `bg-` sibling, or switch to `text-brand-heliotrope` which is already defined.

Anterior uses bare <button> while Siguiente uses <Button> — inconsistent focus ring and theme contract

apps/platform/src/components/discovery/GuidedTour.tsx:285

The previous-step control is a hand-rolled `<button>` with manual `h-8 rounded-md px-2.5` classes and no explicit `focus-visible` ring. The old code used `<Button size="sm" variant="cancel">` which carries the design system's shared focus ring, disabled styling, and size contract. Using the system `<Button size="sm" variant="ghost">` (or the `cancel` variant) would keep keyboard focus styling consistent between Anterior and Siguiente, and propagate future theme changes automatically.

Progress dots aria-label is a bare fraction with no semantic context

apps/platform/src/components/discovery/GuidedTour.tsx:268

The dots container has `aria-label={\`${stepIdx + 1}/${total}\`}` which announces as "2/5" — no indication this is tour progress. Additionally, the `<span>` dots are decorative but lack `aria-hidden="true"`, so screen readers may enumerate them as unlabelled elements. Fix: use a localized label (`Paso {n} de {total}` — add i18n key) and add `aria-hidden="true"` to every dot `<span>`.

Past-step dot opacity (bg-muted-foreground/50) likely fails WCAG 1.4.11 non-text contrast at 6px

apps/platform/src/components/discovery/GuidedTour.tsx:274

Past-step dots use `bg-muted-foreground/50` (50% opacity) at `h-1.5 w-1.5` (6×6 px). At this size and opacity the contrast ratio against a white card background likely falls below the 3:1 minimum for non-text UI components (WCAG 1.4.11). Bump to `bg-muted-foreground` (full opacity) to preserve the three-state encoding without relying on opacity for differentiation.

ArrowRight icon in Hazlo-ahora link won't flip in RTL locales

apps/platform/src/components/discovery/GuidedTour.tsx:261

The `<ArrowRight>` icon always points right. If the platform is ever used in an RTL context the icon direction should mirror. Low risk today but a known trap for icon-decorated CTA links. Add `rtl:rotate-180` to the icon's className or use a directional icon utility when RTL is first supported.

Navigation row lacks a group landmark — AT users can't jump directly to tour controls

apps/platform/src/components/discovery/GuidedTour.tsx:267

The footer `<div>` containing progress dots + Anterior/Siguiente has no landmark or group role. Adding `role="group" aria-label="Navegación del tour"` (or an i18n key) lets screen reader users jump directly to the navigation controls without tabbing through the card body.

Dot key={i} is index-based — fragile if steps become dynamic

apps/platform/src/components/discovery/GuidedTour.tsx:271

Safe with the current static `Array.from({ length: total })` shape. If steps are ever made conditional or reordered, React will reuse wrong DOM nodes and `transition-all` will animate incorrectly. Worth keying on step index or step ID if the catalog drives this in future.