@ggui-ai/mcp-apps-react-native 0.11.0 → 0.12.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ggui-ai/mcp-apps-react-native",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "description": "React Native SDK for ggui — components and hooks for embedding agent-generated UIs in mobile apps.",
   "keywords": [
     "ggui",
@@ -58,9 +58,9 @@
   },
   "dependencies": {
     "@modelcontextprotocol/ext-apps": "^1.7.2",
-    "@ggui-ai/design": "0.11.0",
-    "@ggui-ai/protocol": "0.11.0",
-    "@ggui-ai/iframe-runtime": "0.11.0"
+    "@ggui-ai/iframe-runtime": "0.12.0",
+    "@ggui-ai/protocol": "0.12.0",
+    "@ggui-ai/design": "0.12.0"
   },
   "devDependencies": {
     "@modelcontextprotocol/sdk": "^1.27.0",

package/src/McpAppIframe/dispatch.ts

@@ -164,7 +164,12 @@ export async function dispatchHostBridgeRequest(
         // `define`), and a hand-maintained literal would silently drift
         // from the published version at every release.
         hostInfo: { name: 'ggui-react-native', version: 'unstamped' },
-        hostCapabilities: {},
+        // Truthful positive advertisement (kit R2 grade, ggui#600 OPEN
+        // FINDING closed): a wired tools/call relay advertises
+        // `serverTools` so the runtime never spends a failed user
+        // gesture probing a capability the host actually has.
+        hostCapabilities:
+          ctx.onToolCall !== undefined ? { serverTools: {} } : {},
         hostContext: {
           locale: ctx.locale,
           containerDimensions: ctx.containerDimensions,

package/src/theme/ThemeProvider.tsx

@@ -93,9 +93,33 @@ export interface ThemeProviderProps {
   children: ReactNode;
 }
 
+/**
+ * TERMINAL CONSUMER of the theme-mode ladder (adversarial-cycle
+ * ruling, ggui#598 leg 4): the RN provider paints the NATIVE chrome
+ * around the WebView — there is no downstream layer left to fill an
+ * absent opinion, and React Native must render with SOME concrete
+ * scheme. The `?? 'light'` here is therefore the documented
+ * terminal-consumer default (the same posture as the design package's
+ * css-tokens terminal default), NOT a mid-ladder defaulting: it fires
+ * only after the embedder's explicit prop AND the OS scheme are both
+ * absent (`useColorScheme()` → null, rare). Mid-ladder code — anything
+ * with a layer below it — must never default; it delegates to
+ * `@ggui-ai/protocol/integrations/theme-binding` and lets absence
+ * propagate (the composition law).
+ *
+ * @internal — exported for the precedence pin; production caller is
+ *   `ThemeProvider`.
+ */
+export function resolveNativeScheme(
+  prop: 'light' | 'dark' | undefined,
+  system: 'light' | 'dark' | null | undefined,
+): 'light' | 'dark' {
+  return prop ?? system ?? 'light';
+}
+
 export function ThemeProvider({ colorScheme: colorSchemeProp, children }: ThemeProviderProps) {
   const systemScheme = useColorScheme();
-  const effectiveScheme = colorSchemeProp ?? systemScheme ?? 'light';
+  const effectiveScheme = resolveNativeScheme(colorSchemeProp, systemScheme);
   const [reduceMotionEnabled, setReduceMotionEnabled] = useState(false);
 
   useEffect(() => {