@vibes.diy/prompts 14.3.42 → 14.3.44

package/llms/backend.md

@@ -251,9 +251,14 @@ const gh = await ctx.github.fetch("/repos/acme/site/issues", { method: "POST", b
   `next`. On the last page the property is absent, not undefined — `"next" in
   page` is `false`.
 - Both reads are read-gated as the acting identity, through the same gate:
-  anonymous `fetch` callers are denied, and in `fetch`/`onChange` a database
-  bound to an access function cannot be read at all (keep those lanes' read
-  databases unbound). In `scheduled` (admin mode) reads are
+  anonymous `fetch` callers are denied, and in `fetch` a database bound to an
+  access function cannot be read at all (keep the fetch lane's read databases
+  unbound, or declare `config.fetch.unfilteredReads`). In `onChange` a bound
+  database reads **filtered to the triggering user's channels** — the same
+  per-reader filter the client's own reads use, so the handler sees exactly
+  what the user who triggered it could see: neighbouring docs for dedup, rank
+  and "don't repeat what's already there" checks, and nothing privileged. In
+  `scheduled` (admin mode) reads are
   **unfiltered** — access-fn-bound databases return every doc, across all users
   and channels. Made for `scheduled` sweeps: read, decide, then `put`/`delete`.
 - The one exception to that last sentence is the declared opt-in above,
@@ -880,6 +885,32 @@ Two rules keep change-reactions sane:
    same-database ping-pong is still wasted work. Different db + dbName guard
    makes loops structurally impossible.
 
+### `onChange` reads what the triggering user could read
+
+A reaction usually needs the set its write joins — the siblings, the existing
+keys, what's already there. `ctx.db.query` and `ctx.db.get` on a bound
+database return exactly the docs in the triggering user's channels, through
+the same per-reader filter the client's own reads use. Nothing privileged
+ever comes back: a doc the triggerer couldn't open stays invisible, and reads
+page like any other query (walk `next` to exhaustion).
+
+```js
+export async function onChange(event, ctx) {
+  if (event.dbName !== "links" || event.deleted) return;
+  // What did sibling drafts already say about this link? Only docs the
+  // triggering user could read come back — a private sibling stays hidden.
+  // Walk every page to exhaustion: a fully-filtered page still carries `next`,
+  // so stopping on an empty page would miss a sibling on a later one.
+  let after = null;
+  do {
+    const page = await ctx.db.query({ db: "drafts", field: "linkId", key: event.doc.linkId, limit: 100, after });
+    if (page.some((d) => d.angle === event.doc.angle)) return; // already covered
+    after = page.next;
+  } while (after);
+  await ctx.db.put({ _id: "draft-" + event.docId, linkId: event.doc.linkId, angle: event.doc.angle }, { db: "drafts" });
+}
+```
+
 ### Jobs that finish even when a run crashes
 
 **A job that survives a crash carries its status, its claim and its lease on the document.**
@@ -903,8 +934,9 @@ sweep's `query` row), then `put` the next status with `ifRev: doc._rev`. A
   `attempts + 1`.
 - The finish carries the same `claimId`, and `access.js` refuses a `done`
   whose `claimId` differs from `oldDoc.claimId`. A slow run's lease can be
-  taken back and the job claimed again while it works, and `onChange` cannot
-  read the job back, so the token is how the finish knows it still owns it.
+  taken back and the job claimed again while it works; the second claim's
+  fresh `claimId` is what makes the first run's finish refuse instead of
+  overwrite.
 - The sweep releases an expired lease with `ifRev: job._rev` from its query,
   so it never overwrites a job that finished between the read and the write.
 - A lost claim returns rather than throws: a redelivered event carries the doc

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibes.diy/prompts",
-  "version": "14.3.42",
+  "version": "14.3.44",
   "type": "module",
   "main": "./index.js",
   "exports": {
@@ -37,9 +37,9 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@adviser/cement": "~0.5.34",
-    "@vibes.diy/call-ai-v2": "14.3.42",
-    "@vibes.diy/identity": "14.3.42",
-    "@vibes.diy/use-vibes-types": "14.3.42",
+    "@vibes.diy/call-ai-v2": "14.3.44",
+    "@vibes.diy/identity": "14.3.44",
+    "@vibes.diy/use-vibes-types": "14.3.44",
     "arktype": "~2.2.3",
     "json-schema-faker": "~0.6.3"
   },