openreceive 0.4.23 → 0.4.25

data/skills/integrate-openreceive/references/laravel.md

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/laravel/full.md
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Start the quickstart only once the NWC code is saved, and the LSC code is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.23.
+These directions describe OpenReceive 0.4.25.
 
 Add OpenReceive to a Laravel application — the app you are already working in.
 You do not need a copy of the OpenReceive source: the package is on Packagist
@@ -376,6 +376,7 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/environment-variables.md — every variable, and what is deliberately not one
 - https://openreceive.org/guides/storage.md — the engine tables and the attempt state machine
 - https://openreceive.org/guides/frontend-checkout.md — the drop-in's props, attributes and slots
+- https://openreceive.org/guides/mobile-apps.md — when a mobile app takes the payment: the checkout page it opens, and what the App Store and Google Play allow
 - https://openreceive.org/guides/checkout-ux.md — read before building any custom UI
 - https://openreceive.org/guides/headless-checkout.md — the controller, the display models, refunds
 - https://openreceive.org/guides/provider-registry.md — where the wallet logos and pay
@@ -717,7 +718,9 @@ PHP builds the whole engine again on every request. Under PHP-FPM or Apache,
 that same preflight would then run per request. To avoid that, the package
 caches the wallet's info event in your default cache store for
 `config('openreceive.wallet_info_cache_seconds')` (600). A checkout request
-then costs one relay round trip, not two.
+then costs one relay round trip, not two. The same store keeps the BTC price
+and the swap provider's currencies and rates between requests, so checkout
+routes do not fetch them again.
 
 ### Render the checkout
 

data/skills/integrate-openreceive/references/lovable.md

@@ -3,7 +3,7 @@ This is the full file; follow it from Step 0.
 # OpenReceive agent directions (Lovable)
 
 ```text
-READ THIS FIRST: this file is 25 KB and a summary drops required steps. Read all of it:
+READ THIS FIRST: this file is 26 KB and a summary drops required steps. Read all of it:
 https://openreceive.org/agent-directions/lovable/full.md
 If your fetch tool gave you a summary, fetch that URL again for the full text.
 ```
@@ -17,7 +17,7 @@ If your fetch tool gave you a summary, fetch that URL again for the full text.
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Start Step 1 only once NWC_URI is saved, and LSC_URI_PRIMARY is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.23.
+These directions describe OpenReceive 0.4.25.
 
 Add OpenReceive to this Lovable app: a TanStack Start app on Cloudflare
 Workers, with Lovable Cloud or a connected Supabase project as its database.
@@ -117,7 +117,7 @@ saved or explicitly declined.
 
 ## Step 1 — the packages
 
-Add `@openreceive/http` and `@openreceive/react` at 0.4.23 or newer.
+Add `@openreceive/http` and `@openreceive/react` at 0.4.25 or newer.
 Nothing else: no `pg`, no Postgres driver, no OpenReceive scaffold. Do not
 change the Vite or Wrangler configuration.
 
@@ -148,9 +148,12 @@ every settlement.
   `crypto.randomUUID()` (HttpOnly, Secure, SameSite=Lax, path `/`, one
   year) with `getCookie` and `setCookie` from `@tanstack/react-start/server`,
   then inserts the order with `buyer_token` set to it through `supabaseAdmin`
-  from `@/integrations/supabase/client.server`, and returns the id. If the app
-  creates orders in the browser today, move that insert into this function.
-  Keep the order's user column too, if the app has sign-in.
+  from `@/integrations/supabase/client.server`, and returns the id. Keep the
+  app's order flow as it is: where it creates orders on the server today (a
+  server route a form posts to, or another server function), call this
+  function there, and keep those routes, forms and redirects working. If the
+  app creates orders in the browser today, move that insert into this
+  function. Keep the order's user column too, if the app has sign-in.
 - **The order is unpaid or paid.** Do not copy attempt statuses (`pending`,
   `expired`, `failed`, `attention`) onto it, and do not add a relation to
   `openreceive_payments`.
@@ -408,7 +411,7 @@ idempotent. See Payment storage.
 
 On Supabase the route keeps payments in your Supabase database through its
 HTTPS API, with the project's secret key. There is no `pg` pool. Use
-`@openreceive/*` 0.4.23 or newer:
+`@openreceive/*` 0.4.24 or newer:
 
 ```sh
 npm install @openreceive/http @openreceive/react