@flamingo-stack/openframe-frontend-core 0.0.213 → 0.0.214

package/src/types/.blog.md

@@ -1,41 +1,65 @@
-<!-- source-hash: 2e7702b67a6483fc1681bf381b96a9f8 -->
-Comprehensive TypeScript definitions for the Flamingo blog system, including database models, API interfaces, and SEO analytics for multi-platform content management.
+<!-- source-hash: 8148802670f3c4122204649c0bccdbcd -->
+Type definitions for the Flamingo blog system, covering database models, form data, query options, SEO analysis, and filtering structures used across the blog feature.
 
 ## Key Components
 
-- **Core Models**: `BlogPost`, `BlogCategory`, `BlogTag` - Main database entities with normalized relationships
-- **Platform Integration**: `BlogPostPlatform` - Links posts to different platforms with featured content support
-- **Media Management**: `BlogMediaAsset` - File uploads, storage paths, and metadata
-- **SEO Features**: `BlogSEOAnalytics`, `SEOAnalysisResult` - Content optimization and scoring
-- **Form Data**: `CreateBlogPostData`, `UpdateBlogPostData` - Structured input validation
-- **Query Options**: `GetBlogPostsOptions`, `BlogSearchParams` - Flexible content filtering
-- **Pagination**: `BlogPagination`, `BlogPostSummary` - Optimized list views
-- **Dashboard**: `BlogPostStats` - Analytics and performance metrics
+| Export | Type | Description |
+|--------|------|-------------|
+| `BlogPost` | Interface | Core database model with SEO fields, relationships, and raw API response structure |
+| `BlogStatus` | Union Type | Post lifecycle states: `draft`, `ai_drafted`, `published`, `ai_published`, `scheduled`, `archived` |
+| `Platform` | Type | String alias for platform identifiers (fetched dynamically from DB) |
+| `CreateBlogPostData` | Interface | Payload shape for creating new posts including platforms, categories, and tags |
+| `UpdateBlogPostData` | Interface | Partial update payload for existing posts |
+| `GetBlogPostsOptions` | Interface | Query filters including pagination, sorting, platform, and search |
+| `BlogPostStats` | Interface | Dashboard aggregates with per-platform post counts |
+| `SEOAnalysisResult` | Interface | Scored SEO breakdown with keyword density, suggestions, errors, and warnings |
+| `BlogPagination` | Interface | Paginated response wrapping `BlogPostSummary` records |
+| `BlogPostSummary` | Interface | Lightweight post projection for listing pages |
+| `BlogFilters` | Interface | Filter options (categories + tags) for sidebar filtering UI |
 
 ## Usage Example
 
 ```typescript
-import { BlogPost, CreateBlogPostData, GetBlogPostsOptions } from './blog';
+import type {
+  BlogPost,
+  CreateBlogPostData,
+  GetBlogPostsOptions,
+  SEOAnalysisResult
+} from './blog'
 
-// Create a new blog post
+// Fetch options with filtering and pagination
+const options: GetBlogPostsOptions = {
+  platform: 'flamingo',
+  status: 'published',
+  page: 1,
+  pageSize: 10,
+  sortBy: 'published_at',
+  sortOrder: 'desc',
+  search: 'automation'
+}
+
+// Create post payload
 const newPost: CreateBlogPostData = {
-  title: "OpenFrame AI Platform Overview",
-  slug: "openframe-ai-platform-overview",
-  content: "Comprehensive guide to OpenFrame...",
-  author_id: "user123",
-  status: "published",
-  platforms: ["flamingo", "docs"],
+  title: 'Getting Started with OpenFrame',
+  slug: 'getting-started-openframe',
+  content: '...',
+  author_id: 'user-123',
+  status: 'draft',
+  platforms: ['flamingo', 'openframe'],
   categories: [1, 3],
-  tags: [5, 8, 12]
-};
+  tags: [5]
+}
 
-// Query published posts with filtering
-const queryOptions: GetBlogPostsOptions = {
-  platform: "flamingo",
-  status: "published",
-  page: 1,
-  pageSize: 10,
-  sortBy: "published_at",
-  sortOrder: "desc"
-};
+// SEO result from analysis service
+const seo: SEOAnalysisResult = {
+  overall_score: 82,
+  title_score: 90,
+  meta_description_score: 75,
+  content_score: 85,
+  readability_score: 78,
+  keyword_density: { 'openframe': 0.03 },
+  suggestions: ['Add more internal links'],
+  errors: [],
+  warnings: ['Meta description slightly short']
+}
 ```

package/src/types/.case-study.md

@@ -1,38 +1,55 @@
-<!-- source-hash: d35b9646a09424ac4cacd696dd9b620a -->
-This TypeScript file defines the type structure for a case study system that showcases MSP (Managed Service Provider) success stories and customer testimonials.
+<!-- source-hash: 347abba356d14a3c4bf7cf70892add4e -->
+Defines TypeScript interfaces and types for the Case Study content entity within the Flamingo/OpenMSP platform, following the same structural pattern as `blog.ts`.
 
 ## Key Components
 
-- **`CaseStudy`** - Main interface defining the complete case study structure with story sections (challenge/solution/results), SEO fields, and relationships to users, MSPs, platforms, and tags
-- **`CreateCaseStudyData`** - Input interface for creating new case studies with required fields and platform/tag associations
-- **`UpdateCaseStudyData`** - Partial type for updating existing case studies
-- **`CaseStudyFilters`** - Query parameters for filtering and searching case studies by platform, industry, company size, etc.
-- **`CaseStudyListResponse`** - API response wrapper containing paginated case study data
+| Export | Type | Description |
+|--------|------|-------------|
+| `CaseStudy` | `interface` | Full case study record with all fields, relations, and metadata |
+| `CreateCaseStudyData` | `interface` | Payload shape for creating a new case study |
+| `UpdateCaseStudyData` | `type` | Partial version of `CreateCaseStudyData` for updates |
+| `CaseStudyFilters` | `interface` | Query filter options for listing/searching case studies |
+| `CaseStudyListResponse` | `interface` | Paginated response wrapper for case study arrays |
 
 ## Usage Example
 
 ```typescript
-// Creating a new case study
-const newCaseStudy: CreateCaseStudyData = {
-  title: "How TechCorp Reduced Downtime by 90%",
-  slug: "techcorp-reduced-downtime",
-  summary: "A comprehensive case study on infrastructure optimization",
-  user_id: "uuid-of-msp-user",
-  challenge: "Frequent system outages affecting productivity",
-  solution: "Implemented redundant systems and monitoring",
-  results: "90% reduction in downtime, $50k annual savings",
-  status: "published",
-  author_id: "author-uuid",
-  platforms: ["platform-uuid-1", "platform-uuid-2"],
-  tags: [1, 3, 7]
+import type {
+  CaseStudy,
+  CreateCaseStudyData,
+  CaseStudyFilters,
+  CaseStudyListResponse
+} from './case-study'
+
+// Create a new case study
+const payload: CreateCaseStudyData = {
+  title: 'How Acme IT Reduced Ticket Volume by 40%',
+  slug: 'acme-it-ticket-reduction',
+  status: 'draft',
+  author_id: 'uuid-author',
+  platforms: ['uuid-platform-1'],
+  tags: [1, 2],
+  challenge: 'High volume of repetitive L1 tickets...',
+  solution: 'Deployed Mingo AI with automated triage...',
+  results: '40% reduction in ticket volume in 30 days.',
+  testimonial_video_url: 'https://www.youtube.com/watch?v=EXAMPLE',
 }
 
-// Filtering case studies
+// Filter published case studies by industry
 const filters: CaseStudyFilters = {
-  platform: "microsoft-365",
-  industry: "healthcare",
-  company_size: "50-200",
-  featured: true,
-  limit: 10
+  industry: 'healthcare',
+  status: 'published',
+  limit: 10,
+  offset: 0,
 }
-```
+
+// Typed paginated response
+const response: CaseStudyListResponse = await fetchCaseStudies(filters)
+console.log(response.count, response.data)
+```
+
+## Notes
+
+- **Video fields**: `testimonial_video_url` (YouTube, preferred) and `main_video_url` (uploaded fallback) follow the same `ENTITY_FIELD_CONFIG` convention used across `customer_interviews`, `webinars`, `podcasts`, and `investor_updates`.
+- **MSP relation**: Company, industry, and testimonial data are resolved indirectly via `user.msp_id`, not stored directly on the case study.
+- `video_source_type` is deprecated — consumers should detect source from URL presence instead.

package/src/types/.customer-interview.md

@@ -1,52 +1,74 @@
-<!-- source-hash: 81676ec584ead4c16c897cb47ac18263 -->
-Customer interview management types for video testimonials and case studies, including AI-powered processing capabilities for transcription, summarization, and video clip extraction.
+<!-- source-hash: 110781f95cc87ef6269255e1ff54d089 -->
+Brief description: Defines TypeScript types and interfaces for the Customer Interview content module, covering the full lifecycle from creation and AI processing to publishing and analytics within the Flamingo/OpenFrame platform.
 
 ## Key Components
 
-### Core Interfaces
-- **`CustomerInterview`** - Main entity with video content, AI processing status, and SEO metadata
-- **`VideoTeaser`** - Short promotional video clips with thumbnail and visibility controls
-- **`VideoClip`** - AI-generated video segments with confidence scoring and timestamps
-- **`Speaker`** - Identified speakers in video transcripts with confidence levels
-
-### Data Management
-- **`CreateCustomerInterviewData`** - Required fields for creating new interviews
-- **`UpdateCustomerInterviewData`** - Partial update interface for modifications
-- **`CustomerInterviewFilters`** - Query filtering by platform, industry, status, and search terms
-
-### AI Processing
-The interface tracks AI processing states for:
-- Transcript generation (AssemblyAI integration)
-- Summary extraction with bullet points and gist
-- Video clip identification (TwelveLabs integration)
-- Speaker identification with confidence scoring
+| Export | Type | Description |
+|--------|------|-------------|
+| `CustomerInterview` | Interface | Core entity representing a recorded customer interview with all fields including video, AI processing state, SEO, and relations |
+| `CustomerInterviewConfig` | Interface | Per-interview configuration options (highlight video duration, subtitle burning) |
+| `CreateCustomerInterviewData` | Interface | Input shape for creating a new interview record |
+| `UpdateCustomerInterviewData` | Type alias | Partial version of `CreateCustomerInterviewData` for patch updates |
+| `CustomerInterviewFilters` | Interface | Query filter options for listing interviews (platform, industry, search, pagination) |
+| `CustomerInterviewListResponse` | Interface | Paginated response wrapper for interview list queries |
+| Re-exports | Types | `VideoTeaser`, `Speaker`, `VideoClip`, `TranscriptWord`, `SpeakerMapping`, `ExcludedRange` from `./video-processing` for backwards compatibility |
 
 ## Usage Example
 
 ```typescript
-// Create a new customer interview
-const newInterview: CreateCustomerInterviewData = {
-  title: "MSP Success Story: 50% Cost Reduction",
-  slug: "msp-cost-reduction-story",
-  summary: "How **TechFlow MSP** reduced operational costs by 50% using OpenFrame",
-  user_id: "customer-uuid",
-  main_video_url: "https://videos.example.com/interview.mp4",
-  status: "draft",
-  author_id: "author-uuid",
-  platforms: ["azure", "aws"],
-  teasers: [{
-    url: "https://videos.example.com/teaser.mp4",
-    title: "Quick Preview",
-    published: true,
-    source: "manual"
-  }]
-};
-
-// Filter interviews by platform and status
+import type {
+  CustomerInterview,
+  CreateCustomerInterviewData,
+  CustomerInterviewFilters,
+  CustomerInterviewListResponse
+} from './customer-interview'
+
+// Creating a new interview
+const payload: CreateCustomerInterviewData = {
+  title: 'How Acme IT Scaled Support with Flamingo',
+  slug: 'acme-it-flamingo-interview',
+  status: 'draft',
+  author_id: 'user-uuid-123',
+  platforms: ['platform-uuid-abc'],
+  user_id: 'customer-uuid-456',
+  main_video_url: 'https://cdn.example.com/interviews/acme.mp4',
+  config: {
+    highlight_target_duration_seconds: 120,
+    skipSubtitleBurning: false
+  },
+  custom_instructions: 'Focus on ROI and ticket volume reduction metrics.'
+}
+
+// Filtering interviews for a listing page
 const filters: CustomerInterviewFilters = {
-  platform: "azure",
-  status: "completed",
-  featured: true,
-  limit: 10
-};
-```
+  platform: 'all',
+  status: 'completed',
+  search: 'managed services',
+  limit: 12,
+  offset: 0
+}
+
+// Consuming a list response
+async function fetchInterviews(
+  filters: CustomerInterviewFilters
+): Promise<CustomerInterviewListResponse> {
+  const response = await api.get('/interviews', { params: filters })
+  return response.data
+}
+
+// Checking AI processing state
+function isReadyToPublish(interview: CustomerInterview): boolean {
+  return (
+    interview.ai_transcript_status === 'completed' &&
+    interview.ai_summary_status === 'completed' &&
+    interview.status === 'draft'
+  )
+}
+```
+
+## Notes
+
+- AI processing fields (`ai_transcript_status`, `ai_summary_status`, `ai_clips_status`) follow a `pending → processing → completed | failed` lifecycle driven by **AssemblyAI** (transcription) and **TwelveLabs** (video understanding).
+- `speaker_mapping` maps AssemblyAI speaker labels (e.g. `"A"`, `"B"`) to real `UserProfile` identities resolved during transcription.
+- `incentive_excluded_ranges` stores timestamp ranges where promotional/incentive language was detected and should be excluded from highlight clip generation.
+- Relations (`user`, `msp`, `author`, `case_study`, `platforms`) are populated only when explicitly joined — treat them as optional at the call site.

package/src/types/.delivery.md

@@ -0,0 +1,40 @@
+<!-- source-hash: e2c52b22632b1213075a4266559e9a2b -->
+Shared wire types for the Delivery (ClickUp bug-fixes & enhancements) surface, used by both the hub's `/api/delivery*` routes and the lib's `DeliveryTable`/`DeliveryLists`/`DeliverySection` components.
+
+## Key Components
+
+| Export | Type | Description |
+|--------|------|-------------|
+| `DeliveryItem` | `interface` | Canonical shape for a single ClickUp task (bug or enhancement) |
+| `DeliveryResponse` | `interface` | API response envelope splitting items into `completed` and `inProgress` buckets |
+| `TASK_TYPE_LABELS` | `const` | Maps ClickUp task types to display badge labels (`Request` → `ENHANCEMENT`, `Bug` → `BUG-FIX`) |
+| `TASK_TYPE_TEXT_COLORS` | `const` | Maps task types to ODS CSS token classes (attention-red for bugs) |
+
+### `DeliveryItem` Notable Fields
+
+| Field | Type | Notes |
+|-------|------|-------|
+| `customItemId` | `number \| null` | ClickUp `custom_item_id` used to render a `TaskTypeIcon` instead of initials fallback |
+| `listNames` | `string[]` | All ClickUp lists the task belongs to; falls back to a single-element array |
+| `dateClosed` | `number \| null` | Unix timestamp; `null` when task is still open |
+
+## Usage Example
+
+```typescript
+import {
+  DeliveryItem,
+  DeliveryResponse,
+  TASK_TYPE_LABELS,
+  TASK_TYPE_TEXT_COLORS,
+} from '@your-lib/types/delivery';
+
+// Consuming an API response
+const response: DeliveryResponse = await fetch('/api/delivery').then(r => r.json());
+
+// Rendering a badge label and color
+function getTaskBadge(item: DeliveryItem) {
+  const label = TASK_TYPE_LABELS[item.taskType as keyof typeof TASK_TYPE_LABELS] ?? item.taskType;
+  const color = TASK_TYPE_TEXT_COLORS[item.taskType as keyof typeof TASK_TYPE_TEXT_COLORS] ?? '';
+  return { label, color };
+}
+```

package/src/types/.employee.md

@@ -1,42 +1,36 @@
-<!-- source-hash: cd29c21e14e07013c1811844b35e272d -->
-Defines TypeScript interfaces for employee data structures used throughout the Flamingo MSP platform, providing type safety for employee management and profile operations.
+<!-- source-hash: c1dd04b1f059ffd424cb55cea9d504ed -->
+Defines TypeScript interfaces for employee data structures used across the Flamingo platform for managing and displaying employee information.
 
 ## Key Components
 
-- **`Employee`** - Complete employee record interface with all fields including ID, personal info, and organizational data
-- **`EmployeeResponse`** - API response wrapper for employee data operations with success status and employee array
-- **`EmployeeProfileData`** - Subset of employee data used specifically for profile operations, excluding the ID field
+| Interface | Description |
+|-----------|-------------|
+| `Employee` | Full employee record including identity, role, and optional location |
+| `EmployeeResponse` | API response wrapper containing a success flag and array of `Employee` records |
+| `EmployeeProfileData` | Slim profile subset used for display contexts (excludes `id`, `about`, `location_country`) |
 
 ## Usage Example
 
 ```typescript
 import { Employee, EmployeeResponse, EmployeeProfileData } from './employee';
 
-// Creating a new employee record
-const newEmployee: Employee = {
-  id: "emp-123",
-  full_name: "John Doe",
-  department: "IT Support",
-  avatar_url: "https://example.com/avatar.jpg",
-  role: "technician",
-  job_title: "Senior Support Engineer",
-  about: "Experienced IT professional specializing in network infrastructure"
-};
-
-// Handling API response
-const apiResponse: EmployeeResponse = {
-  success: true,
-  data: [newEmployee]
-};
-
-// Profile update data
-const profileUpdate: EmployeeProfileData = {
-  full_name: "John Smith",
-  department: "IT Support",
-  avatar_url: "https://example.com/new-avatar.jpg",
-  role: "senior_technician",
-  job_title: "Lead Support Engineer"
+// Typing an API response
+const response: EmployeeResponse = await fetchEmployees();
+if (response.success) {
+  const employees: Employee[] = response.data;
+}
+
+// Using the profile subset for UI display
+const profile: EmployeeProfileData = {
+  full_name: 'Jane Doe',
+  department: 'Engineering',
+  avatar_url: 'https://cdn.example.com/avatars/jane.png',
+  role: 'admin',
+  job_title: 'Senior Engineer',
 };
 ```
 
-These interfaces ensure consistent employee data handling across the OpenFrame platform, supporting both individual employee operations and bulk data management through the unified MSP interface.
+## Notes
+
+- `location_country` is the only optional field on `Employee` — all other fields are required.
+- `EmployeeProfileData` is a strict subset of `Employee`, suitable for profile cards or directory listings where sensitive/verbose fields (`about`, `id`) are not needed.

package/src/types/.index.md

@@ -1,55 +1,41 @@
-<!-- source-hash: d207a06dcc5db890a52ec10da489179b -->
-Centralized type definition index that provides a single import point for all TypeScript types used across the Flamingo UI Kit platform, including core platform, authentication, content, user management, and business logic types.
+<!-- source-hash: 2dec9acc6154e0160c391613c83b192e -->
+Centralized barrel export file for all type definitions in the `@flamingo/ui-kit` package, providing a single import entry point for platform, application, and domain types.
 
 ## Key Components
 
-**Core Platform Types**
-- `announcement` - System announcement and notification types
-- `categories`, `category` - Content categorization and filtering types
-- `media` - Media asset and file handling types
-- `platform` - Platform configuration, stats, and filtering types including `LegacyPlatform`, `PlatformFilter`, `PlatformName`, `PlatformOption`, `PlatformRecord`, `PlatformSettings`, and `PlatformStats`
-
-**Data & Authentication**
-- `supabase` - Database schema and query types
-- `auth` - Authentication and authorization types
-- `profile`, `user`, `employee`, `team` - User management and organizational types
-
-**Content Management**
-- `blog`, `case-study`, `customer-interview`, `product-release` - Content type definitions
-- `vendor`, `vendor-links` - Vendor and integration types
-- `faq`, `report`, `stack` - Documentation and reporting types
-
-**System Integration**
-- `slack`, `luma` - Third-party service integration types
-- `tool.types`, `shell.types`, `os.types` - System and tooling types
-- `navigation` - UI navigation and routing types
-- `marketing`, `waitlist` - Marketing and lead generation types
+| Export Group | Modules |
+|---|---|
+| **Core Platform** | `announcement`, `categories`, `category`, `media`, `platform` |
+| **Database & API** | `supabase` |
+| **Authentication** | `auth` |
+| **Content** | `blog`, `case-study`, `customer-interview`, `luma`, `product-release`, `delivery`, `vendor`, `video-processing` |
+| **User & Profile** | `employee`, `profile`, `team`, `user` |
+| **Communication** | `slack`, `waitlist` |
+| **Business Logic** | `faq`, `report`, `stack` |
+| **Navigation** | `navigation` |
+| **Tools & Shell** | `tool.types`, `shell.types`, `os.types` |
+| **Marketing & Access** | `marketing`, `access-code-cohorts`, `icons`, `permissions`, `tmcg` |
+
+> **Note:** `platform` uses named re-exports (`export type { ... }`) to avoid conflicts with internal types, exposing only `LegacyPlatform`, `PlatformFilter`, `PlatformName`, `PlatformOption`, `PlatformRecord`, `PlatformSettings`, and `PlatformStats`.
 
 ## Usage Example
 
 ```typescript
-import { 
-  PlatformName, 
-  PlatformStats, 
-  CategoryCardProps,
+// Import any type directly from the package root
+import type {
+  PlatformSettings,
+  Category,
+  BlogPost,
   UserProfile,
-  BlogPost 
-} from '@flamingo/ui-kit/types'
-
-// Use platform types
-const platformConfig: PlatformName = 'openframe'
-const stats: PlatformStats = { users: 1000, tools: 50 }
-
-// Use content types
-const category: CategoryCardProps = {
-  name: 'MSP Tools',
-  description: 'Essential MSP platform tools'
-}
-
-// Use combined types across modules
-interface DashboardProps {
-  platform: PlatformName
-  user: UserProfile
-  featuredContent: BlogPost[]
-}
-```
+  NavigationItem,
+} from '@flamingo/ui-kit'
+
+// No need to reach into individual type files
+const config: PlatformSettings = { /* ... */ }
+const nav: NavigationItem[] = []
+```
+
+## Notes
+
+- Prefer importing from `@flamingo/ui-kit` directly rather than deep-importing individual type modules (e.g., `@flamingo/ui-kit/types/platform`).
+- `categories` also uses named exports to selectively expose `Category`, `CategoryCardProps`, and `RealCategoryCardProps`.

package/src/types/.marketing.md

@@ -1,60 +1,65 @@
-<!-- source-hash: e41f588f9afa7a96c3aef555124474a5 -->
-Defines comprehensive TypeScript interfaces for Flamingo's Marketing AI system, covering campaign management, AI-generated content, social media automation, and usage tracking across various platforms and providers.
+<!-- source-hash: f0baaf40642c975086a4698fa70728a9 -->
+Brief description: Defines all TypeScript interfaces, types, and enums for the Flamingo Marketing AI system, covering campaigns, AI-generated content, media assets, social accounts, scheduled posts, approvals, and usage tracking.
 
 ## Key Components
 
-**Core Campaign Types**
-- `MarketingCampaign` - Main campaign entity with content source configuration
-- `CreateCampaignInput`/`UpdateCampaignInput` - Campaign CRUD operations
-- Support for various content sources (product releases, blog posts, case studies)
+### Campaign Types
+- **`MarketingCampaign`** — Core campaign entity with content seed fields (`content_source_type`, `content_source_id`, `custom_instructions`)
+- **`CreateCampaignInput`** / **`UpdateCampaignInput`** — Input shapes for campaign mutations
 
-**AI Content Management**
-- `AIContent` - AI-generated content with approval workflow
-- Content types: blog posts, social posts, ad copy, email
-- Publishing controls with URL injection preferences and override capabilities
+### Content Types
+- **`ContentType`** — `'blog_post' | 'social_post' | 'ad_copy' | 'email'`
+- **`ContentStatus`** — Lifecycle states from `'draft'` through `'published'`
+- **`AIContent`** — Generated text content with publishing, override, and URL injection fields
+- **`CreateAIContentInput`** — Input for creating AI-generated content records
 
-**AI Media Generation**
-- `AIMedia` - Generated media assets (images, videos, Figma exports)
-- Multiple providers: DALL-E, Midjourney, Flux, Stable Diffusion, video models
-- Comprehensive metadata tracking including costs and dimensions
+### Media Types
+- **`MediaType`** — `'image' | 'video' | 'figma_export'`
+- **`MediaProvider`** — Supported AI providers: `dalle`, `flux-pro`, `kling-v2.5`, `luma-ray2`, and more
+- **`AIMedia`** — Media asset entity including storage paths, dimensions, Figma integration, and publish overrides
+- **`MediaDimensions`** — Width, height, and aspect ratio descriptor
 
-**Social Integration**
-- `SocialAccount` - Multi-platform social media account management
-- `ScheduledPost` - Automated post scheduling with status tracking
-- Support for Slack, LinkedIn, Facebook, Instagram, Twitter, YouTube
+### Social & Scheduling Types
+- **`SocialChannel`** — `'slack' | 'linkedin' | 'facebook' | 'instagram' | 'twitter' | 'youtube'`
+- **`SocialAccount`** / **`CreateSocialAccountInput`** — OAuth account records with encrypted tokens
+- **`ScheduledPost`** / **`CreateScheduledPostInput`** — Post scheduling with retry tracking
 
-**Workflow Management**
-- `ContentApproval` - Content review and approval system
-- `AIUsage` - Cost and token tracking across AI services
-- Campaign statistics and performance metrics
+### Approval & Usage Types
+- **`ContentApproval`** — Approval workflow for content, media, and campaigns
+- **`AIUsage`** / **`TrackAIUsageInput`** — Cost and token tracking per AI service and operation
+- **`AIService`** — `'anthropic' | 'openai' | 'replicate' | 'figma' | 'google'`
+
+### Aggregate & Source Types
+- **`CampaignWithDetails`** — Campaign bundled with its content and media arrays
+- **`CampaignStats`** / **`AIUsageSummary`** — Dashboard-level rollup statistics
+- **`ContentSourceType`** — Union of 11 seed content origins (`product_release`, `blog_post_seed`, `event`, `podcast`, etc.)
+- **`URLInjectionPreference`** — `'none' | 'in_post' | 'as_comment'`
 
 ## Usage Example
 
 ```typescript
-// Create a new campaign with blog post seed
-const campaign: CreateCampaignInput = {
-  name: "Product Launch Campaign",
-  description: "Launch our new AI features",
-  content_source_type: "blog_post",
-  content_source_id: 123,
-  future_blog_social_account_id: 456,
-  goals: ["increase awareness", "drive signups"]
-};
+import type {
+  CreateCampaignInput,
+  AIContent,
+  ContentType,
+  URLInjectionPreference,
+} from './marketing';
 
-// Generate AI content for the campaign
-const content: CreateAIContentInput = {
-  campaign_id: campaign.id,
-  content_type: "social_post",
-  content: "Exciting new AI features are here! 🚀",
-  ai_model: "gpt-4",
-  url_injection_preference: "in_post"
+// Create a campaign seeded from a product release
+const newCampaign: CreateCampaignInput = {
+  name: 'Q3 Product Launch',
+  content_source_type: 'product_release',
+  content_source_id: 42,
+  custom_instructions: 'Emphasize enterprise features and ROI',
+  start_date: '2025-07-01',
 };
 
-// Schedule content publication
-const scheduledPost: CreateScheduledPostInput = {
-  campaign_id: campaign.id,
-  content_id: content.id,
-  social_account_id: 789,
-  scheduled_at: "2024-03-15T10:00:00Z"
+// Type-safe AI content with URL injection preference
+const socialPost: Partial<AIContent> = {
+  content_type: 'social_post' as ContentType,
+  status: 'draft',
+  social_account_id: 7,
+  url_injection_preference: 'as_comment' as URLInjectionPreference,
+  selected_for_publish: false,
 };
 ```