@ateam-ai-mobile/plugin-runtime 0.1.5 → 0.1.8

package/src/sdk/index.ts

@@ -5,9 +5,9 @@
  */
 
 // Registration API
-export { register, registerService } from './registration';
-import { register, registerService } from './registration';
-export const PluginSDK = { register, registerService } as const;
+export { register, registerService, registerTools } from './registration';
+import { register, registerService, registerTools } from './registration';
+export const PluginSDK = { register, registerService, registerTools } as const;
 
 // Types
 export type {
@@ -24,9 +24,23 @@ export type {
   ConnectivityAPI,
   FileSystemAPI,
   CookiesAPI,
+  WebViewCookie,
   SharingAPI,
   ScannerAPI,
   NfcAPI,
+  BluetoothAPI,
+  BluetoothDevice,
+  VisionAPI,
+  VisionText,
+  VisionLabel,
+  VisionObject,
+  VisionFrameQuality,
+  MapsAPI,
+  MapsCoordinate,
+  MapsAddress,
+  MapsPlace,
+  MapsRoute,
+  MapsRouteStep,
   BiometricsAPI,
   BiometricsAPIv2,
   NativeCapabilities,
@@ -36,8 +50,29 @@ export type {
   RegisteredPlugin,
   RegisteredUIPlugin,
   RegisteredServicePlugin,
+  RegisteredToolsPlugin,
+  DeviceToolContext,
+  DeviceToolDefinition,
+  DeviceToolFn,
 } from './types';
 
+// Voice — the live conversational SESSION surface (props.voice).
+export type {
+  VoiceAPI,
+  VoiceState,
+  VoiceSnapshot,
+  VoiceTranscriptEntry,
+  VoiceStartOptions,
+  VoicePersona,
+  VoiceEvent,
+  VoiceSubscription,
+  VoiceCaller,
+  VoiceSessionProvider,
+} from './voice';
+// The privileged platform caller (a value) — the host injects the owner-aware
+// provider and its own surfaces call it as this caller. See VoiceSessionProvider.
+export { PLATFORM_VOICE_CALLER } from './voice';
+
 // RN primitives (plugins import from the SDK, not from react-native)
 export {
   View,
@@ -72,5 +107,9 @@ export {
 } from './components';
 
 // Theme + API hooks
+// Showing the camera is a COMPONENT, not a native module handed to bundles —
+// one door, one lock. See CameraPreview.tsx for why.
+export { CameraPreview } from './CameraPreview';
+export type { CameraPreviewProps } from './CameraPreview';
 export { usePluginTheme, setPluginThemeColors } from './usePluginTheme';
 export { useApi } from './useApi';

package/src/sdk/registration.ts

@@ -3,29 +3,69 @@
  * Solution developers use these to register their plugins.
  */
 import type {
+  DeviceToolDefinition,
   NativeCapabilities,
   PluginHooks,
   PluginProps,
   RegisteredUIPlugin,
   RegisteredServicePlugin,
+  RegisteredToolsPlugin,
 } from './types';
+import type { DeviceBridgeDomain } from './device-state';
 
 /**
  * Register a UI or hybrid plugin (has a visual component).
+ *
+ * `tools` is optional: a plugin may ship UI and local tools together. Tools are
+ * picked up when the bundle loads, independently of whether the UI is mounted.
  */
 export function register(
   id: string,
   config: {
     type?: 'ui' | 'hybrid';
     capabilities?: NativeCapabilities;
+    /** L3 DeviceState domains this plugin's UI reads via props.deviceState (e.g.
+     *  ['spatial','visual']). Carried through so a HOST-registered plugin (no
+     *  server manifest) can declare its domains — resolvePluginRuntimeProps reads
+     *  this as the trusted source when there is no manifest. Dropping it here left
+     *  every registered UI plugin with no L3, silently. Mirrors registerTools. */
+    stateDomains?: DeviceBridgeDomain[];
     Component: React.FC<PluginProps>;
+    tools?: DeviceToolDefinition[];
   },
 ): RegisteredUIPlugin {
   return {
     id,
     type: config.type || 'ui',
     capabilities: config.capabilities,
+    stateDomains: config.stateDomains,
     Component: config.Component,
+    tools: config.tools,
+  };
+}
+
+/**
+ * Register a tools-only plugin — a `tools/` section with no UI at all.
+ *
+ * Nothing here mounts. The tools become callable as soon as the bundle is
+ * evaluated, and stay callable with nothing of the plugin on screen.
+ */
+export function registerTools(
+  id: string,
+  config: {
+    capabilities?: NativeCapabilities;
+    /** L3 DeviceState domains the tools read via ctx.deviceState (e.g. ['visual']).
+     *  For a remote bundle the MANIFEST grants them — see RegisteredToolsPlugin. */
+    stateDomains?: DeviceBridgeDomain[];
+    tools: DeviceToolDefinition[];
+  },
+): RegisteredToolsPlugin {
+  return {
+    id,
+    type: 'tools',
+    capabilities: config.capabilities,
+    stateDomains: config.stateDomains,
+    tools: config.tools,
   };
 }