@alia.onl/sdk 15.2.1 → 15.4.0

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # @alia.onl/sdk
 
+## 15.4.0
+
+- **New leaf entry `@alia.onl/sdk/avatar`.** `AliaAvatarIcon`, `AliaAvatar`, `ALIA_AVATAR` and
+  `useAliaActivity` without the chat: an app draws Alia's live avatar on a header button and keeps
+  the conversation UI behind a lazy import, instead of putting the whole SDK in its entry bundle.
+  `check:entries` holds the leaf free of the sheet, the composer, the markdown renderer and the
+  voice call. The root entry still exports the same four.
+
+## 15.3.0
+
+- **The composer is Bloom's `ComposerPill`.** `AliaComposer` (the sheet's, the screen's and the
+  Alia app's one composer) was built on `ComposerPanel` in 13.2.0, which changed the sheet's
+  look. It is the pill again — the compact composer the sheet always had — carrying everything the
+  app needed from the panel: the power-level picker (`modes` → the pill's `permissions`), the
+  docked questions and the status tab. Requires `@oxy.so/bloom` >= 10.6.0, where the pill takes
+  them. No prop of `AliaComposer` changes.
+- The 13.1.1 note under 13.2.0 below (the avatar flights load the runtime) shipped in 13.2.0.
+
 ## 15.2.1
 
 - **The shipped source compiles under `noUnusedLocals`.** The package ships its `.tsx` source, so a

package/README.md

@@ -147,7 +147,7 @@ app should not have to install a transport to use a button.
 ## The composer
 
 The sheet, the screen and the Alia app share one composer, `AliaComposer`: Bloom's
-`ComposerPanel` with files by paste and drop (read with real progress, retried, refused with a
+`ComposerPill` with files by paste and drop (read with real progress, retried, refused with a
 sentence), dictation, suggestions over the field and Alia's questions docked above it.
 `AliaChatSheet` and `AliaChatScreen` render it with photos, voice and suggestions, and
 `AliaChatSheet` focuses it once the sheet has presented. To build your own surface, mount it and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alia.onl/sdk",
-  "version": "15.2.1",
+  "version": "15.4.0",
   "description": "Alia AI chat SDK — reusable chat UI, voice calls, dictation and streaming components for Oxy apps",
   "main": "src/index.ts",
   "react-native": "src/index.ts",
@@ -8,6 +8,7 @@
   "types": "src/index.ts",
   "exports": {
     ".": "./src/index.ts",
+    "./avatar": "./src/avatar.ts",
     "./content": "./src/lib/content-utils.ts",
     "./tools": "./src/tools.ts",
     "./voice": "./src/voice.ts",
@@ -40,7 +41,7 @@
     "react": "^19.2.3",
     "react-native": "^0.86.0",
     "@expo/vector-icons": "^15.1.1",
-    "@oxy.so/bloom": ">=10.4.0",
+    "@oxy.so/bloom": ">=10.6.0",
     "@oxy.so/core": ">=3.0.0",
     "@oxy.so/services": ">=8.0.0",
     "@react-native-async-storage/async-storage": "^2.2.0",

package/src/avatar.ts

@@ -0,0 +1,13 @@
+/**
+ * The avatar leaf entry: Alia's live avatar and what makes it react, without the chat.
+ *
+ * An app puts her on a button in its header (`AliaAvatarIcon`) and keeps the chat itself behind a
+ * lazy import, so the SDK's conversation UI is not in the entry bundle just to draw a face. This
+ * entry reaches the avatar, the activity store and its one socket, and nothing of the sheet, the
+ * composer, the markdown renderer or the voice call (`check:entries` holds that).
+ */
+export { ALIA_AVATAR, AliaAvatar } from './components/AliaAvatar';
+export type { AliaAvatarProps, AliaAvatarState } from './components/AliaAvatar';
+export { AliaAvatarIcon } from './components/AliaAvatarIcon';
+export { useAliaActivity } from './hooks/useAliaActivity';
+export type { UseAliaActivityOptions } from './hooks/useAliaActivity';

package/src/components/AliaComposer.tsx

@@ -14,7 +14,7 @@ import {
   type TextInputKeyPressEventData,
 } from 'react-native';
 import {
-  ComposerPanel,
+  ComposerPill,
   type ComposerPanelAddMenuGroup,
   type ComposerPanelAttachment,
   type ComposerPanelPermissionOption,
@@ -41,10 +41,10 @@ import { QuestionCard } from './QuestionCard';
 
 /**
  * Alia's composer: the ONE composer of the sheet, the screen and the Alia app, Bloom's
- * `ComposerPanel` plus everything Alia puts around it.
+ * `ComposerPill` plus everything Alia puts around it.
  *
- * Everything the panel draws is Bloom's: the prompt, the add menu, the mode selector (the
- * panel's permission pill, which is the host's power-level selector), the mic, send / stop, the
+ * Everything the pill draws is Bloom's: the prompt, the add menu, the mode selector (the
+ * pill's permission picker, which is the host's power-level selector), the mic, send / stop, the
  * attachment tiles and the status tab. What this adds is what every Alia surface needs the same
  * way: files arriving by paste and drop (read with real progress, retried, refused with a
  * sentence), dictation, the suggestions over the field, and the questions Alia asked docked
@@ -302,7 +302,7 @@ function AliaComposerBody<T extends AliaSuggestion>({
           {labels.dictationRemaining(remainingSeconds)}
         </Text>
       ) : null}
-      <ComposerPanel
+      <ComposerPill
         value={value}
         onValueChange={onValueChange}
         onSubmit={() => onSubmit()}