openreceive 0.4.28 → 0.4.29

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8c198777522ede161b4aa74adfbc59ba1602b12f4796da961a525c1712cc39a9
-  data.tar.gz: d0a7f92203bda702712fa5168defa22771837c3d25b367e11918baacf564abbe
+  metadata.gz: d1a81bab2d7f01fe8c723b24b3d22b5ae1b2cfa705dbf9f52001b2dc3259af89
+  data.tar.gz: d46ece12f35400fccfc15365cbe61854d2ad9a6dd8641ab42dd2b6bc8d157829
 SHA512:
-  metadata.gz: 30e0688e93e66f04e1c01950f889a9f1506de5d687a6596664da8d657932d35179594ef961933794b4ecb4923922ae7a6f5a00a4fc14ef4b0530ffb95c71462a
-  data.tar.gz: c59517260edb75d6b4289d10317a9105971bfb731a46e7e3b7c682efa80a2b54629c7166d0c9890b1993c5e60e85f0e33ac7270cef2f242e84ab6210184b0fe4
+  metadata.gz: 7b90b00d878b6cc2a6800337a096d98790ebdc5402717814f620c45042f21ec31347fa6c1448b9ff77d5e524b1e61b6d3a954c3e8a3d75d2e1813b7a28da96a6
+  data.tar.gz: 4d209c7a0cdc243d7d3e801a0c3617aa8be4a567ea2f78b057ab6ba8de13ce302f1bbe2f42d9fd870bf872ce128ef90dc018681de8370a5ebd1a576ba3a7c894

data/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.4.29 - 2026-10-19
+
+Release with the complete 0.4.29 package family. The bundled agent skill's
+FOSSBilling reference covers the extension directory install. No Ruby runtime
+changes from 0.4.28.
+
 ## 0.4.28 - 2026-10-18
 
 Release with the complete 0.4.28 package family. The bundled agent skill adds

data/lib/openreceive/version.rb

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

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/astro/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Add OpenReceive to an Astro site — the one you are already working in, on
 `@astrojs/node`. OpenReceive ships no Astro package: the integration is one

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

@@ -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.28.
+These directions describe OpenReceive 0.4.29.
 
 Add OpenReceive to this Bolt app: a Vite React app on Bolt Cloud, with Bolt
 Database or a connected Supabase project as its database, and Supabase Edge
@@ -123,8 +123,8 @@ explicitly declined.
 
 ## Step 1 — the packages
 
-Add `@openreceive/react` at 0.4.28 or newer to the app's
-`package.json`. The function imports `npm:@openreceive/http@^0.4.28`
+Add `@openreceive/react` at 0.4.29 or newer to the app's
+`package.json`. The function imports `npm:@openreceive/http@^0.4.29`
 and `npm:@supabase/supabase-js@2` directly; add nothing else. No `pg`, no
 Postgres driver, no OpenReceive scaffold.
 

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.28.
+These directions describe OpenReceive 0.4.29.
 
 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.28.
+These directions describe OpenReceive 0.4.29.
 
 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

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/edd/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Install and configure the OpenReceive payment gateway in the Easy Digital
 Downloads (EDD) store you are working in. Preserve its theme, checkout,
@@ -96,7 +96,7 @@ is saved or the user said "Bitcoin only". Never invent a placeholder code.
 Install this release from the WordPress.org plugin directory:
 
 ```sh
-wp plugin install openreceive --version=0.4.28 --activate
+wp plugin install openreceive --version=0.4.29 --activate
 ```
 
 If that fails because WordPress.org does not have this version yet, install
@@ -104,7 +104,7 @@ the ZIP attached to the same GitHub 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.28/openreceive-wordpress-0.4.28.zip --activate
+wp plugin install https://github.com/OpenReceive/openreceive/releases/download/v0.4.29/openreceive-wordpress-0.4.29.zip --activate
 ```
 
 It needs Easy Digital Downloads active, and PHP 8.2+ with GMP and sodium in
@@ -258,7 +258,7 @@ activate it. With WP-CLI, run `wp plugin install openreceive --activate`.
 
 Each GitHub release also attaches the plugin as a ZIP, for a site that cannot
 reach WordPress.org:
-[openreceive-wordpress-0.4.28.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-wordpress-0.4.28.zip).
+[openreceive-wordpress-0.4.29.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.29/openreceive-wordpress-0.4.29.zip).
 Install it through **Plugins → Add New → Upload Plugin**. The GitHub
 source-code ZIP is not an installable plugin.
 

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.28.
+These directions describe OpenReceive 0.4.29.
 
 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

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.28.
+These directions describe OpenReceive 0.4.29.
 
 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

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/flask/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Add OpenReceive to a Flask application — the app you are already working in.
 You do not need a copy of the OpenReceive source: the engine is on PyPI

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

@@ -3,7 +3,7 @@ This is the full file; follow it from Step 0.
 # OpenReceive agent directions (FOSSBilling)
 
 ```sh
-# READ THIS FIRST: this file is 23 KB and a summary drops required steps. Download it whole:
+# READ THIS FIRST: this file is 25 KB and a summary drops required steps. Download it whole:
 curl -fsSL https://openreceive.org/agent-directions/fossbilling/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/fossbilling/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Install and configure the OpenReceive payment method in the FOSSBilling
 billing panel you are working in. Preserve its theme, clients, products,
@@ -121,16 +121,18 @@ Docker image, download and unpack it inside the container, as the web user,
 then activate the module:
 
 ```sh
-docker compose exec -T -u www-data fossbilling sh -c 'curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-fossbilling-0.4.28.zip && unzip -oq openreceive-fossbilling-0.4.28.zip && rm openreceive-fossbilling-0.4.28.zip'
+docker compose exec -T -u www-data fossbilling sh -c 'curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.29/openreceive-fossbilling-0.4.29.zip && unzip -oq openreceive-fossbilling-0.4.29.zip && rm openreceive-fossbilling-0.4.29.zip'
 docker compose exec -T -u www-data fossbilling php modules/Openreceive/activate.php
 ```
 
 On a server, unpack it in FOSSBilling's folder the same way, make the two
-folders the web user's, and run the same `activate.php`. Activation creates
-the extension's two tables in FOSSBilling's database and its payment gateway,
-"Bitcoin Lightning", hooks its reconcile pass into FOSSBilling's cron, and
-makes the `openreceive:*` console commands appear. The gateway stays off until
-a wallet code is saved.
+folders the web user's, and run the same `activate.php`. Activation writes the
+payment gateway's files into `library/Payment/Adapter/OpenReceive` from the
+module's own copy, creates the extension's two tables in FOSSBilling's
+database and its payment gateway, "Bitcoin Lightning", hooks its reconcile
+pass into FOSSBilling's cron, and makes the `openreceive:*` console commands
+appear. The gateway stays off until a wallet code is saved. If `activate.php`
+says that folder holds another gateway, report that and stop.
 
 ## Step 2 — store the codes
 
@@ -275,9 +277,9 @@ routes, console commands and cron hook), and
 
 ```sh
 cd /var/www/fossbilling
-curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-fossbilling-0.4.28.zip
-unzip -oq openreceive-fossbilling-0.4.28.zip
-rm openreceive-fossbilling-0.4.28.zip
+curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.29/openreceive-fossbilling-0.4.29.zip
+unzip -oq openreceive-fossbilling-0.4.29.zip
+rm openreceive-fossbilling-0.4.29.zip
 chown -R www-data:www-data modules/Openreceive library/Payment/Adapter/OpenReceive
 sudo -u www-data php modules/Openreceive/activate.php
 ```
@@ -288,11 +290,26 @@ either. Activation creates the extension's two tables and its payment
 gateway, "Bitcoin Lightning", and hooks its reconcile pass into FOSSBilling's
 cron. The gateway stays off until a wallet code is saved.
 
+The module carries its own copy of the payment gateway and writes it into
+`library/Payment/Adapter/OpenReceive` each time it is activated, so running
+`activate.php` again after an update brings the gateway up to date with the
+module. It replaces only OpenReceive's own gateway files: if that folder holds
+anything else, activation stops and says so.
+
 The ZIP already bundles the extension's dependencies and the checkout's
 script, under their own prefixed names, so Composer never runs and nothing in
 FOSSBilling's own `vendor/` changes. The GitHub source-code ZIP is not an
 installable extension.
 
+#### The module-only ZIP
+
+Each release also attaches `openreceive-fossbilling-module-<version>.zip`:
+the module alone, with its files at the top of the ZIP rather than inside
+`modules/Openreceive`. That is the package FOSSBilling's extension directory
+installs. Its **Install** button unpacks the ZIP into `modules/Openreceive`,
+and activating OpenReceive under **Extensions** then writes the payment
+gateway, as above. Both ZIPs hold the same module.
+
 #### FOSSBilling in Docker
 
 FOSSBilling's official image has sodium but not GMP. Build your own image on
@@ -314,7 +331,7 @@ Run every command inside the container, in `/var/www/html`, as its web user
 `www-data`. Unpack the release there too:
 
 ```sh
-docker compose exec -T -u www-data fossbilling sh -c 'curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-fossbilling-0.4.28.zip && unzip -oq openreceive-fossbilling-0.4.28.zip && rm openreceive-fossbilling-0.4.28.zip'
+docker compose exec -T -u www-data fossbilling sh -c 'curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.29/openreceive-fossbilling-0.4.29.zip && unzip -oq openreceive-fossbilling-0.4.29.zip && rm openreceive-fossbilling-0.4.29.zip'
 docker compose exec -T -u www-data fossbilling php modules/Openreceive/activate.php
 ```
 
@@ -349,7 +366,8 @@ Lightning" to "Bitcoin & stablecoins"; the settings page's name field, or
 `--name="…"`, sets your own. Skip the swap code for Bitcoin-only checkout.
 
 `doctor` checks the module, GMP and sodium, each code as set or unset (never
-its value), the payment gateway, the tables, the checkout's files, the wallet,
+its value), the payment gateway's files and row, the tables, the checkout's
+files, the wallet,
 the price feed for every FOSSBilling currency, each swap provider and the cron
 hook with FOSSBilling's last cron run. It exits nonzero when a check fails.
 
@@ -413,8 +431,14 @@ converted reclaims it from the same invoice's payment page, while the invoice
 is still unpaid. If you turn on swaps, you commit to keeping that path
 available. See [swap refunds](https://openreceive.org/guides/swap-refunds.md).
 
-Deactivating or uninstalling the module keeps the two tables: they are a
-record of payments received.
+Deactivating the module turns its payment gateway off, because a deactivated
+module serves no checkout. Activating it again turns the gateway back on when
+a wallet code is saved.
+
+Uninstalling the module keeps the two tables, which are a record of payments
+received, and leaves the gateway off. Its row and its files in
+`library/Payment/Adapter/OpenReceive` stay too, since FOSSBilling's invoices
+and transactions refer to the gateway.
 
 ### Tested, and not tested
 
@@ -427,6 +451,15 @@ service is active. A payment whose page was closed was recorded by
 FOSSBilling's cron. Another client, a visitor and a request without the page's
 security token were refused.
 
+Tested on 2026-10-18 in the same setup: the module-only ZIP installed through
+FOSSBilling's own **Install** and **Activate** buttons in the admin area, with
+the extension directory's answer for OpenReceive supplied locally, then the
+same checks. Deactivating, activating again, uninstalling, reinstalling and
+updating a 0.4.28 install with `activate.php` were checked too. On
+FOSSBilling 0.8.0, the oldest release the module accepts: the same install
+and activation, `configure`, the doctor, `test-invoice --new`, deactivating
+and activating again.
+
 Not tested: FOSSBilling behind nginx rather than its image's Apache, shared
 hosting without a shell, and FOSSBilling's subscription payments. Lightning
 cannot pull a payment, so OpenReceive offers no subscriptions: the client

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.28.
+These directions describe OpenReceive 0.4.29.
 
 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

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

@@ -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.28.
+These directions describe OpenReceive 0.4.29.
 
 Add OpenReceive to this Lovable app: a TanStack Start app on Cloudflare
 Workers, with Lovable Cloud or a connected Supabase project as its database.
@@ -121,7 +121,7 @@ saved or explicitly declined.
 
 ## Step 1 — the packages
 
-Add `@openreceive/http` and `@openreceive/react` at 0.4.28 or newer.
+Add `@openreceive/http` and `@openreceive/react` at 0.4.29 or newer.
 Nothing else: no `pg`, no Postgres driver, no OpenReceive scaffold. Do not
 change the Vite or Wrangler configuration.
 

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/medusa/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Add OpenReceive to the Medusa store you are working in: a Medusa server, and
 usually a storefront in its own project (Medusa's Next.js starter or another).

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/mobile/full.md
 - The app never decides paid: it asks the server. A link back to the app is navigation only.
 - Do not suggest rotating or revoking a code because it was pasted here.
 
-These directions describe OpenReceive 0.4.28.
+These directions describe OpenReceive 0.4.29.
 
 Add Bitcoin checkout, with optional USDT, USDC, ETH and SOL, to a mobile app:
 React Native or Expo, Flutter, Swift or Kotlin. OpenReceive has no mobile SDK

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/nestjs/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Add OpenReceive to a NestJS application — the app you are already working in,
 on Nest's default Express platform. You do not need a copy of the OpenReceive

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

@@ -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.28.
+These directions describe OpenReceive 0.4.29.
 
 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

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

@@ -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.28.
+These directions describe OpenReceive 0.4.29.
 
 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

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/nuxt/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Add OpenReceive to a Nuxt application — the app you are already working in,
 on Nitro's `node-server` preset. OpenReceive ships no Nuxt package: the

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/paymenter/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Install and configure the OpenReceive payment gateway in the Paymenter billing
 panel you are working in. Preserve its theme, clients, products, invoices and
@@ -97,7 +97,7 @@ release. With Paymenter's official Docker image, download and unpack it inside
 the container, as the web user:
 
 ```sh
-docker compose exec -T -u nginx paymenter sh -c 'cd /app/extensions/Gateways && curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-paymenter-0.4.28.zip && unzip -q openreceive-paymenter-0.4.28.zip && rm openreceive-paymenter-0.4.28.zip'
+docker compose exec -T -u nginx paymenter sh -c 'cd /app/extensions/Gateways && curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.29/openreceive-paymenter-0.4.29.zip && unzip -q openreceive-paymenter-0.4.29.zip && rm openreceive-paymenter-0.4.29.zip'
 docker compose exec -T -u nginx paymenter php artisan app:extension:install gateway OpenReceive
 ```
 
@@ -243,9 +243,9 @@ directory, next to Stripe and PayPal:
 
 ```sh
 cd /var/www/paymenter
-curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-paymenter-0.4.28.zip
-unzip -q openreceive-paymenter-0.4.28.zip -d extensions/Gateways
-rm openreceive-paymenter-0.4.28.zip
+curl -fsSLO https://github.com/OpenReceive/openreceive/releases/download/v0.4.29/openreceive-paymenter-0.4.29.zip
+unzip -q openreceive-paymenter-0.4.29.zip -d extensions/Gateways
+rm openreceive-paymenter-0.4.29.zip
 chown -R www-data:www-data extensions/Gateways/OpenReceive
 sudo -u www-data php artisan app:extension:install gateway OpenReceive
 ```

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.28.
+These directions describe OpenReceive 0.4.29.
 
 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

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.28.
+These directions describe OpenReceive 0.4.29.
 
 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

data/skills/integrate-openreceive/references/react-router.md

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/react-router/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Add OpenReceive to a React Router application in framework mode — the app
 you are already working in, on Node. OpenReceive ships no React Router

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

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/sveltekit/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Add OpenReceive to a SvelteKit application — the app you are already working
 in, on `@sveltejs/adapter-node`. OpenReceive ships no SvelteKit package: the

data/skills/integrate-openreceive/references/tanstack-start.md

@@ -17,7 +17,7 @@ curl -fsSL https://openreceive.org/agent-directions/tanstack-start/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.28.
+These directions describe OpenReceive 0.4.29.
 
 Add OpenReceive to a TanStack Start application on Node — the app you are
 already working in, with its own Postgres. OpenReceive ships no TanStack

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.28.
+These directions describe OpenReceive 0.4.29.
 
 Install and configure the OpenReceive payment gateway in the WooCommerce store
 you are working in. Preserve its theme, checkout, customer accounts, order
@@ -95,7 +95,7 @@ is saved or the user said "Bitcoin only". Never invent a placeholder code.
 Install this release from the WordPress.org plugin directory:
 
 ```sh
-wp plugin install openreceive --version=0.4.28 --activate
+wp plugin install openreceive --version=0.4.29 --activate
 ```
 
 If that fails because WordPress.org does not have this version yet, install
@@ -103,7 +103,7 @@ the ZIP attached to the same GitHub 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.28/openreceive-wordpress-0.4.28.zip --activate
+wp plugin install https://github.com/OpenReceive/openreceive/releases/download/v0.4.29/openreceive-wordpress-0.4.29.zip --activate
 ```
 
 It needs WooCommerce active, and PHP 8.2+ with GMP and sodium in BOTH the web
@@ -254,7 +254,7 @@ database or application.
 
 Each GitHub release also attaches the same plugin as a ZIP, for a site that
 cannot reach WordPress.org or when WordPress.org does not list a release yet.
-Download [openreceive-wordpress-0.4.28.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.28/openreceive-wordpress-0.4.28.zip)
+Download [openreceive-wordpress-0.4.29.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.29/openreceive-wordpress-0.4.29.zip)
 and install it through **Plugins → Add New → Upload Plugin**. 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
@@ -264,7 +264,7 @@ GMP/sodium, Composer and WP-CLI:
 ```sh
 git clone https://github.com/OpenReceive/openreceive.git
 cd openreceive
-git checkout v0.4.28
+git checkout v0.4.29
 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.28
+  version: 0.4.29
 platform: ruby
 authors:
 - OpenReceive