@stacksjs/defaults 0.75.54 → 0.75.56

package/ai/skills/stacks-chat/SKILL.md

@@ -392,14 +392,17 @@ store in its group container, so Full Disk Access again), never written. Its
 `controller` is `{ archive(names), unarchive(names) }`, given the chat's name
 and formatted number. Message types map onto the inbox shape: captions come
 from the media item's title, contact cards and locations become text, deleted
-messages are `unsent`, group events and calls are `kind: 'event'`. Reactions and
-quoted replies sit in protobuf blobs the driver does not decode, so they are
-absent rather than guessed. Status updates and broadcast lists are not listed.
+messages are `unsent`, group events and calls are `kind: 'event'`. Reactions
+come out of the receipts protobuf (field 7) as `kind: 'reaction'` messages, and
+a reply's `replyToId` is field 5 of the media item's metadata - both read with
+the schema-less `formats/protobuf` reader. Status updates and broadcast lists
+are not listed.
 
 Profile pictures: a person (and a group or server conversation) may carry an
 `avatar` reference; pass it to the optional `driver.avatar(ref)` for the image
 as a `Response`. iMessage reads the contact's photo from Contacts (inline, or
-the store's `_EXTERNAL_DATA` file for larger iCloud photos), WhatsApp the
+the store's `_EXTERNAL_DATA` file for larger iCloud photos) and a group's own
+photo from `chat.properties` (a binary plist, read by `formats/bplist`), WhatsApp the
 pictures it has cached on this Mac (only some - it keeps the ones it showed
 recently), Slack `profile.image_72`, Discord user avatars and server icons.
 The remote ones are fetched only from the provider's own image hosts.

package/ai/skills/stacks-mobile/SKILL.md

@@ -96,6 +96,61 @@ Choose exactly one primary content source:
 Only enable capabilities the product uses. Craft turns enabled capabilities
 into native bridge availability and required iOS privacy descriptions.
 
+## Device search index
+
+`spotlight` says what of the application's own content a device may index, so
+somebody searching their home screen finds a record rather than only finding
+the app:
+
+```ts
+export default {
+  ios: { /* ... */ },
+  spotlight: {
+    kinds: {
+      trail: { slots: 24, route: '/trail/:id', noun: 'Trail' },
+      club: { slots: 8, route: '/club/:id', noun: 'Club' },
+    },
+    // Anything the app donates outside the registry: a Siri phrase, an App Intent.
+    activityTypes: ['favorites', 'trails-near-me'],
+  },
+} satisfies MobileConfig
+```
+
+`slots` is a budget, not a guess. iOS indexes donated `NSUserActivity` objects
+and hands a tapped one back only for an activity type the build declares in
+`Info.plist`, a list fixed at build time — so a type per record id cannot be
+declared at all. Each kind gets that many slots, each slot holds whichever
+record is currently in it, and the oldest donation makes room for the next.
+`buddy build:ios` writes the declarations; an entry the build did not declare
+still appears in Spotlight and merely opens the app wherever it was last, which
+looks like the feature working until somebody taps a result.
+
+Drive it with one index per application:
+
+```ts
+import mobileConfig from '../config/mobile'
+import { createSpotlightIndex, onSpotlightTap } from '@stacksjs/mobile'
+
+export const spotlight = createSpotlightIndex({ kinds: mobileConfig.spotlight.kinds })
+
+await spotlight.index('trail', { id: trail.id, name: trail.name }) // one record
+await spotlight.sync('club', myClubs) // a list that is theirs, most important first
+await spotlight.remove('club', club.id) // left, unsaved, withdrawn from, deleted
+await spotlight.clear() // sign-out: none of it is this person's
+onSpotlightTap(spotlight, route => location.assign(route))
+```
+
+Every call is a no-op that reports as much off a native host, on a build whose
+host predates the bridge, and where the index is turned off (`enabled: false`),
+so a page can donate unconditionally. `spotlight.routeFor(action)` answers a tap
+synchronously for an app that already routes Craft's shortcut events itself.
+
+Index what is the person's — saved, joined, entered — rather than what they
+looked at, wherever the page re-renders on that change: a page that donates on
+every render would put a record straight back the moment they left it. Donating
+the same record twice is free, so an effect over the record is the natural call
+site.
+
 ## Runtime API
 
 ```ts
@@ -201,3 +256,9 @@ physical-device archive. Compile the Android project with Gradle when Android is
 configured. Verify permission prompts, safe-area
 layout, deep links, offline/error states, background transitions, and native
 feedback on device.
+
+A device search index needs its own device check, because nothing about it is
+observable from the generated project: search a record's name from the home
+screen, confirm the entry appears and opens that record rather than the last
+screen, then make it stop being the person's (leave, unsave, withdraw, sign
+out) and confirm it stops being findable.

package/ide/vscode/package.json

@@ -2,7 +2,7 @@
   "publisher": "Stacks",
   "name": "vscode-stacks",
   "displayName": "Stacks",
-  "version": "0.75.54",
+  "version": "0.75.56",
   "description": "Stacks, built into VS Code: stx templates, pickier linting and formatting, encrypted env files, the dev server preview and every buddy command. No other extensions required.",
   "license": "MIT",
   "funding": "https://github.com/sponsors/chrisbbreuer",

package/package.json

@@ -2,7 +2,7 @@
   "name": "@stacksjs/defaults",
   "type": "module",
   "sideEffects": false,
-  "version": "0.75.54",
+  "version": "0.75.56",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/stacksjs/stacks.git",
@@ -55,7 +55,7 @@
   "dependencies": {
     "@iconify-json/f7": "^1.2.2",
     "@iconify-json/hugeicons": "^1.2.35",
-    "@stacksjs/mobile": "^0.75.54",
+    "@stacksjs/mobile": "^0.75.56",
     "@stacksjs/sanitizer": "^0.2.348",
     "ts-qr-codes": "^0.1.8"
   }