@flamingo-stack/openframe-frontend-core 0.0.210-snapshot.20260528032637 → 0.0.210

package/dist/chunk-ZG2YY5E7.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/contexts/chat-runtime-context.tsx"],"sourcesContent":["'use client'\n\n/**\n * Chat runtime context — single seam for embedding the chat panel in a\n * different host (e.g. user1.openframe.ai reverse-proxying API calls\n * under /api/mingo-guide/* to hub.openframe.ai/api/*).\n *\n * Three concerns, one context:\n *   1. API endpoints: chatStreamUrl / approvalToolUrl / commandsUrl /\n *      buildListUrl + attachment endpoints + chat-identity. The chat\n *      reads them from runtime; hub vs embedded app supply different\n *      strings via different providers.\n *   2. Navigation mode + callbacks: 'host' or 'embed' mode. Host wires\n *      its own router/docNav via the optional `navigate` callback\n *      (plain function, NOT a hook); embed forces new-tab via\n *      `defaultContentOrigin` + lib's `resolveExternalNavigation`.\n *   3. Identity context: only `source` (required for localStorage\n *      namespacing). The display identity (greeting first-name etc.)\n *      comes from the server via `useChatIdentity()` — never injected\n *      client-side, so it always matches the server-resolved auth.\n *\n * Sibling of EndpointsRuntimeContext (announcement bar, contact form,\n * access codes). Each runtime stays an independent React context so\n * embedders can opt into either feature without forcing the other.\n *\n * IMPORTANT for embedders: memoize the value passed to\n * `<ChatRuntimeContext.Provider value={...}>` (e.g. via React.useMemo).\n * Every change to its reference identity invalidates downstream\n * `useMemo` consumers (the chat input's slash-commands binding,\n * useNavLink's embed-resolution memo, useDocChat's streamFn factory).\n * The hub's `<HubRuntimeProvider>` already memoizes correctly with\n * stable deps. Embedded apps that build the value inline on each render\n * will pay an avoidable re-render cost across the entire chat tree.\n */\n\nimport { createContext, useContext, type ReactNode } from 'react'\n\n/**\n * Runtime config consumed by the chat panel.\n */\nexport interface ChatRuntime {\n  endpoints: {\n    /** POST streaming chat. Hub: '/api/docs/chat'. */\n    chatStreamUrl: string\n    /** POST agent approve/reject. Hub: '/api/chat/agent/confirm-tool'. */\n    approvalToolUrl: string\n    /** GET slash-command catalog. Hub: '/api/docs/commands'. */\n    commandsUrl: string\n    /** Build entity-card list URL for a content type + ids. Hub delegates\n     *  to the rag-table-config registry; embedded app provides its own\n     *  per-type URL builder against the reverse proxy. Returns null when\n     *  the type has no list endpoint (caller skips rendering). */\n    buildListUrl: (type: string, ids: string[]) => string | null\n    /** Chat-attachment endpoints — added for the v2 attachment feature.\n     *\n     *  Three concerns:\n     *    - `attachmentUploadUrl` — POSTed by the chat-attachment hook\n     *      to mint a Supabase signed-upload-URL + HMAC view token.\n     *    - `attachmentViewUrlPrefix` — embedded in markdown URLs the\n     *      chat hosts in user message bubbles (`![]()` / `[Attached]`).\n     *      Stored in chat history; chosen at SEND time. In host mode the\n     *      relative `/api/storage/view/chat-attachments/` is sufficient\n     *      (same-origin); embedders supply an absolute hub URL so the\n     *      browser can fetch cross-origin.\n     *    - `identityUrl` — GET endpoint the `useChatIdentity` hook\n     *      hits to learn the `{authTier, source, attachmentsEnabled}`\n     *      capability bag for the current session. Used beyond chat\n     *      (tickets / contact form / any embedded surface that needs\n     *      to identify the proxied customer), so the name has no\n     *      \"chat\" prefix even though the consuming hook still does. */\n    attachmentUploadUrl: string\n    attachmentViewUrlPrefix: string\n    identityUrl: string\n    /** Optional URL prefix for the image proxy (`<prefix>?url=<external>`).\n     *  When unset, lib's `getProxiedImageUrl` returns the original URL\n     *  unchanged. Hub default: '/api/image-proxy'. Embedders that don't\n     *  host an image-proxy route leave this undefined → images load\n     *  directly cross-origin (CORS-permitting). */\n    imageProxyUrlPrefix?: string\n    /** Optional list of hostnames that should bypass the image proxy\n     *  (rendered direct). Hub uses ['openmsp.ai']; embedders typically\n     *  leave it unset. Matches the `skipDomains` parameter of\n     *  `getProxiedImageUrl`. */\n    imageProxySkipDomains?: string[]\n  }\n  navigation: {\n    /** ONE knob, two behaviors:\n     *  - 'host' = use the host page's existing click-routing untouched.\n     *    The chat panel calls `navigate?.()` for in-app routing.\n     *  - 'embed' = guest inside another app: short-circuit at the top\n     *    of click handlers to force new-tab + absolutize via\n     *    resolveExternalNavigation. */\n    mode: 'host' | 'embed'\n    /** Embed-only fallback origin for relative URLs whose target platform\n     *  can't be inferred. Used by resolveExternalNavigation when\n     *  `targetPlatform` is null — without this, a relative `/foo` href would\n     *  window.open against the embedder's origin, which is WRONG.\n     *  Set to your content host (e.g. 'https://hub.openframe.ai').\n     *  Required by the embedded app whenever mode='embed'. */\n    defaultContentOrigin?: string\n    /** Override for opening external URLs. MUST BE SYNCHRONOUS —\n     *  Safari/Firefox block popups opened outside a direct user gesture.\n     *  Default: window.open(href, '_blank', 'noopener,noreferrer'). */\n    openExternal?: (href: string) => void\n    /** Optional in-app navigation callback (host-mode only).\n     *  Returns `true` if the host handled the click in-app\n     *  (router.push + docNav.navigate); returns `false`, `undefined`,\n     *  or `void` → lib falls back to window.location.assign(href).\n     *  Hub wires this via HubRuntimeProvider's HubNavigationWiring;\n     *  embedders not in Next.js leave it undefined. */\n    navigate?: (input: { href: string; path?: string | null; targetPlatform?: string | null }) => boolean | void\n    /** Optional new-tab decision callback. Returns true → lib opens in\n     *  new tab; false → same tab via `navigate`. Hub wires the existing\n     *  `decideNewTab` logic from use-nav-link.tsx (re-imports the pure\n     *  helper from lib). Embedders may omit; lib defaults to:\n     *  same-origin/same-platform → same tab, else new tab. */\n    decideNewTab?: (args: { href: string; targetPlatform?: string | null }) => boolean\n  }\n  /** Chat source identifier — REQUIRED. Used for localStorage\n   *  namespacing (`mingo-chat-<source>-v1`). Hub sets via\n   *  `currentPlatform()`; embedders set explicitly.\n   *  `useEmbeddedChat()` throws if source is empty/missing. */\n  source: string\n  // NOTE: No `user` field. The chat's display identity (greeting\n  // first-name, etc.) comes from the SERVER-resolved auth via\n  // `useChatIdentity()` — the same identity the server uses to\n  // authorize requests. Letting embedders pass a client-side `user`\n  // would let it desync from the actual auth tier, causing greetings\n  // like \"Hey Bob\" while the server treats the session as\n  // alice@example.com. Single source of truth: the server.\n}\n\nexport const ChatRuntimeContext = createContext<ChatRuntime | null>(null)\n\n/**\n * Returns the active runtime, or null when no provider is mounted.\n * NULL is a first-class value — it signals \"no chat runtime configured.\"\n * Optional consumers fall back to no-op behavior; strict consumers\n * use `useRequiredChatRuntime` (below).\n */\nexport function useChatRuntime(): ChatRuntime | null {\n  return useContext(ChatRuntimeContext)\n}\n\n/**\n * Strict variant used INSIDE the chat panel. Throws if no provider.\n * The hub guarantees one exists by mounting `<HubRuntimeProvider>` at\n * root; the embedded app mounts its own `<ChatRuntimeContext.Provider>`\n * at the tree root. In Jest / Storybook tests that render chat\n * internals directly, wrap with `<HubRuntimeProvider>` (hub defaults)\n * or supply `<ChatRuntimeContext.Provider value={mockedRuntime}>`.\n */\nexport function useRequiredChatRuntime(): ChatRuntime {\n  const v = useContext(ChatRuntimeContext)\n  if (!v) {\n    throw new Error(\n      '[chat-runtime] hook called outside a <ChatRuntimeContext.Provider>. ' +\n        'The hub mounts <HubRuntimeProvider> at root — this only fires when ' +\n        'chat internals are rendered above the provider tree. ' +\n        'Fix: ensure the rendering subtree descends from the runtime provider. ' +\n        'In tests/Storybook: wrap with <HubRuntimeProvider> or supply ' +\n        'a <ChatRuntimeContext.Provider value={mockedRuntime}>.',\n    )\n  }\n  return v\n}\n"],"mappings":";;;AAmCA,SAAS,eAAe,kBAAkC;AAiGnD,IAAM,qBAAqB,cAAkC,IAAI;AAQjE,SAAS,iBAAqC;AACnD,SAAO,WAAW,kBAAkB;AACtC;AAUO,SAAS,yBAAsC;AACpD,QAAM,IAAI,WAAW,kBAAkB;AACvC,MAAI,CAAC,GAAG;AACN,UAAM,IAAI;AAAA,MACR;AAAA,IAMF;AAAA,EACF;AACA,SAAO;AACT;","names":[]}

package/dist/utils/scroll-into-view.d.ts

@@ -1,63 +0,0 @@
-/**
- * `scrollElementIntoView` — canonical "smooth scroll element to top
- * of viewport, account for sticky chrome, optionally adjust for
- * known layout shifts" helper.
- *
- * Before this util existed, ~3 different call sites in the lib + hub
- * had the same 5-line snippet copy-pasted with subtle differences:
- *
- *   - `useUnifiedNav` same-URL re-scroll branch (hub)
- *   - `<HelpCenterCard>` click-to-expand (lib, with cross-row
- *     layout-shift adjustment)
- *   - Future ticket-row / docs anchor scrolls
- *
- * The canonical pattern is `window.scrollTo({top, behavior:'smooth'})`
- * with a pre-computed pixel target — NOT `element.scrollIntoView()`.
- * Pre-computing the target lets the browser run a clean uninterrupted
- * smooth animation to a fixed pixel value. `scrollIntoView` re-targets
- * continuously as the page layout shifts during the animation, which
- * causes visible jitter when content above the target is also moving
- * (a sibling collapsing, an async image loading, …).
- *
- * The `adjustTargetY` callback is the escape hatch for cases where
- * the consumer KNOWS about an upcoming layout shift and can compute
- * the correct FINAL target before the animation starts. Example: in
- * `HelpCenterCard`, clicking row B while row A above is currently
- * expanded — A's drawer collapses simultaneously with B's expansion,
- * shifting B's tile up by A's drawer height. The consumer passes
- * `adjustTargetY: raw => raw - getAboveDrawerHeight()` and the
- * browser smooth-scrolls to the post-collapse position directly.
- */
-export interface ScrollElementIntoViewOptions {
-    /** Pixels to subtract from the target element's `top` so it lands
-     *  BELOW sticky chrome. Defaults to 0. Pass `96` (matches
-     *  `scroll-mt-24`) for the standard hub header offset. */
-    headerOffset?: number;
-    /** Scroll animation style. Defaults to `'smooth'`. Use `'instant'`
-     *  for imperative jumps where animation would feel laggy (deep
-     *  link land, programmatic focus moves). */
-    behavior?: ScrollBehavior;
-    /** Optional adjustment applied to the computed pixel target. The
-     *  callback receives the "raw" Y (`element.top + scrollY -
-     *  headerOffset`) and returns the FINAL pixel target. Use this
-     *  when the caller knows about a layout shift that will happen
-     *  between the call and the animation completing — the browser's
-     *  smooth-scroll commits to a single pixel value, so providing the
-     *  post-shift target up front lands the element correctly even as
-     *  content above it moves. */
-    adjustTargetY?: (rawTargetY: number) => number;
-}
-/**
- * Scroll the page so `target` lands at the top of the viewport,
- * accounting for sticky chrome via `headerOffset`. Returns void; the
- * scroll runs async via the browser's smooth-scroll engine.
- *
- * Accepts:
- *   - `HTMLElement` — direct reference (most common from `useRef`).
- *   - `null` / `undefined` — no-op so callers can pass refs without
- *     defensive branching.
- *
- * SSR-safe: short-circuits when `window` is undefined.
- */
-export declare function scrollElementIntoView(target: HTMLElement | null | undefined, options?: ScrollElementIntoViewOptions): void;
-//# sourceMappingURL=scroll-into-view.d.ts.map

package/dist/utils/scroll-into-view.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"scroll-into-view.d.ts","sourceRoot":"","sources":["../../src/utils/scroll-into-view.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAEH,MAAM,WAAW,4BAA4B;IAC3C;;8DAE0D;IAC1D,YAAY,CAAC,EAAE,MAAM,CAAA;IACrB;;gDAE4C;IAC5C,QAAQ,CAAC,EAAE,cAAc,CAAA;IACzB;;;;;;;kCAO8B;IAC9B,aAAa,CAAC,EAAE,CAAC,UAAU,EAAE,MAAM,KAAK,MAAM,CAAA;CAC/C;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,qBAAqB,CACnC,MAAM,EAAE,WAAW,GAAG,IAAI,GAAG,SAAS,EACtC,OAAO,GAAE,4BAAiC,GACzC,IAAI,CAON"}

package/src/utils/scroll-into-view.ts

@@ -1,74 +0,0 @@
-/**
- * `scrollElementIntoView` — canonical "smooth scroll element to top
- * of viewport, account for sticky chrome, optionally adjust for
- * known layout shifts" helper.
- *
- * Before this util existed, ~3 different call sites in the lib + hub
- * had the same 5-line snippet copy-pasted with subtle differences:
- *
- *   - `useUnifiedNav` same-URL re-scroll branch (hub)
- *   - `<HelpCenterCard>` click-to-expand (lib, with cross-row
- *     layout-shift adjustment)
- *   - Future ticket-row / docs anchor scrolls
- *
- * The canonical pattern is `window.scrollTo({top, behavior:'smooth'})`
- * with a pre-computed pixel target — NOT `element.scrollIntoView()`.
- * Pre-computing the target lets the browser run a clean uninterrupted
- * smooth animation to a fixed pixel value. `scrollIntoView` re-targets
- * continuously as the page layout shifts during the animation, which
- * causes visible jitter when content above the target is also moving
- * (a sibling collapsing, an async image loading, …).
- *
- * The `adjustTargetY` callback is the escape hatch for cases where
- * the consumer KNOWS about an upcoming layout shift and can compute
- * the correct FINAL target before the animation starts. Example: in
- * `HelpCenterCard`, clicking row B while row A above is currently
- * expanded — A's drawer collapses simultaneously with B's expansion,
- * shifting B's tile up by A's drawer height. The consumer passes
- * `adjustTargetY: raw => raw - getAboveDrawerHeight()` and the
- * browser smooth-scrolls to the post-collapse position directly.
- */
-
-export interface ScrollElementIntoViewOptions {
-  /** Pixels to subtract from the target element's `top` so it lands
-   *  BELOW sticky chrome. Defaults to 0. Pass `96` (matches
-   *  `scroll-mt-24`) for the standard hub header offset. */
-  headerOffset?: number
-  /** Scroll animation style. Defaults to `'smooth'`. Use `'instant'`
-   *  for imperative jumps where animation would feel laggy (deep
-   *  link land, programmatic focus moves). */
-  behavior?: ScrollBehavior
-  /** Optional adjustment applied to the computed pixel target. The
-   *  callback receives the "raw" Y (`element.top + scrollY -
-   *  headerOffset`) and returns the FINAL pixel target. Use this
-   *  when the caller knows about a layout shift that will happen
-   *  between the call and the animation completing — the browser's
-   *  smooth-scroll commits to a single pixel value, so providing the
-   *  post-shift target up front lands the element correctly even as
-   *  content above it moves. */
-  adjustTargetY?: (rawTargetY: number) => number
-}
-
-/**
- * Scroll the page so `target` lands at the top of the viewport,
- * accounting for sticky chrome via `headerOffset`. Returns void; the
- * scroll runs async via the browser's smooth-scroll engine.
- *
- * Accepts:
- *   - `HTMLElement` — direct reference (most common from `useRef`).
- *   - `null` / `undefined` — no-op so callers can pass refs without
- *     defensive branching.
- *
- * SSR-safe: short-circuits when `window` is undefined.
- */
-export function scrollElementIntoView(
-  target: HTMLElement | null | undefined,
-  options: ScrollElementIntoViewOptions = {},
-): void {
-  if (typeof window === 'undefined' || !target) return
-  const { headerOffset = 0, behavior = 'smooth', adjustTargetY } = options
-  const rawTargetY =
-    target.getBoundingClientRect().top + window.scrollY - headerOffset
-  const finalY = adjustTargetY ? adjustTargetY(rawTargetY) : rawTargetY
-  window.scrollTo({ top: Math.max(0, finalY), behavior })
-}