openreceive 0.4.19 → 0.4.20

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 69ebcc5498ead076761f4bc0fc6b6d6d5033bd7d545d8205f1a506158e245aec
-  data.tar.gz: bcd3dc96c037672bd91b92670404cdddae35092e2203a8dc9bd6609b476d4d4e
+  metadata.gz: a4d27a57c2eb4472bb9115faa410c456627175138dfdc0a99bac922b41e2c5e2
+  data.tar.gz: 8b9cf0b6349386672e6ddd837b4b22e37ae2b8b60859c81b434db6e61e800449
 SHA512:
-  metadata.gz: d1496080f84486058630a54707199070930ec5e68dfc13da251ef6a8e6ae71dd2ff33d073b7609c83f50be576753c8b5516060d936a9c36e05b97204309bd48d
-  data.tar.gz: fbfa6d7bd3fd06b2f08ceef369c4cd82051e14ecaf38c2eadaafbf4bcf9d1d9cc554a0e28d6fb7e8c55c4ce5917dd2040f8adf41efc559cc9fec4667637592fe
+  metadata.gz: f8209f3a34e49f833443c7bbf7da40ea1244c4369e18457d3936994234b98b94be28639f0299427493842eef8e84fa7829dd09ac35bb239b78ea6c37926cb236
+  data.tar.gz: a1ad42f0a0ef75f78f986f3104f1aa380ab05c559bf62694c83a08f10933af2eead4436fe64eb3114ef18b4fede8c7af1f51d3a17ffb88d4d47f676bd89d9e06

data/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 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.20"
 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.20.
 
 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

@@ -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.20.
 
 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
@@ -352,6 +352,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 +691,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.20.
 
 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
@@ -351,6 +351,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 +591,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.20.
 
 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
@@ -335,6 +335,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 +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/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.20.
 
 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
@@ -668,7 +668,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.20.
 
 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
@@ -344,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
@@ -361,6 +362,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 +649,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.20.
 
 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
@@ -331,6 +331,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 +576,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

@@ -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.20.
 
 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
@@ -613,7 +613,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.20.
 
 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
@@ -630,7 +630,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.20.
 
 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.20/openreceive-wordpress-0.4.20.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.20.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.20/openreceive-wordpress-0.4.20.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.20
 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.20
 platform: ruby
 authors:
 - OpenReceive