@vibes.diy/prompts 14.3.164 → 14.3.166

package/llms/backend.md

@@ -203,7 +203,8 @@ const routes = await ctx.github.routes(); // [{ repo, accountLogin, binderHandle
   </a>;
   ```
 
-  The owner goes straight to GitHub to pick repositories. By default only the
+  The owner goes straight to GitHub to sign in, then ticks the repositories
+  this vibe gets (each vibe gets only the ones ticked for it). By default only the
   owner may connect one; to let **visitors** connect their own repositories (a
   PR reviewer, a repo dashboard anyone can use), declare it in `backend.js`:
 

package/llms/github.md

@@ -3,7 +3,7 @@
 An app that works with somebody's GitHub repo — answers its pull requests,
 sorts its issues, reads its files, shows its commits — connects that repo in
 one click through the **vibes.diy GitHub App**. The person presses Connect,
-picks repos on GitHub's own screen, and lands back in your app. From then on
+ticks the repos this app gets on a vibes.diy page, and lands back in your app. From then on
 `backend.js` reads and writes those repos with `ctx.github.fetch`, and GitHub's
 events for them arrive at your `/_api/github-webhook` route.
 
@@ -72,7 +72,9 @@ import { buildGithubInstallUrl } from "use-vibes";
 
 The app's owner goes straight to GitHub. A visitor first sees the platform's
 consent page quoting your `why`; its Continue button carries the visitor on to
-GitHub's install screen, where they pick the repos. **The platform builds every
+GitHub to sign in (and add the GitHub App if it is new to them), then to a
+vibes.diy page where they tick the repos THIS app gets — nothing starts ticked,
+so each app gets exactly the repos chosen for it. **The platform builds every
 step after `/github/install` itself, so the app's one link is
 `buildGithubInstallUrl()`** — GitHub's own install page is reached only through
 that door. When the new tab finishes, the person comes back to the app's tab,
@@ -96,7 +98,9 @@ await ctx.github.fetch(`/repos/${repo}/pulls/${number}/reviews`, {
 
 `ctx.github.fetch` attaches the App's credential itself, so a repo call carries only its path, method and body.
 `path` starts at `/`: any `/repos/{owner}/{repo}/…` path for a repo connected to
-this app, plus `/installation/repositories`. Methods are GET, POST, PUT, PATCH
+this app, plus `/installation/repositories`, which lists exactly the repos
+connected to this app. **An app sees only the repos connected to it**, so build
+every repo list from `routes()` or that listing. Methods are GET, POST, PUT, PATCH
 and DELETE; an object `body` is sent as JSON. It resolves a normal `Response`
 (GitHub's own 404 or 422 included — read `res.ok` and `res.status`), and it
 rejects with an `Error` whose `err.reason` names what happened:
@@ -553,12 +557,18 @@ channel.
   conversation. Build on those. Other writes (labels, issue comments, check
   runs) may answer `permission_not_granted`; record that reason on the
   person's record and show it, so they see exactly what happened.
-- **One repo connects to one app.** A repo already connected to another app
-  answers the person on the connect screen with "Already connected" — say so on
-  your page near the Connect button, so it reads as expected.
+- **Each app gets the repos chosen for it.** The person ticks repos per app, and
+  each app's connection stands on its own. One repo can feed up to ten apps,
+  each hearing its deliveries with its own connector. While that switches on, a
+  repo another app already has is left out with a note to try again soon. Say
+  near the Connect button that the person picks which repos this app gets.
+- **Connecting a repo takes write access to it on GitHub.** The picker offers
+  the repos the person can push to, and shows the rest greyed out. Suggest that
+  someone with read-only access ask a maintainer to connect the repo.
 - **Repo names are case-insensitive on GitHub.** Lower-case them in `_id`s and
   comparisons, as the example does, and keep GitHub's spelling for display.
-- **Disconnecting happens on GitHub**, in the person's installed GitHub Apps
-  settings.
+- **Taking a repo off this app:** the person presses Connect again and unticks
+  it; their other apps keep it. Removing the GitHub App on GitHub disconnects
+  the repo from every app.
 - More on `ctx` — `ctx.db`, `ctx.log`, `ifRev`, `apiFetch` — lives in the
   `backend` skill.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "14.3.164",
+  "version": "14.3.166",
   "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.164",
-    "@vibes.diy/call-ai-v2": "14.3.164",
-    "@vibes.diy/identity": "14.3.164",
-    "@vibes.diy/use-vibes-types": "14.3.164",
+    "@vibes.diy/api-types": "14.3.166",
+    "@vibes.diy/call-ai-v2": "14.3.166",
+    "@vibes.diy/identity": "14.3.166",
+    "@vibes.diy/use-vibes-types": "14.3.166",
     "arktype": "~2.2.6",
     "json-schema-faker": "~0.6.3"
   },