openreceive 0.4.19 → 0.4.21

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 69ebcc5498ead076761f4bc0fc6b6d6d5033bd7d545d8205f1a506158e245aec
-  data.tar.gz: bcd3dc96c037672bd91b92670404cdddae35092e2203a8dc9bd6609b476d4d4e
+  metadata.gz: dfeec42ce821ad2ab73b5140eb1959f76f4125c34f26bfd214cc0e68ef507a00
+  data.tar.gz: '09f6e1227799a8d50cab35b0b2e69d4eb6509e55f4e6cbbff9e5067c50fb9b06'
 SHA512:
-  metadata.gz: d1496080f84486058630a54707199070930ec5e68dfc13da251ef6a8e6ae71dd2ff33d073b7609c83f50be576753c8b5516060d936a9c36e05b97204309bd48d
-  data.tar.gz: fbfa6d7bd3fd06b2f08ceef369c4cd82051e14ecaf38c2eadaafbf4bcf9d1d9cc554a0e28d6fb7e8c55c4ce5917dd2040f8adf41efc559cc9fec4667637592fe
+  metadata.gz: 0bc687a6d13e167aa2ad2a9dbfc1286058177be57a245424e8ad8e0e911631579296b1520c3fa4876baca6562570b3fdeaadc3fd49576c49752102a72f939bc6
+  data.tar.gz: 64ab63dda22aafcac83e0b831ebc3ab17b441145eb07250516e2de2c8141eb7ebeb4cd812ac274fe1427df1c94e96fe00ec45b2b94c1aac47c89a07aa57b5d6b

data/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.4.21 - 2026-10-09
+
+Release with the complete 0.4.21 package family. The bundled agent skills'
+directions now end on a closing message of at most five lines that keeps the
+test order and names the payment methods it offers, without calling a coin
+unavailable over a swap minimum. No Ruby runtime changes from 0.4.20.
+
+## 0.4.20 - 2026-10-09
+
+Release with the complete 0.4.20 package family. The bundled agent skills now
+describe the checkout stylesheet's rules as low specificity rather than zero:
+inside the checkout they carry one attribute, so a host page's Tailwind
+utilities cannot rearrange it. No Ruby runtime changes from 0.4.19.
+
 ## 0.4.19 - 2026-10-07
 
 Release with the complete 0.4.19 package family. The bundled agent skills link

data/lib/openreceive/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module OpenReceive
-  VERSION = "0.4.19"
+  VERSION = "0.4.21"
 end

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/btcpay/full.md
 - Never tick the spend-capable override to make a save succeed.
 - Do not suggest rotating or revoking a code because it was pasted here.
 
-These directions describe OpenReceive 0.4.19.
+These directions describe OpenReceive 0.4.21.
 
 Connect a BTCPay Server store to a receive-only NWC wallet with the OpenReceive
 plugin, and optionally let payers pay BTCPay invoices with USDT, USDC, ETH or

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

@@ -3,7 +3,7 @@ This is the full file; follow it from Step 0.
 # OpenReceive agent directions (Django)
 
 ```sh
-# READ THIS FIRST: this file is 43 KB and a summary drops required steps. Download it whole:
+# READ THIS FIRST: this file is 44 KB and a summary drops required steps. Download it whole:
 curl -fsSL https://openreceive.org/agent-directions/django/full.md
 # Skip the download only if you already have all of it: pasted, read from disk or fetched raw.
 ```
@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/django/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.19.
+These directions describe OpenReceive 0.4.21.
 
 Add OpenReceive to a Django project — the app you are already working in. You
 do not need a copy of the OpenReceive source: the Python package is on PyPI
@@ -167,8 +167,15 @@ mark an order paid, and do not look for a way to (a wallet control port, a
 test endpoint, another wallet). If the user wants a real settlement test, they
 pay on that link from their own wallet, and `on_paid` marks the order paid.
 
-Setup ends here. Say "Setup is finished" in one message, with the link and
-what to check. Do not offer more work or end the message on a question.
+Setup ends here. Say "Setup is finished" in one message of at most five
+lines, with the link and what to check. Do not list what changed, offer more
+work, or end the message on a question.
+
+- The link is to a real unpaid order. Keep that order; do not delete it.
+- Name the methods it offers: Bitcoin, plus USDT, USDC, ETH and SOL when
+  `LSC_URI_PRIMARY` is saved. Never say a coin will not work or will not be
+  offered. Swap minimums apply per order, and a coin whose minimum is above an
+  order's total says so on its own tile.
 
 ## Non-negotiables
 
@@ -352,6 +359,7 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/authorization.md — before you write `authorize`
 - 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/supabase.md — when the database is Supabase: its pooler, its certificate, and locking the tables away from its Data API
 - https://openreceive.org/guides/frontend-checkout.md — the drop-in's props, attributes and slots
 - 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
@@ -690,7 +698,7 @@ manage.py openreceive_doctor                        # the same, for humans; neve
 Serve the compiled `styles.css` without Tailwind processing. Either import it
 from JavaScript (with a CSS-capable bundler) or use a plain
 `<link rel="stylesheet">`. Do not `@import` it into your Tailwind entry. Its
-rules have zero specificity, so your own styles can override checkout styles.
+rules have low specificity, so your own styles can override checkout styles.
 Scoping does not prevent that.
 
 The app serves JSON checkout routes only. Your template does the rendering. Any

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/fastapi/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.19.
+These directions describe OpenReceive 0.4.21.
 
 Add OpenReceive to a FastAPI application — the app you are already working in.
 You do not need a copy of the OpenReceive source: the engine is on PyPI
@@ -161,8 +161,15 @@ mark an order paid, and do not look for a way to (a wallet control port, a
 test endpoint, another wallet). If the user wants a real settlement test, they
 pay on that link from their own wallet, and `on_paid` marks the order paid.
 
-Setup ends here. Say "Setup is finished" in one message, with the link and
-what to check. Do not offer more work or end the message on a question.
+Setup ends here. Say "Setup is finished" in one message of at most five
+lines, with the link and what to check. Do not list what changed, offer more
+work, or end the message on a question.
+
+- The link is to a real unpaid order. Keep that order; do not delete it.
+- Name the methods it offers: Bitcoin, plus USDT, USDC, ETH and SOL when
+  `LSC_URI_PRIMARY` is saved. Never say a coin will not work or will not be
+  offered. Swap minimums apply per order, and a coin whose minimum is above an
+  order's total says so on its own tile.
 
 ## Non-negotiables
 
@@ -351,6 +358,7 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/authorization.md — before you write `authorize`
 - https://openreceive.org/guides/environment-variables.md — every variable, and what is deliberately not one
 - https://openreceive.org/guides/storage.md — the payment tables and the attempt state machine
+- https://openreceive.org/guides/supabase.md — when the database is Supabase: its pooler, its certificate, and locking the tables away from its Data API
 - https://openreceive.org/guides/frontend-checkout.md — the drop-in's props, attributes and slots
 - 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
@@ -590,7 +598,7 @@ rule applies only inside what OpenReceive renders.
 Serve the compiled `styles.css` without Tailwind processing. Import it from
 JavaScript if your bundler handles CSS, or use a plain
 `<link rel="stylesheet">`. Do not `@import` it into your app's Tailwind entry.
-Its rules have zero specificity, so your page's styles can override checkout
+Its rules have low specificity, so your page's styles can override checkout
 styles. Scoping does not prevent that.
 
 `<Checkout>` is complete as rendered. It already shows the `description` from

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/fastify/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.19.
+These directions describe OpenReceive 0.4.21.
 
 Add OpenReceive to a Fastify application — the app you are already working in.
 You do not need a copy of the OpenReceive source: the packages are on npm, and
@@ -144,6 +144,8 @@ The quickstart is done when
 `npx openreceive doctor --db <file-or-url> --url <app url>` is clean and this
 app serves the checkout page for one of its orders. Doctor names any failed
 check and exits nonzero; fix it before going on.
+Doctor reads `.env` itself. Never source it into a shell: the `&` in a
+code splits the value and prints the pieces.
 
 Give the user that checkout link. The browser check in the quickstart's step 6
 (payment-method icons, wallet logos, a pay tutorial) is theirs: tell them what
@@ -154,8 +156,15 @@ mark an order paid, and do not look for a way to (a wallet control port, a
 test endpoint, another wallet). If the user wants a real settlement test, they
 pay on that link from their own wallet, and `onPaid` marks the order paid.
 
-Setup ends here. Say "Setup is finished" in one message, with the link and
-what to check. Do not offer more work or end the message on a question.
+Setup ends here. Say "Setup is finished" in one message of at most five
+lines, with the link and what to check. Do not list what changed, offer more
+work, or end the message on a question.
+
+- The link is to a real unpaid order. Keep that order; do not delete it.
+- Name the methods it offers: Bitcoin, plus USDT, USDC, ETH and SOL when
+  `LSC_URI_PRIMARY` is saved. Never say a coin will not work or will not be
+  offered. Swap minimums apply per order, and a coin whose minimum is above an
+  order's total says so on its own tile.
 
 ## Non-negotiables
 
@@ -335,6 +344,7 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/authorization.md — before you write `authorize`
 - https://openreceive.org/guides/environment-variables.md — every variable, and what is deliberately not one
 - https://openreceive.org/guides/storage.md — the payment tables and the attempt state machine
+- https://openreceive.org/guides/supabase.md — when the database is Supabase: its pooler, its certificate, and locking the tables away from its Data API
 - https://openreceive.org/guides/node-orms.md — recipes for Prisma, Drizzle, Knex, TypeORM, Sequelize
 - https://openreceive.org/guides/frontend-checkout.md — the drop-in's props, attributes and slots
 - https://openreceive.org/guides/checkout-ux.md — read before building any custom UI
@@ -597,7 +607,7 @@ rule applies only inside what OpenReceive renders.
 Serve the compiled `styles.css` without Tailwind processing. Import it from
 JavaScript if your bundler handles CSS, or use a plain
 `<link rel="stylesheet">`. Do not `@import` it into your app's Tailwind entry.
-Its rules have zero specificity, so your page's styles can override checkout
+Its rules have low specificity, so your page's styles can override checkout
 styles. Scoping does not prevent that.
 
 `<Checkout>` is complete as rendered. It already shows the `description` from

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.19.
+These directions describe OpenReceive 0.4.21.
 
 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
@@ -158,8 +158,15 @@ mark an order paid, and do not look for a way to (a wallet control port, a
 test endpoint, another wallet). If the user wants a real settlement test, they
 pay on that link from their own wallet, and `onPaid` marks the order paid.
 
-Setup ends here. Say "Setup is finished" in one message, with the link and
-what to check. Do not offer more work or end the message on a question.
+Setup ends here. Say "Setup is finished" in one message of at most five
+lines, with the link and what to check. Do not list what changed, offer more
+work, or end the message on a question.
+
+- The link is to a real unpaid order. Keep that order; do not delete it.
+- Name the methods it offers: Bitcoin, plus USDT, USDC, ETH and SOL when
+  `LSC_URI_PRIMARY` is saved. Never say a coin will not work or will not be
+  offered. Swap minimums apply per order, and a coin whose minimum is above an
+  order's total says so on its own tile.
 
 ## Non-negotiables
 
@@ -668,7 +675,7 @@ then costs one relay round trip, not two.
 Serve the compiled `styles.css` without Tailwind processing. Either import it
 from JavaScript (with a CSS-capable bundler) or use a plain
 `<link rel="stylesheet">`. Do not `@import` it into your Tailwind entry. Its
-rules have zero specificity, so your own styles can override checkout styles.
+rules have low specificity, so your own styles can override checkout styles.
 Scoping does not prevent that.
 
 The engine serves JSON checkout routes only. Your view does the rendering. Any

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

@@ -3,7 +3,7 @@ This is the full file; follow it from Step 0.
 # OpenReceive agent directions (Next.js)
 
 ```sh
-# READ THIS FIRST: this file is 38 KB and a summary drops required steps. Download it whole:
+# READ THIS FIRST: this file is 39 KB and a summary drops required steps. Download it whole:
 curl -fsSL https://openreceive.org/agent-directions/next/full.md
 # Skip the download only if you already have all of it: pasted, read from disk or fetched raw.
 ```
@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/next/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.19.
+These directions describe OpenReceive 0.4.21.
 
 Add OpenReceive to a Next.js App Router application — the app you are already
 working in. You do not need a copy of the OpenReceive source: the packages are
@@ -149,6 +149,8 @@ The quickstart is done when
 `npx openreceive doctor --db <file-or-url> --url <app url>` is clean and this
 app serves the checkout page for one of its orders. Doctor names any failed
 check and exits nonzero; fix it before going on.
+Doctor reads `.env.local` itself. Never source it into a shell: the `&` in a
+code splits the value and prints the pieces.
 
 Give the user that checkout link. The browser check in the quickstart's step 6
 (payment-method icons, wallet logos, a pay tutorial) is theirs: tell them what
@@ -159,8 +161,15 @@ mark an order paid, and do not look for a way to (a wallet control port, a
 test endpoint, another wallet). If the user wants a real settlement test, they
 pay on that link from their own wallet, and `onPaid` marks the order paid.
 
-Setup ends here. Say "Setup is finished" in one message, with the link and
-what to check. Do not offer more work or end the message on a question.
+Setup ends here. Say "Setup is finished" in one message of at most five
+lines, with the link and what to check. Do not list what changed, offer more
+work, or end the message on a question.
+
+- The link is to a real unpaid order. Keep that order; do not delete it.
+- Name the methods it offers: Bitcoin, plus USDT, USDC, ETH and SOL when
+  `LSC_URI_PRIMARY` is saved. Never say a coin will not work or will not be
+  offered. Swap minimums apply per order, and a coin whose minimum is above an
+  order's total says so on its own tile.
 
 ## Non-negotiables
 
@@ -344,6 +353,7 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/authorization.md — before you write `authorize`
 - https://openreceive.org/guides/environment-variables.md — every variable, and what is deliberately not one
 - https://openreceive.org/guides/storage.md — the payment tables and the attempt state machine
+- https://openreceive.org/guides/supabase.md — when the database is Supabase: its pooler, its certificate, and locking the tables away from its Data API
 - https://openreceive.org/guides/node-orms.md — recipes for Prisma, Drizzle, Knex, TypeORM, Sequelize
 - https://openreceive.org/guides/frontend-checkout.md — the drop-in's props, attributes and slots
 - https://openreceive.org/guides/checkout-ux.md — read before building any custom UI
@@ -361,6 +371,7 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/api-reference.md — every route, option and error code
 - https://openreceive.org/guides/custom-checkout-route.md — advanced: replacing the shipped adapter's routes with your own
 - https://openreceive.org/guides/react-material-ui-recipe.md — a worked custom UI on a component library
+- https://openreceive.org/guides/tanstack-start-recipe.md — the same handler as a TanStack Start server route, if this app is TanStack Start after all
 - https://openreceive.org/guides.md — the index, if what you need is not above
 
 Questions, or a problem with the library itself:
@@ -647,7 +658,7 @@ scoped: every rule applies only inside what OpenReceive renders. You need no
 
 Serve the compiled `styles.css` without Tailwind processing: import it from
 JavaScript (with a CSS-capable bundler) or use a plain `<link rel="stylesheet">`.
-Do not `@import` it into the host Tailwind entry. Its zero-specificity rules
+Do not `@import` it into the host Tailwind entry. Its low-specificity rules
 allow host styles to override checkout styles; scoping does not prevent that.
 
 `<Checkout>` is complete as rendered. It already shows the `description` from

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

@@ -3,7 +3,7 @@ This is the full file; follow it from Step 0.
 # OpenReceive agent directions (Node.js)
 
 ```sh
-# READ THIS FIRST: this file is 34 KB and a summary drops required steps. Download it whole:
+# READ THIS FIRST: this file is 35 KB and a summary drops required steps. Download it whole:
 curl -fsSL https://openreceive.org/agent-directions/node/full.md
 # Skip the download only if you already have all of it: pasted, read from disk or fetched raw.
 ```
@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/node/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.19.
+These directions describe OpenReceive 0.4.21.
 
 Add OpenReceive to a Node application — the app you are already working in. You
 do not need a copy of the OpenReceive source: the packages are on npm, and the
@@ -145,6 +145,8 @@ Only then start the quickstart.
 The quickstart is done when `npx openreceive doctor --db <file-or-url> --url <app url>`
 is clean and this app serves the checkout page for one of its orders. Doctor
 names any failed check and exits nonzero; fix it before going on.
+Doctor reads `.env` itself. Never source it into a shell: the `&` in a
+code splits the value and prints the pieces.
 
 Give the user that checkout link. The browser check in the quickstart's
 step 6 (payment-method icons, wallet logos, a pay tutorial) is theirs: tell
@@ -155,8 +157,15 @@ mark an order paid, and do not look for a way to (a wallet control port, a
 test endpoint, another wallet). If the user wants a real settlement test, they
 pay on that link from their own wallet, and `onPaid` marks the order paid.
 
-Setup ends here. Say "Setup is finished" in one message, with the link and
-what to check. Do not offer more work or end the message on a question.
+Setup ends here. Say "Setup is finished" in one message of at most five
+lines, with the link and what to check. Do not list what changed, offer more
+work, or end the message on a question.
+
+- The link is to a real unpaid order. Keep that order; do not delete it.
+- Name the methods it offers: Bitcoin, plus USDT, USDC, ETH and SOL when
+  `LSC_URI_PRIMARY` is saved. Never say a coin will not work or will not be
+  offered. Swap minimums apply per order, and a coin whose minimum is above an
+  order's total says so on its own tile.
 
 ## Non-negotiables
 
@@ -331,6 +340,7 @@ enough; drop the `.md` for the same page a person would read.
 - https://openreceive.org/guides/authorization.md — before you write `authorize`
 - https://openreceive.org/guides/environment-variables.md — every variable, and what is deliberately not one
 - https://openreceive.org/guides/storage.md — the payment tables and the attempt state machine
+- https://openreceive.org/guides/supabase.md — when the database is Supabase: its pooler, its certificate, and locking the tables away from its Data API
 - https://openreceive.org/guides/node-orms.md — recipes for Prisma, Drizzle, Knex, TypeORM, Sequelize
 - https://openreceive.org/guides/frontend-checkout.md — the drop-in's props, attributes and slots
 - https://openreceive.org/guides/checkout-ux.md — read before building any custom UI
@@ -575,7 +585,7 @@ rule applies only inside what OpenReceive renders.
 Serve the compiled `styles.css` without Tailwind processing. Import it from
 JavaScript if your bundler handles CSS, or use a plain
 `<link rel="stylesheet">`. Do not `@import` it into your app's Tailwind entry.
-Its rules have zero specificity, so your page's styles can override checkout
+Its rules have low specificity, so your page's styles can override checkout
 styles. Scoping does not prevent that.
 
 `<Checkout>` is complete as rendered. It already shows the `description` from

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

@@ -3,7 +3,7 @@ This is the full file; follow it from Step 0.
 # OpenReceive agent directions (PHP)
 
 ```sh
-# READ THIS FIRST: this file is 38 KB and a summary drops required steps. Download it whole:
+# READ THIS FIRST: this file is 39 KB and a summary drops required steps. Download it whole:
 curl -fsSL https://openreceive.org/agent-directions/php/full.md
 # Skip the download only if you already have all of it: pasted, read from disk or fetched raw.
 ```
@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/php/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.19.
+These directions describe OpenReceive 0.4.21.
 
 Add OpenReceive to a PHP application — the app you are already working in. You
 do not need a copy of the OpenReceive source: the engine is on Packagist
@@ -163,8 +163,15 @@ mark an order paid, and do not look for a way to (a wallet control port, a
 test endpoint, another wallet). If the user wants a real settlement test, they
 pay on that link from their own wallet, and `onPaid` marks the order paid.
 
-Setup ends here. Say "Setup is finished" in one message, with the link and
-what to check. Do not offer more work or end the message on a question.
+Setup ends here. Say "Setup is finished" in one message of at most five
+lines, with the link and what to check. Do not list what changed, offer more
+work, or end the message on a question.
+
+- The link is to a real unpaid order. Keep that order; do not delete it.
+- Name the methods it offers: Bitcoin, plus USDT, USDC, ETH and SOL when
+  `LSC_URI_PRIMARY` is saved. Never say a coin will not work or will not be
+  offered. Swap minimums apply per order, and a coin whose minimum is above an
+  order's total says so on its own tile.
 
 ## Non-negotiables
 
@@ -613,7 +620,7 @@ HTTP routes and the browser snapshots are snake_case throughout.
 Serve the compiled `styles.css` without Tailwind processing. Either import it
 from JavaScript (with a CSS-capable bundler) or use a plain
 `<link rel="stylesheet">`. Do not `@import` it into your Tailwind entry. Its
-rules have zero specificity, so your own styles can override checkout styles.
+rules have low specificity, so your own styles can override checkout styles.
 Scoping does not prevent that.
 
 Unpack the release's `standalone-checkout-<version>.tar.gz` into a directory

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/rails/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.19.
+These directions describe OpenReceive 0.4.21.
 
 Add OpenReceive to a Rails application — the app you are already working in. You
 do not need a copy of the OpenReceive source: the gem is on RubyGems, the
@@ -154,8 +154,15 @@ mark an order paid, and do not look for a way to (a wallet control port, a
 test endpoint, another wallet). If the user wants a real settlement test, they
 pay on that link from their own wallet, and `on_paid` marks the order paid.
 
-Setup ends here. Say "Setup is finished" in one message, with the link and
-what to check. Do not offer more work or end the message on a question.
+Setup ends here. Say "Setup is finished" in one message of at most five
+lines, with the link and what to check. Do not list what changed, offer more
+work, or end the message on a question.
+
+- The link is to a real unpaid order. Keep that order; do not delete it.
+- Name the methods it offers: Bitcoin, plus USDT, USDC, ETH and SOL when
+  `LSC_URI_PRIMARY` is saved. Never say a coin will not work or will not be
+  offered. Swap minimums apply per order, and a coin whose minimum is above an
+  order's total says so on its own tile.
 
 ## Non-negotiables
 
@@ -630,7 +637,7 @@ live wallet is needed.
 Serve the compiled `styles.css` without Tailwind processing. Either import it
 from JavaScript (with a CSS-capable bundler) or use a plain
 `<link rel="stylesheet">`. Do not `@import` it into your Tailwind entry. Its
-rules have zero specificity, so your own styles can override checkout styles.
+rules have low specificity, so your own styles can override checkout styles.
 Scoping does not prevent that.
 
 The engine serves JSON checkout routes only. Your view does the rendering. Any

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/woocommerce/full.md
 - Do not suggest rotating or revoking a code because it was pasted here.
 - Setup is done only when the NWC code is saved, and the LSC code is saved or the user said "Bitcoin only".
 
-These directions describe OpenReceive 0.4.19.
+These directions describe OpenReceive 0.4.21.
 
 Install and configure the OpenReceive payment gateway in the WooCommerce store
 you are working in. Preserve its theme, checkout, customer accounts, order
@@ -96,7 +96,7 @@ Install the plugin built for this release. Never install the GitHub
 source-code ZIP or a ZIP from an older release:
 
 ```sh
-wp plugin install https://github.com/OpenReceive/openreceive/releases/download/v0.4.19/openreceive-wordpress-0.4.19.zip --activate
+wp plugin install https://github.com/OpenReceive/openreceive/releases/download/v0.4.21/openreceive-wordpress-0.4.21.zip --activate
 ```
 
 It needs WooCommerce active, and PHP 8.2+ with GMP and sodium in BOTH the web
@@ -236,7 +236,7 @@ database or application.
 
 ### Get the installable archive
 
-Download [openreceive-wordpress-0.4.19.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.19/openreceive-wordpress-0.4.19.zip)
+Download [openreceive-wordpress-0.4.21.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.21/openreceive-wordpress-0.4.21.zip)
 from the matching release. Historical releases may lack this asset. If that exact
 URL returns 404, build the same tag below; never silently install an older ZIP.
 The GitHub source-code ZIP is not an installable plugin. On a development machine
@@ -245,7 +245,7 @@ with Node 22+, PHP 8.2+ with GMP/sodium, Composer and WP-CLI:
 ```sh
 git clone https://github.com/OpenReceive/openreceive.git
 cd openreceive
-git checkout v0.4.19
+git checkout v0.4.21
 npm ci
 npm run build:packages
 composer install --working-dir=packages/php/wordpress

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: openreceive
 version: !ruby/object:Gem::Version
-  version: 0.4.19
+  version: 0.4.21
 platform: ruby
 authors:
 - OpenReceive