@vibes.diy/prompts 10.6.3 → 10.7.0

package/llms/access.md

@@ -120,33 +120,6 @@ This is especially useful when an app has many databases.
 
 Use `oldDoc` (the previous version of the document) to enforce invariants across updates: `if (oldDoc === null) { /* create-only logic */ }` for new documents, and `if (oldDoc && doc.version <= oldDoc.version) { throw { forbidden: "version must increase" } }` for monotonic versions.
 
-### Per-Database Access Control (`acl` option)
-
-On vibes.diy, `useFireproof` accepts an optional `acl` argument that declares who can read, write, or delete documents in that database. The ACL is stored server-side and enforced on every operation — no separate API call needed.
-Only use the `acl` option when the user explicitly asks for fine-grained access control (or equivalent permission constraints).
-
-```jsx
-// Anyone with a grant can post; only editors can delete
-const { useLiveQuery, database } = useFireproof("announcements", {
-  acl: { write: ["members"], delete: ["editors"] },
-});
-```
-
-**Subject groups** — who each name covers:
-
-| Group        | Who is included                                             |
-| ------------ | ----------------------------------------------------------- |
-| `members`    | owner + editor + viewer + submitter (anyone with any grant) |
-| `editors`    | owner + editor                                              |
-| `submitters` | owner + submitter                                           |
-| `readers`    | owner + editor + viewer                                     |
-
-Owner is always implicitly included — never list `owner` explicitly in an ACL.
-
-Each capability (`read`, `write`, `delete`) is independent. Omitting one falls back to the app-level role gate for that operation. The `acl` is sent once on first database open and persists across sessions (last-write-wins). Only the **app owner** can set ACLs; non-owner apps opening a database with an `acl` option have it silently ignored — the database still opens and works normally.
-
-Other `acl` variants: `useFireproof("drafts", { acl: { read: ["editors"], write: ["editors"], delete: ["editors"] } })` for editors-only space, or omit `acl` entirely to fall back to app-level role gates (existing behavior, always safe).
-
 ## When to emit access.js, and where it goes
 
 The **placement** of `access.js` depends on which turn shape you are in — one-shot whole-app generation vs. incremental scaffold/follow-up edits. Follow the subsection that matches your turn; the other one's ordering is wrong for you and will strand writes.
@@ -369,9 +342,7 @@ App.jsx
 
 ```jsx
 <<<<<<< SEARCH
-  const { useLiveQuery, database } = useFireproof("announcements", {
-    acl: { write: ["members"], delete: ["editors"] },
-  });
+  const { useLiveQuery, database } = useFireproof("comments");
 =======
   const { database, useLiveQuery, access } = useFireproof("comments");
   const { can, me } = useVibe("comments");

package/mcp-footer.md

@@ -21,7 +21,7 @@ Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
 
 ### Claude Code
 
-Add to .claude/settings.json:
+Add to .mcp.json in your project root:
 
 ```json
 {

package/package.json

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