@vibes.diy/prompts 9.4.1 → 9.4.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "9.4.1",
+  "version": "9.4.2",
   "type": "module",
   "main": "./index.js",
   "description": "",
@@ -24,9 +24,9 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@adviser/cement": "~0.5.34",
-    "@vibes.diy/call-ai-v2": "^9.4.1",
-    "@vibes.diy/identity": "^9.4.1",
-    "@vibes.diy/use-vibes-types": "^9.4.1",
+    "@vibes.diy/call-ai-v2": "^9.4.2",
+    "@vibes.diy/identity": "^9.4.2",
+    "@vibes.diy/use-vibes-types": "^9.4.2",
     "arktype": "~2.2.3",
     "json-schema-faker": "~0.6.2"
   },

package/system-prompt.md

@@ -436,15 +436,24 @@ docs in your database, and never build follow UI state machines.
   `requestFollowersAccess(): Promise<void>` (the preflight consent path). For a normal app,
   `followersEnabled` is ON by default — sharing with followers just works, so DON'T gate your
   audience UI on it or make users flip a switch first. It is `false` only for the minority:
-  the viewer explicitly turned this app off, chose a never-share standing policy, or the app is
-  marked privacy-sensitive (a diary, a personal tracker), where sharing stays off until a
-  deliberate opt-in. Show a small "open to followers so friends can see your picks" callout
+  the viewer explicitly turned this app off, chose a never-share standing preference, or the app
+  is marked privacy-sensitive (a diary, a personal tracker), where sharing stays off until a
+  deliberate opt-in. Show a small "open to followers so followers can see your picks" callout
   wired to `requestFollowersAccess()` ONLY when `!followersEnabled` (that minority), for an app
   whose whole point is sharing; for a privacy-sensitive app this is the deliberate-consent
   prompt. `requestFollowersAccess()` resolves quietly with no state change (including when the
   app is already enabled, or the viewer already declined/opted out) — never call it in a loop,
   on every render, or more than once per explicit user action. Don't invent a callout an app's
   own privacy doesn't call for.
+- For an explicit visibility control (a settings toggle inside your app), `useSocial()` returns
+  `visibility: "followers" | "private"` (read-only: the effective level for THIS viewer/app —
+  `followersEnabled` is just `visibility !== "private"`) and
+  `setVisibility(level): Promise<void>` to change it. `"followers"` means followers can see;
+  `"private"` turns this app's sharing off for the viewer. Call `setVisibility` only from an
+  explicit user action (a toggle), then re-render from `visibility` — it resolves after the
+  change lands. (`"public"`/world-readable is not settable yet; don't offer it.) Most apps don't
+  need this — the default already shares with followers; reach for it only when the app's own UX
+  wants an in-app privacy switch.
 - To grow the graph, `useSocial()` returns
   `invite(email: string): Promise<"ok" | "rate-limited" | "cancelled">` — asks the PLATFORM to
   email a non-user an invitation to connect with the viewer. The platform shows a consent prompt,