@vibes.diy/prompts 14.3.181 → 14.3.184

package/llms/use-vibe.md

@@ -85,13 +85,14 @@ Don't gate management UI on a display flag directly. Encode the rule in `access.
 
 Most apps work the moment they open. Some need their owner to do one thing first — paste a key, save a billing portal, connect an account — and that is a property of the app, not of any one integration, so every app that has it takes the same shape. An app has at most one **Setup** surface, and the backend's verdict decides its state, never a display flag. The integration skills (Stripe, Spotify, YouTube) each contribute one item to it: what the app needs, how the backend checks it, and the linked steps in the provider's own words.
 
-**The backend answers what the app needs and whether each item is done.** A `/setup` route in `backend.js`, called with `apiFetch` so `ctx.userInfo` is set, lists the items — the key is present, the portal is saved, the account is connected — with `done` read from `ctx.secrets` or the connection, and `ready` when every item is done. An item whose verdict costs a provider call (is the portal saved?) is asked on the owner's call alone and kept in a document the backend writes; a visitor's read takes the kept value, so visitor traffic spends nothing of the provider's and a blip there keeps the last verdict. The Setup surface is the owner's alone: the backend decides who the owner is, and non-owners never receive the items. Each step is a link to the exact page in that page's own words, with the vibe's real handle and slug filled in from what the backend hands the client. The route carries `ownerHandle` and `appSlug` from `ctx.appInfo`, so the Settings link (`https://vibes.diy/vibes/mine/<ownerHandle>/<appSlug>/settings`, **Secrets**) and the CLI line (`npx vibes-diy secrets set KEY --vibe <ownerHandle>/<appSlug>`) are copy-ready rather than templates.
+**The backend answers what the app needs and whether each item is done.** A `/setup` route in `backend.js`, called with `apiFetch` so `ctx.userInfo` is set, lists the items — the key is present, the portal is saved, the account is connected — with `done` read from `ctx.secrets`, the connection or `ctx.stripe.status()`, and `ready` when every item is done. An item whose verdict costs a provider call (is the portal saved?) is asked on the owner's call alone and kept in a document the backend writes; a visitor's read takes the kept value, so visitor traffic spends nothing of the provider's and a blip there keeps the last verdict. The Setup surface is the owner's alone: the backend decides who the owner is, and non-owners never receive the items. Each step is a link to the exact page in that page's own words, with the vibe's real handle and slug filled in from what the backend hands the client. The route carries `ownerHandle` and `appSlug` from `ctx.appInfo`, so the Settings link (`https://vibes.diy/vibes/mine/<ownerHandle>/<appSlug>/settings`, **Secrets**) and the CLI line (`npx vibes-diy secrets set KEY --vibe <ownerHandle>/<appSlug>`) are copy-ready rather than templates.
 
 ```js
 // backend.js — the verdict for everyone, the items for the owner alone
 if (url.pathname === "/setup" && request.method === "GET") {
   const owner = ctx.userInfo?.userHandle === ctx.appInfo.ownerHandle;
-  const items = [{ id: "stripe-key", label: "Stripe secret key", done: Boolean(ctx.secrets.STRIPE_SECRET_KEY) }];
+  const stripe = await ctx.stripe.status(); // the stripe skill picks the mode: test until the owner takes this app live
+  const items = [{ id: "stripe-connect", label: "Connect Stripe", done: stripe.test.state === "ready" }];
   const ready = items.every((item) => item.done);
   if (!owner) return json({ ok: true, ready, owner });
   return json({ ok: true, ready, owner, items, ownerHandle: ctx.appInfo.ownerHandle, appSlug: ctx.appInfo.appSlug });
@@ -132,8 +133,8 @@ function SetupScreen({ setup }) {
           <Row gap={2}><Text>{item.label}</Text><Badge tone={item.done ? "up" : "info"}>{item.done ? "Done" : "To do"}</Badge></Row>
           {/* the skill's steps: each one a link to the exact page, in that page's own words */}
           <ol>
-            <li>Open Stripe's <a href="https://dashboard.stripe.com/test/apikeys" target="_blank" rel="noreferrer">API keys page (test mode)</a> and press <b>Reveal test key</b> beside <b>Secret key</b>.</li>
-            <li>Open <a href={`https://vibes.diy/vibes/mine/${vibe}/settings`} target="_blank" rel="noreferrer">this vibe's Settings tab</a>; under <b>Secrets</b>, enter <code>STRIPE_SECRET_KEY</code>, paste the value, and save.</li>
+            <li>Open <a href={`https://vibes.diy/vibes/mine/${vibe}/settings`} target="_blank" rel="noreferrer">this vibe's Settings tab</a> and press <b>Connect Stripe</b> under <b>Payments</b>; Stripe opens its own setup pages.</li>
+            <li>Come back here: the feature unlocks as soon as Stripe says the account is ready.</li>
           </ol>
         </Stack>
       ))}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "14.3.181",
+  "version": "14.3.184",
   "type": "module",
   "main": "./index.js",
   "exports": {
@@ -39,10 +39,10 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@adviser/cement": "~0.5.34",
-    "@vibes.diy/api-types": "14.3.181",
-    "@vibes.diy/call-ai-v2": "14.3.181",
-    "@vibes.diy/identity": "14.3.181",
-    "@vibes.diy/use-vibes-types": "14.3.181",
+    "@vibes.diy/api-types": "14.3.184",
+    "@vibes.diy/call-ai-v2": "14.3.184",
+    "@vibes.diy/identity": "14.3.184",
+    "@vibes.diy/use-vibes-types": "14.3.184",
     "arktype": "~2.2.8",
     "json-schema-faker": "~0.6.3"
   },