@oxy.so/bloom 4.7.0 → 4.9.0

package/src/ai-chat/context.ts

@@ -79,3 +79,42 @@ export const AiChatShellContext = createContext<AiChatShellState | null>(null);
 export function useAiChatShell(): AiChatShellState | null {
   return useContext(AiChatShellContext);
 }
+
+/**
+ * The heights an `AiChatContainer floatingChrome` measures for the chrome it
+ * floats over its `children`: the header block at the top and the footer
+ * (`AgentThinking` + composer, with its fade strip) at the bottom, px.
+ */
+export interface AiChatChromeInsets {
+  top: number;
+  bottom: number;
+}
+
+/** Where the thread is, reported to the container so each edge knows when to fade. */
+export interface AiChatScrollMetrics {
+  offset: number;
+  viewport: number;
+  content: number;
+}
+
+/**
+ * What a floating-chrome container hands its `children`. Internal: the thread
+ * reads `insets` and reports its scroll; hosts read only the insets, through
+ * `useAiChatChromeInsets()`.
+ */
+export interface AiChatFloatingChrome {
+  insets: AiChatChromeInsets;
+  reportScroll: (metrics: AiChatScrollMetrics) => void;
+}
+
+export const AiChatFloatingChromeContext = createContext<AiChatFloatingChrome | null>(null);
+
+/**
+ * Inside `AiChatContainer floatingChrome`: how much of the top and bottom of the
+ * card the floating header and composer cover, so a custom child (an empty
+ * state, a scroller of its own) can keep its resting content clear of them.
+ * `null` anywhere else — outside a container, or in one that stacks its chrome.
+ */
+export function useAiChatChromeInsets(): AiChatChromeInsets | null {
+  return useContext(AiChatFloatingChromeContext)?.insets ?? null;
+}

package/src/ai-chat/index.ts

@@ -15,8 +15,8 @@ export {
   AiChatUserMessage,
 } from './AiChatMessages';
 export { AiChatMobileHeader, AiChatResizeHandle, AiChatShell } from './AiChatShell';
-export { useAiChatShell } from './context';
-export type { AiChatShellState } from './context';
+export { useAiChatChromeInsets, useAiChatShell } from './context';
+export type { AiChatChromeInsets, AiChatShellState } from './context';
 export type {
   AiChatAssistantMessageProps,
   AiChatBulletListProps,

package/src/ai-chat/index.web.ts

@@ -20,8 +20,8 @@ export {
   AiChatUserMessage,
 } from './AiChatMessages';
 export { AiChatMobileHeader, AiChatResizeHandle, AiChatShell } from './AiChatShell';
-export { useAiChatShell } from './context';
-export type { AiChatShellState } from './context';
+export { useAiChatChromeInsets, useAiChatShell } from './context';
+export type { AiChatChromeInsets, AiChatShellState } from './context';
 export type {
   AiChatAssistantMessageProps,
   AiChatBulletListProps,

package/src/ai-chat/types.ts

@@ -317,6 +317,23 @@ export interface AiChatContainerProps {
    * `false` leaves the root transparent.
    */
   surface?: boolean;
+  /**
+   * Float the header and the composer OVER the transcript instead of stacking
+   * them around it. Default `false`: header row, thread, footer, as siblings.
+   *
+   * With it, `children` fill the whole card and scroll BEHIND both: the header
+   * slot and breadcrumb row are pinned to the top with no band of their own,
+   * the footer (`AgentThinking` + `composer`) to the bottom. Each edge paints a
+   * fade of the card's surface only while the transcript actually runs under
+   * it, ramping in over the first px of overlap. An `AiChatThread` inside pads
+   * its content by the measured heights of both, so the first and last turns
+   * rest clear of them; a custom child reads the same numbers from
+   * `useAiChatChromeInsets()`.
+   *
+   * The fades are background-secondary; with `surface={false}` there is no
+   * known colour to fade to, so the chrome floats without them.
+   */
+  floatingChrome?: boolean;
   labels?: AiChatContainerLabels;
   style?: StyleProp<ViewStyle>;
   testID?: string;

package/src/settings-modal/SettingsStorage.tsx

@@ -446,10 +446,12 @@ export function SettingsStoragePage({
 
   return (
     <View testID={testID} style={[styles.page, settingsRingVars(palette), style]}>
-      <FileUpload
-        {...upload}
-        testID={testID ? `${testID}-dropzone` : undefined}
-      />
+      {upload === false ? null : (
+        <FileUpload
+          {...upload}
+          testID={testID ? `${testID}-dropzone` : undefined}
+        />
+      )}
 
       <View style={[styles.table, { borderColor: palette.separator }]} testID={testID ? `${testID}-table` : undefined}>
         <View style={styles.toolbar}>

package/src/settings-modal/types.ts

@@ -320,8 +320,9 @@ export interface SettingsStoragePageProps {
    * The dropzone's props — Bloom's `FileUpload`. Omitted, it runs a
    * self-simulating demo; pass `file`/`progress`/`onFileSelected` for a real
    * upload, and add the finished file to `files` from `onUploadComplete`.
+   * `false` drops the dropzone: a read-only store of what already exists.
    */
-  upload?: Omit<FileUploadProps, 'style' | 'testID'>;
+  upload?: Omit<FileUploadProps, 'style' | 'testID'> | false;
   kinds?: SettingsFileKind[];
   selectedIds?: string[];
   defaultSelectedIds?: string[];