@lotics/cli 0.147.0 → 0.148.0

package/dist/src/cli.js

@@ -46473,6 +46473,8 @@ import { useAiContext } from "@lotics/app-sdk";
 import { Card } from "@lotics/ui/card";
 import { Text } from "@lotics/ui/text";
 import { Button } from "@lotics/ui/button";
+import { BackButton } from "@lotics/ui/back_button";
+import { EmptyState } from "@lotics/ui/empty_state";
 
 // AppRouter makes the app's screens real URLs \u2014 write plain react-router
 // (useNavigate / useParams / <Link>) and it handles both modes. The app owns its
@@ -46539,25 +46541,39 @@ function ItemDetailScreen() {
   // what the app rendered to the member, never a channel for chat to pull app
   // data \u2014 the text lands in the prompt as labeled data (not instructions) and
   // any record refs would act only within the member's own IAM. Pass null to
-  // clear the slot (here: nothing to describe when the item isn't found).
-  useAiContext(
-    "item_detail",
-    item ? { description: \`Viewing item "\${item.name}".\`, data: { id: item.id } } : null,
-  );
+  // clear the slot \u2014 which is what the scaffold does, deliberately.
+  //
+  // WIRE THIS when the screen shows real data:
+  //   useAiContext("item_detail", item ? { description: \`Viewing \${item.name}.\`,
+  //     data: { id: item.id } } : null);
+  //
+  // Left empty because these items are placeholders, and a filled slot is the
+  // one thing here that reaches OUT of the app: it would seed the member's live
+  // chat with a fact about a record that does not exist, invisibly, since
+  // nothing on the screen shows what was pushed.
+  useAiContext("item_detail", null);
   return (
     <Screen>
-      {/* An in-app Back control; navigate(-1) walks the history (the browser Back
-          button walks app screens too). */}
-      <View style={{ alignItems: "flex-start" }}>
-        <Button title="Back" onPress={() => navigate(-1)} />
-      </View>
+      {/* The kit's one go-back control; navigate(-1) walks the history (the
+          browser Back button walks app screens too). Don't hand-roll it: a bare
+          \`<Button title="Back">\` with no \`color\` draws NOTHING at rest \u2014 no
+          ground, no border, no underline \u2014 so its only affordance is a hover
+          wash, which touch and keyboard never see. BackButton also carries its
+          own \`alignSelf\`, so it needs no wrapping View to sit left. */}
+      <BackButton onPress={() => navigate(-1)} />
       <Text size="xl" weight="semibold">{item ? item.name : "Not found"}</Text>
-      <Card>
-        <View style={{ padding: 16, gap: 8 }}>
-          <Text>Detail for item {id}.</Text>
-          <Text color="muted">Reached via in-app navigation, not a host route.</Text>
-        </View>
-      </Card>
+      {/* Every state gets its own content. Swapping only the TITLE left the card
+          below still describing the record the title had just said was missing. */}
+      {item ? (
+        <Card>
+          <View style={{ padding: 16, gap: 8 }}>
+            <Text>Detail for item {id}.</Text>
+            <Text color="muted">Reached via in-app navigation, not a host route.</Text>
+          </View>
+        </Card>
+      ) : (
+        <EmptyState message={"No item with id " + id + "."} />
+      )}
     </Screen>
   );
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/cli",
-  "version": "0.147.0",
+  "version": "0.148.0",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {