@vibes.diy/prompts 5.2.2 → 5.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "5.2.2",
+  "version": "5.3.1",
   "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": "^5.2.2",
-    "@vibes.diy/identity": "^5.2.2",
-    "@vibes.diy/use-vibes-types": "^5.2.2",
+    "@vibes.diy/call-ai-v2": "^5.3.1",
+    "@vibes.diy/identity": "^5.3.1",
+    "@vibes.diy/use-vibes-types": "^5.3.1",
     "arktype": "~2.2.3",
     "json-schema-faker": "~0.6.2"
   },

package/system-prompt-initial.md

@@ -188,6 +188,17 @@ docs in your database, and never build follow UI state machines.
   small callout when `!followersEnabled` — "open to followers so friends can see your picks" —
   wired to this action; an app that's inherently private (a diary, a personal tracker) renders
   nothing here at all. Don't invent a callout an app's own privacy doesn't call for.
+- 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,
+  so you never send silently. It resolves `"ok"` when queued — this NEVER reveals whether the
+  address is already a user, was already invited, or opted out, so don't build UI that implies
+  delivery or "already invited"; `"rate-limited"` when the viewer hits their own daily cap
+  (back off gracefully — "you're inviting a bit fast, try again later"); `"cancelled"` when they
+  dismiss the prompt. Call it ONLY from an explicit user action (a form submit / button), one
+  email per action — never in a loop, on every render, or to bulk-blast a list. Accepting makes
+  you both follow each other. Copy: "invite a friend to connect" — never imply you can tell
+  whether they're already on Vibes.
 
 **`access.js` must be one self-contained exported function.** The server extracts and evaluates ONLY the exported function's source — module-scope code (a `const CHANNEL = "team:hub"` above the function, a shared helper, an import) does not exist at runtime, and referencing it throws `ReferenceError: 'CHANNEL' is not defined` on every write, breaking the app. Declare constants and helpers inside the function body, as every worked example here does.
 

package/system-prompt.md

@@ -396,6 +396,17 @@ docs in your database, and never build follow UI state machines.
   small callout when `!followersEnabled` — "open to followers so friends can see your picks" —
   wired to this action; an app that's inherently private (a diary, a personal tracker) renders
   nothing here at all. Don't invent a callout an app's own privacy doesn't call for.
+- 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,
+  so you never send silently. It resolves `"ok"` when queued — this NEVER reveals whether the
+  address is already a user, was already invited, or opted out, so don't build UI that implies
+  delivery or "already invited"; `"rate-limited"` when the viewer hits their own daily cap
+  (back off gracefully — "you're inviting a bit fast, try again later"); `"cancelled"` when they
+  dismiss the prompt. Call it ONLY from an explicit user action (a form submit / button), one
+  email per action — never in a loop, on every render, or to bulk-blast a list. Accepting makes
+  you both follow each other. Copy: "invite a friend to connect" — never imply you can tell
+  whether they're already on Vibes.
 
 **`access.js` must be one self-contained exported function.** The server extracts and evaluates ONLY the exported function's source — module-scope code (a `const CHANNEL = "team:hub"` above the function, a shared helper, an import) does not exist at runtime, and referencing it throws `ReferenceError: 'CHANNEL' is not defined` on every write, breaking the app. Declare constants and helpers inside the function body, as every worked example here does.