@vibes.diy/prompts 14.3.113 → 14.3.114

package/llms/fireproof.md

@@ -23,7 +23,7 @@ Use granular documents, e.g. one document per user action, so saving a form or c
 
 `useLiveQuery` populates and refreshes the UI reactively as data arrives, so you usually render empty states rather than loading spinners. Writes are optimistic and local: `put()`/`save()`/`del()` land in the local replica instantly, and transport or offline failures queue and retry automatically. If the server's access rules reject a synced write, the local optimistic revision converges **server-wins** (it is overwritten by the server's version) — and the **platform** surfaces the reason in a write-fail toast whenever there is one: the app's own `forbidden("…")` text, or the platform's message when a signed-in visitor has no write access to the app (both also reach the app as `writeRejection`, below); a reason-less rejection converges silently. So do **not** wrap plain writes in `try/catch` to show denial errors to the user (a save carrying `_files` is the one exception, covered with the image uploader below); keep the UI reactive to the store (`useLiveQuery`/`useDocument`) so the converged state is the feedback, and gate write surfaces up front with `useVibe(dbName).can.create/edit/delete` so a disallowed action never renders in the first place.
 
-When the server later refuses a write the visitor can act on — a signed-in visitor saving to a private app, say — the platform shows a notice and `useFireproof` hands the app the same reason as `writeRejection` (`{ docId, message }`, or `null` until a save is refused). Render `writeRejection.message` beside the form it came from and call `clearWriteRejection()` when the visitor dismisses it:
+When the server later refuses a write the visitor can act on — a signed-in visitor saving to a private app, say — the platform shows a notice and `useFireproof` hands the app the same reason as `writeRejection` (`{ docId, message, code }`, or `null` until a save is refused). Render `writeRejection.message` beside the form it came from and call `clearWriteRejection()` when the visitor dismisses it:
 
 ```jsx
 function NoteForm({ text }) {
@@ -44,6 +44,28 @@ function NoteForm({ text }) {
 }
 ```
 
+While the app's first build is still finishing, the preview runs on its example records, and saving opens up the moment the build completes. A save in that window comes back as a `writeRejection` with `code: "draft-read-only"` and a friendly ready-made `message`. Treat it as a calm status line: the same quiet `role="status"` note as above (or nothing at all), with the visitor's typed text and selections kept in component state so the next save carries them. The platform clears this `writeRejection` itself the moment saving opens up (and on the next save that lands), so the note goes away on its own:
+
+```jsx
+function AddItem() {
+  const { database, writeRejection } = useFireproof("items");
+  const [text, setText] = useState("");
+  async function add() {
+    const res = await database.put({ type: "item", text });
+    if (res.ok) setText(""); // clear the field once the record is saved
+  }
+  return (
+    <Stack gap={2}>
+      <Field label="Item">{(id, describedBy) => <Input id={id} describedBy={describedBy} value={text} onChange={setText} />}</Field>
+      <Row>
+        <Button type="button" onClick={add}>Add</Button>
+      </Row>
+      {writeRejection?.code === "draft-read-only" && <p role="status">{writeRejection.message}</p>}
+    </Stack>
+  );
+}
+```
+
 ### Basic Example
 
 When the composer is on screen, wire these visible actions in the same build, using the app's own record names. One composer has Add and Ask actions. Add extracts and normalizes facts, saves each record immediately, and shows saved records with edit actions; one item and a pasted batch share this action. Each saved row has Change by sentence: selecting it changes Add to Apply correction, which saves onto that same record id. Ask sends the typed question with the relevant saved records and displays a read-only answer beside the composer. Edit opens the selected row’s populated fields. One parent-owned Undo restores the latest successful creation batch or the previous document from either a sentence correction or a field edit.

package/package.json

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