@flamingo-stack/openframe-frontend-core 0.0.204 → 0.0.205

package/src/components/chat/types/component.types.ts

@@ -2,11 +2,26 @@
  * Component prop types
  */
 
-import type { ComponentType, HTMLAttributes, TextareaHTMLAttributes } from 'react'
+import type { ComponentType, HTMLAttributes, ReactNode, TextareaHTMLAttributes } from 'react'
 import type { AssistantType, AuthorType, ChatApprovalStatus, ConnectionStatus } from './chat.types'
 import type { ApprovalRequestData, Message, MessageSegment, ToolExecutionData } from './message.types'
 import type { ChatRef } from '../chat-ref.types'
 
+/**
+ * Anchor component supplied by the host (or the lib's
+ * `NavLinkAnchorViaRuntime`) for markdown links. Receives at minimum
+ * `href` / `className` / `children` — what react-markdown's anchor
+ * passes. The lib's call site spreads its `rest` via `any`, so
+ * implementations are free to declare additional optional routing
+ * props (e.g. `path`, `targetPlatform`) without TS forcing the host's
+ * NavLinkAnchor prop type to know about them.
+ */
+export type NavLinkAnchorComponent = ComponentType<{
+  href: string
+  className?: string
+  children?: ReactNode
+}>
+
 // ========== Chat Container Props ==========
 
 export interface ChatContainerProps extends HTMLAttributes<HTMLDivElement> {
@@ -35,6 +50,18 @@ export interface ChatHeaderProps extends HTMLAttributes<HTMLDivElement> {
   serverUrl?: string | null
   headerActions?: React.ReactNode
   ticketInfo?: ChatHeaderTicketInfo
+  /**
+   * Drop the default `max-w-ods-content-narrow` (= 600px) constraint so
+   * the header fills the entire parent width. Use for chat dialogs
+   * embedded in narrow side panels (e.g. the multi-platform-hub
+   * `<GlobalAskAI>` panel) where the 600px column would float in the
+   * middle of a 720px panel and look misaligned vs the full-width
+   * input + content area.
+   *
+   * Default `false` — preserves the existing centered-narrow layout
+   * for legacy consumers.
+   */
+  fullWidth?: boolean
 }
 
 // ========== Connection Indicator Props ==========
@@ -94,12 +121,13 @@ export interface ChatMessageEnhancedProps extends Omit<HTMLAttributes<HTMLDivEle
    *
    * `card://` markers are still intercepted by the override BEFORE this
    * component runs, so the host need not handle them.
+   *
+   * Implementations MAY declare additional optional props (e.g.
+   * `path`, `targetPlatform` on `NavLinkAnchorViaRuntime`) — react-markdown
+   * passes its anchor `rest` props via spread, so undeclared extras
+   * simply default to undefined on the receiver.
    */
-  NavLinkAnchor?: React.ComponentType<{
-    href: string
-    className?: string
-    children?: React.ReactNode
-  } & Record<string, unknown>>
+  NavLinkAnchor?: NavLinkAnchorComponent
 }
 
 // ========== Chat Message List Props ==========
@@ -113,6 +141,15 @@ export interface ChatMessageListProps extends HTMLAttributes<HTMLDivElement> {
   smoothScroll?: boolean
   autoScroll?: boolean
   showAvatars?: boolean
+  /** Same `fullWidth` semantics as `ChatHeaderProps.fullWidth` — drops
+   *  the inner content wrapper's `max-w-ods-content-narrow` so messages
+   *  fill the entire scroller width. Preferred over `contentClassName=
+   *  "!max-w-none"` for new consumers (clearer intent, no
+   *  `!important` specificity wrestling). */
+  fullWidth?: boolean
+  /** @deprecated Prefer `fullWidth` for the full-panel-width use case.
+   *  This prop remains supported for callers that need a NON-binary
+   *  override (custom max-w value, etc.). */
   contentClassName?: string
   assistantType?: AssistantType
   assistantIcon?: React.ReactNode
@@ -129,11 +166,7 @@ export interface ChatMessageListProps extends HTMLAttributes<HTMLDivElement> {
   /** Host-provided anchor for markdown links. Forwarded verbatim to every
    *  message's ChatMessageEnhanced. Owns the unified click rule
    *  (same-origin soft nav, cross-origin new tab). */
-  NavLinkAnchor?: React.ComponentType<{
-    href: string
-    className?: string
-    children?: React.ReactNode
-  } & Record<string, unknown>>
+  NavLinkAnchor?: NavLinkAnchorComponent
 }
 
 export interface ChatMessageListRef {
@@ -194,6 +227,15 @@ export interface SlashCommandSummary {
    *  ≥1 action). Single source of truth — same array drives the
    *  empty-state chip on the host side via the synchronous registry. */
   actions: SlashCommandSummaryAction[]
+  /** Icon-registry key — drives both the empty-state chip glyph AND the
+   *  autocomplete dropdown row glyph. Optional; falls back to the
+   *  `primarySourceId`-based resolution when missing. */
+  iconName?: string
+  /** Admin-UI bucket id. */
+  category?: string
+  /** Empty-state chip-grid sort key. Undefined = NOT a chip (utility /
+   *  thematic command — autocomplete dropdown only). Lower = earlier. */
+  displayOrder?: number
 }
 
 /** Icon + label pair returned by the consumer's `resolveSourceIcon`. The
@@ -237,6 +279,10 @@ export interface ChatInputProps extends Omit<TextareaHTMLAttributes<HTMLTextArea
   onStop?: () => void | Promise<void>
   sending?: boolean
   awaitingResponse?: boolean
+  /** Same `fullWidth` semantics as `ChatHeaderProps.fullWidth` — drops
+   *  the default `max-w-ods-content-narrow` so the input fills the
+   *  parent. */
+  fullWidth?: boolean
   /**
    * @deprecated The avatar-offset layout was removed; this prop is accepted
    * for back-compat but silently ignored. Safe to drop from call sites.

package/src/components/chat/types/entities/blog.ts

@@ -0,0 +1,27 @@
+/**
+ * Blog entity types — chat card consumer barrel.
+ *
+ * The canonical Blog shapes already live in `src/types/blog.ts` (lib).
+ * Audit found NO competing definition in the hub — clients have always
+ * relied on this lib shape. This module re-exports the chat-card-relevant
+ * surface so the entities barrel has a single import path.
+ *
+ * Cards consume `BlogPost` (full row) or `BlogPostSummary` (the catalog
+ * projection). Tags / categories / author / pagination shapes are
+ * re-exported for completeness.
+ */
+
+export type {
+  BlogPost,
+  BlogPostSummary,
+  BlogPostPlatform,
+  BlogPostCategory,
+  BlogPostTag,
+  BlogCategory,
+  BlogTag,
+  BlogAuthor,
+  BlogMediaAsset,
+  BlogStatus,
+  BlogPagination,
+  BlogSearchParams,
+} from '@/types/blog';

package/src/components/chat/types/entities/case-study.ts

@@ -0,0 +1,14 @@
+/**
+ * Case Study entity types — chat card consumer barrel.
+ *
+ * The canonical CaseStudy shape already lives in `src/types/case-study.ts`
+ * (lib). Audit found NO competing definition in the hub — clients have
+ * always relied on this lib shape. This module re-exports it for the
+ * chat entities barrel.
+ */
+
+export type {
+  CaseStudy,
+  CaseStudyFilters,
+  CaseStudyListResponse,
+} from '@/types/case-study';

package/src/components/chat/types/entities/content-ref.ts

@@ -0,0 +1,23 @@
+/**
+ * ContentRef — the unified link/embed shape stored in JSONB columns
+ * across investor updates, performance baselines, and any other entity
+ * that surfaces "related content" rails.
+ *
+ * Lifted from `lib/data/investor-update-utils-shared.ts` in the hub
+ * (the server-side data utils in the same file stay hub-side; only the
+ * TYPE moves here).
+ */
+
+export interface ContentRef {
+  type: string;
+  id: string;
+  slug: string;
+  url: string;
+  targetPlatform?: string | null;
+  title: string;
+  summary?: string;
+  image_url?: string;
+  image_bg_color?: string;
+  visibility: 'public' | 'internal';
+  display_order: number;
+}

package/src/components/chat/types/entities/customer-interview.ts

@@ -0,0 +1,15 @@
+/**
+ * Customer Interview entity types — chat card consumer barrel.
+ *
+ * The canonical CustomerInterview shape already lives in
+ * `src/types/customer-interview.ts` (lib). Audit found NO competing
+ * definition in the hub — clients have always relied on this lib shape.
+ * This module re-exports it for the chat entities barrel.
+ */
+
+export type {
+  CustomerInterview,
+  CustomerInterviewConfig,
+  CustomerInterviewFilters,
+  CustomerInterviewListResponse,
+} from '@/types/customer-interview';

package/src/components/chat/types/entities/data-room-doc.ts

@@ -0,0 +1,37 @@
+/**
+ * Data Room Doc entity — wire shape for the chat data-room-doc card.
+ *
+ * Lifted from `components/shared/data-room/data-room-doc-card.tsx`.
+ * Covers both `data_room_documents` rows and `openframe-docs` markdown
+ * rows — the card differentiates via `sourceRepo` and routes the click
+ * via the shared `resolveSourceRowCTA` helper.
+ */
+
+export interface DataRoomDocCardItem {
+  /** Data-room doc UUID (the `external_id` / `id` from data_room_documents) */
+  id: string;
+  /** Display title — the doc's `name` */
+  title: string;
+  /** Path within the data room — e.g. `legal/fundraising/seed/executed/vertex-vii-3.5m-safe` */
+  path?: string | null;
+  /** Optional content preview (up to ~200 chars) */
+  preview?: string | null;
+  /** Resolved URL (typically `/data-room/<path>`) — null when not resolvable */
+  url?: string | null;
+  /** RagTableConfig.id (e.g. `'openframe-docs'`, `'data-room-docs'`) — drives
+   *  the badge label via `SOURCE_LABELS_BY_TABLE`. Falls back to "Data room"
+   *  when missing. */
+  sourceRepo?: string | null;
+  /** Chat shell's base route (e.g. `/data-room`, `/knowledge-base`). Threaded
+   *  from `renderChatInlineEntityCard` → `renderCompactEntityCard` →
+   *  `DataRoomDocChatCard` so the shared `resolveSourceRowCTA` helper can
+   *  compose the destination URL identically to the SourceChip path. */
+  baseRoute?: string;
+  /** Cross-platform target for the card click (e.g. `'flamingo'` to open the
+   *  link on www.flamingo.cx). When set, the resolver composes an absolute
+   *  cross-origin URL; the click handler routes through a plain `<a>` so the
+   *  link opens in a new tab. Without this, product-hub clicks on
+   *  `/knowledge-base/<path>` get redirected to `/` by the middleware
+   *  because the route is not in the platform's `allowedRoutes`. */
+  chipBasePlatform?: string;
+}

package/src/components/chat/types/entities/github-activity.ts

@@ -0,0 +1,36 @@
+/**
+ * GitHub Activity entity types — wire shape for chat cards.
+ *
+ * Mirrors the canonical row consumed by `GitHubActivityCard`:
+ *   - `commit`     : commit on a repo (SHA, message)
+ *   - `pull_request`: PR opened/updated
+ *   - `pr_review`  : review submitted on a PR (state badge drives color)
+ *
+ * Lifted from `components/shared/github/github-activity-card.tsx` so the
+ * type is canonical in lib — clients can build / pass / extend it without
+ * pulling in the card itself.
+ */
+
+export type GitHubActivityKind = 'commit' | 'pull_request' | 'pr_review';
+
+export type PrReviewState =
+  | 'APPROVED'
+  | 'CHANGES_REQUESTED'
+  | 'COMMENTED'
+  | 'DISMISSED'
+  | 'PENDING';
+
+export interface GitHubActivityItem {
+  /** Commit SHA (full or short) / PR-# / review id */
+  id: string;
+  /** Commit message / PR title / review state */
+  title: string;
+  /** "owner/repo" — derived from the GitHub URL when not provided */
+  repo?: string;
+  /** ISO timestamp or millisecond epoch */
+  dateUpdated?: string | number | null;
+  /** GitHub URL — used as the link target */
+  url?: string | null;
+  /** Discriminator — defaults to 'commit' when not supplied */
+  kind?: GitHubActivityKind;
+}

package/src/components/chat/types/entities/hubspot-ticket.ts

@@ -0,0 +1,39 @@
+/**
+ * HubSpot Ticket entity — wire shape for the chat hubspot-ticket card.
+ *
+ * Lifted from `components/shared/hubspot/hubspot-ticket-card.tsx`. The
+ * card consumes this shape across THREE variants — FULL (all fields,
+ * for admin/internal viewers), ANON (no customerCompany, no url), and
+ * SELF (the chat user's own tickets, no admin URL). The shape itself
+ * is the same; the indexer redacts the variant-restricted fields to
+ * null before sending the row to the client.
+ */
+
+export interface HubspotTicketItem {
+  /** HubSpot ticket id (the `external_id` column on hubspot_tickets) */
+  id: string;
+  /** Subject — ticket title */
+  title: string;
+  /** Body preview (sanitized via the mapper's `buildPreview`) */
+  preview?: string;
+  /** Canonical status (NEW | IN_PROGRESS | WAITING | CLOSED) — drives
+   *  badge color + sort order. */
+  status?: string | null;
+  /** Human-readable HubSpot pipeline stage label (e.g. "Code review",
+   *  "Closed"). Drives badge TEXT. Falls back to the formatted canonical
+   *  `status` when null (rows synced before the column landed). */
+  statusLabel?: string | null;
+  /** Severity: LOW | MEDIUM | HIGH | URGENT */
+  priority?: string | null;
+  /** Customer company (FULL variant only — anon strips this) */
+  customerCompany?: string | null;
+  /** Customer email — usually the chat-creating user's address. Shown as
+   *  a discrete row so customers can confirm who the ticket is for
+   *  (especially relevant in proxy-auth surfaces where the chat user
+   *  acts on behalf of another email). */
+  customerEmail?: string | null;
+  /** ISO timestamp or epoch */
+  dateUpdated?: string | number | null;
+  /** HubSpot UI URL (FULL variant only; null for anon + self) */
+  url?: string | null;
+}

package/src/components/chat/types/entities/index.ts

@@ -0,0 +1,28 @@
+/**
+ * Chat entity row types — canonical wire shapes the chat cards consume.
+ *
+ * Each module here holds the type for one entity surface (commit/PR/review,
+ * slack message, hubspot ticket, data-room doc, roadmap item, investor
+ * update, onboarding guide, program items, blog, case study, customer
+ * interview). They moved here from the hub when the chat surface
+ * migrated into lib so the cards have a single, lib-owned source of
+ * truth — clients can compose the wire shape without importing hub-tree
+ * helpers.
+ *
+ * Hub-side server utilities that PRODUCE these shapes (DAL functions,
+ * RAG mappers, sync engines) stay in the hub — only the wire TYPE
+ * (+ pure formatters that operate on it) lives here.
+ */
+
+export * from './blog';
+export * from './case-study';
+export * from './content-ref';
+export * from './customer-interview';
+export * from './data-room-doc';
+export * from './github-activity';
+export * from './hubspot-ticket';
+export * from './investor-update';
+export * from './onboarding-guide';
+export * from './program-types';
+export * from './roadmap-item';
+export * from './slack-message';

package/src/components/chat/types/entities/investor-update.ts

@@ -0,0 +1,100 @@
+/**
+ * Investor Update entity — wire shape for the chat investor-update card
+ * + the `/api/investor-updates` reads.
+ *
+ * Lifted from `lib/data/investor-update-utils-shared.ts` in the hub.
+ * The server-side data utils + visibility filters in that file stay
+ * hub-side; only the TYPES + the pure `formatInvestorUpdatePeriod`
+ * formatter move here.
+ */
+
+import type { ContentRef } from './content-ref';
+
+export interface MetricEntry {
+  current: number;
+  previous?: number;
+  change_pct?: number;
+  visibility: 'public' | 'internal';
+}
+
+export interface HighlightEntry {
+  title: string;
+  description?: string;
+  visibility: 'public' | 'internal';
+}
+
+export interface InvestorUpdateHighlights {
+  key_highlights?: HighlightEntry[];
+  product_milestones?: HighlightEntry[];
+  community_updates?: HighlightEntry[];
+  upcoming_priorities?: HighlightEntry[];
+  financial_notes?: HighlightEntry[];
+}
+
+export interface InvestorUpdate {
+  id: string;
+  title: string;
+  slug: string;
+  update_number: number | null;
+  period_start: string | null;
+  period_end: string | null;
+  platform_id: string | null;
+  content: string | null;
+  video_summary: string | null;
+  transcript: string | null;
+  srt_content?: string | null;
+  main_video_url: string | null;
+  highlight_video_url: string | null;
+  highlight_video_thumbnail: string | null;
+  main_video_thumbnail: string | null;
+  video_bites: unknown[];
+  featured_image: string | null;
+  strategic_update: string | null;
+  financials: Record<string, MetricEntry>;
+  metrics_snapshot: Record<string, MetricEntry>;
+  content_refs: ContentRef[];
+  highlights: InvestorUpdateHighlights | null;
+  section_visibility: Record<string, 'public' | 'internal'>;
+  status: string;
+  published_at: string | null;
+  author_id: string | null;
+  author?: {
+    id: string;
+    full_name: string;
+    avatar_url: string | null;
+    job_title: string | null;
+    email?: string | null;
+  };
+  seo_title: string | null;
+  seo_description: string | null;
+  seo_keywords: string | null;
+  og_image_url: string | null;
+  hubspot_email_id: string | null;
+  hubspot_email_url?: string | null;
+  custom_instructions: string | null;
+  created_at: string;
+  updated_at: string;
+  created_by: string | null;
+  updated_by: string | null;
+}
+
+/**
+ * Format an investor-update period as `Mar 2025 - May 2025` (or `?` for
+ * a missing endpoint). Pure formatter — no DB / state access, so it
+ * moves to lib alongside the types.
+ */
+export function formatInvestorUpdatePeriod(
+  start: string | null,
+  end: string | null,
+  options?: { monthFormat?: 'short' | 'long' },
+): string {
+  if (!start && !end) return '';
+  const fmt = (d: string) =>
+    new Date(d).toLocaleDateString('en-US', {
+      month: options?.monthFormat || 'short',
+      year: 'numeric',
+    });
+  const s = start ? fmt(start) : '?';
+  const e = end ? fmt(end) : '?';
+  return `${s} - ${e}`;
+}

package/src/components/chat/types/entities/onboarding-guide.ts

@@ -0,0 +1,101 @@
+/**
+ * Onboarding Guide entity — wire shape for the chat onboarding-guide
+ * card + the `/api/onboarding-guides` reads.
+ *
+ * Lifted from `lib/data/onboarding-guide-utils.ts` in the hub. The
+ * server-side DAL (createOnboardingGuide / updateOnboardingGuide /
+ * resolvePublicPlatformScope / …) stays hub-side; only the row TYPE +
+ * the filter/response shapes move here.
+ */
+
+export interface OnboardingGuide {
+  id: string;
+  title: string;
+  slug: string;
+
+  // Structured ordering
+  section: string;
+  step_order: number;
+  section_order: number;
+
+  // Body
+  content: string | null;
+  video_summary: string | null;
+  transcript: string | null;
+  transcript_words_data: unknown | null;
+  srt_content: string | null;
+  ai_transcript_formatted: string | null;
+
+  // Video pipeline. `main_video_url` (Mux / MP4) and `youtube_url` are
+  // INDEPENDENT columns — same shape as `product_releases`. The detail
+  // page + RAG mapper read whichever is set; `<VideoSourceSelector>` in
+  // the admin form toggles between them.
+  main_video_url: string | null;
+  main_video_thumbnail: string | null;
+  youtube_url: string | null;
+  highlight_video_url: string | null;
+  highlight_video_thumbnail: string | null;
+  highlight_video_duration_ms: number | null;
+  highlight_video_source: string | null;
+  video_bites: unknown[];
+
+  // Images
+  featured_image: string | null;
+  og_image_url: string | null;
+
+  // SEO
+  seo_title: string | null;
+  seo_description: string | null;
+  seo_keywords: string | null;
+
+  // Workflow
+  status: string;
+  published_at: string | null;
+  author_id: string | null;
+  author?: {
+    id: string;
+    full_name: string;
+    avatar_url: string | null;
+    job_title: string | null;
+    email?: string | null;
+  };
+  custom_instructions: string | null;
+  config: Record<string, unknown> | null;
+  ai_effort_score: number | null;
+
+  // Junction (multi-platform)
+  onboarding_guide_platforms?: Array<{
+    platform_id: string;
+    is_featured: boolean;
+    featured_order: number | null;
+    name?: string;
+    display_name?: string;
+  }>;
+
+  // Audit
+  created_at: string;
+  updated_at: string;
+  created_by: string | null;
+  updated_by: string | null;
+}
+
+export interface OnboardingGuideFilters {
+  status?: string;
+  search?: string;
+  section?: string;
+  platform?: string;
+  limit?: number;
+  offset?: number;
+  ids?: string[];
+}
+
+export interface OnboardingGuideListResponse {
+  data: OnboardingGuide[];
+  count: number;
+}
+
+export interface OnboardingGuideSectionSummary {
+  section: string;
+  section_order: number;
+  count: number;
+}