<!-- source-hash: 862fd90b3a9c67e41d15d6c3cc9b05fe -->
The main barrel export file for the `@flamingo/ui-kit` package, re-exporting all public components, hooks, utilities, and types from their respective submodules into a single entry point.

## Key Components

**Component Exports**
- `./components/ui` — Base UI primitives
- `./components/features` — Feature-specific components
- `./components/icons` — Icon set
- `./components/navigation` — Navigation components
- `./components/platform` — Platform-level components
- `./components/chat` — Chat components and payload types
- `./components/shared/onboarding` — Onboarding flow components

**Named Component Exports**
- `LogsList` — Renders a list of log entries
- `LogSeverityDot` — Visual indicator for log severity levels
- `ToolIcon` — Icon component for tool representations

**Non-Component Exports**
- `./hooks` — Shared React hooks
- `./utils` — Utility functions
- `./types` — CMS domain types (canonical source)
- `./types/logs.types` — Log-specific type definitions
- `./assets` — Static assets

**Disambiguation Block**

Explicit `export type` re-exports for CMS domain types that would otherwise be silently dropped by TypeScript (`TS2308`) due to naming conflicts with identically-named types in `./components/chat`. The following are explicitly resolved to their `./types` (CMS) origin:

`BlogAuthor`, `BlogCategory`, `BlogPost`, `BlogPostSummary`, `CaseStudy`, `CustomerInterview`, and related filter/response/config shapes.

## Usage Example

```typescript
// Consuming the full kit from the barrel
import {
  LogsList,
  LogSeverityDot,
  ToolIcon,
  type BlogPost,
  type CaseStudy,
  type CustomerInterview,
} from '@flamingo/ui-kit'

// Chat subpath still exposes its own payload variants
import type { BlogPost as ChatBlogPost } from '@flamingo/ui-kit/components/chat'
```

> **Note:** If you need the chat-specific payload variants of `BlogPost`, `CaseStudy`, etc., import them directly from the `@flamingo/ui-kit/components/chat` subpath rather than the root barrel to avoid ambiguity.