openreceive 0.4.15 → 0.4.16

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 291e8df2ba4b159d4b5bede37b77df8449773110c8ec307f732e7f1f176df239
-  data.tar.gz: b81c08dd8358630ea628eb2d04cda593d1ba99e559612ffdffcaf9568c46f5e6
+  metadata.gz: b6bccc561cfb62ab23269e121a9941b294933ef5d1e0d9f94587112160f5ef7d
+  data.tar.gz: ad06d5b3acc767c333aab47b42d92aff0c66cb1ae448cd50be485b3450a1d7f4
 SHA512:
-  metadata.gz: a29c57a32d0e44750b4122d10e4c4bad8f451ca97dce0c8dfcbd5011e77666871d4d090bf1325e3bfc69fc74cabb815b217c15a836e62b6941a7b89ab02ded45
-  data.tar.gz: fd92160562d64c75466cb814419e1ca7bb781df453dfe275bae5d229595195f99b1be945c3e31070591834ad083f0fa07d54e9290557bbc3bf2be3bf9ead27e4
+  metadata.gz: aed3a70c5b0ae4fe4d7eb4066324ca4b0bf4dcffd61b39ac1f9e8db39db9341453a6457e6fb534fc268db5de9ee22ec19d5c2e18ad29f1ae5fc2541c9cf2b203
+  data.tar.gz: 9b6e40b40e28e11f482011df69f58ca3394ce6a61e6a01f20a1d0d6e0a8cf956dc183491521c9a81c5ea429510fe076515243fc8e0b9fe64cb05f498b152fe6e

data/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 0.4.16 - 2026-10-06
+
+Release with the complete 0.4.16 package family and corrected shared agent
+directions. No Ruby runtime changes from 0.4.15.
+
 ## 0.4.15 - 2026-10-06
 
 - Install agent skills with `bin/rails openreceive:skills` (optional

data/lib/openreceive/version.rb

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

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (BTCPay Server)
 
-These directions describe OpenReceive 0.4.15.
+These directions describe OpenReceive 0.4.16.
 
 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
@@ -164,13 +164,17 @@ them to install the plugin for you.
 
 **1. Open the Plugins menu.** It is the plug icon in the top-right corner.
 
+
 **2. Click Plugin Directory.**
 
+
 **3. Search for `openreceive`** and click the **OpenReceive** result.
 
+
 **4. Click Install in BTCPay Server.** Confirm when prompted, then click
 **Restart now** and wait for BTCPay to come back.
 
+
 At startup, BTCPay creates the plugin's two tables in its own Postgres
 database: `openreceive_invoices` and `openreceive_swaps`, in the schema
 `BTCPayServer.Plugins.OpenReceive`. Nothing else is created.

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Django)
 
-These directions describe OpenReceive 0.4.15.
+These directions describe OpenReceive 0.4.16.
 
 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
@@ -366,17 +366,18 @@ Then add the app, point it at a host class, and mount the routes:
 INSTALLED_APPS += ["openreceive.django"]
 
 OPENRECEIVE = {
-    "HOST": "shop.openreceive_host.Host",   # the class with the three hooks (generated below)
+    "HOST": "shop.openreceive_host.Host",  # the class with the three hooks (generated below)
     "PRICE_CURRENCIES": ["USD"],
-    "RATE_LIMITING": False,                 # True for public web shops (see below)
-    "OPPORTUNISTIC_RECONCILE": True,        # or {"min_interval_seconds": …}; False only with your own worker
-    "DATABASE": "default",                  # the DATABASES alias that holds the two engine tables
+    "RATE_LIMITING": False,  # True for public web shops (see below)
+    "OPPORTUNISTIC_RECONCILE": True,  # or {"min_interval_seconds": …}; False only with your own worker
+    "DATABASE": "default",  # the DATABASES alias that holds the two engine tables
 }
 ```
 
 ```python
 # urls.py
 from django.urls import include, path
+
 urlpatterns += [path("openreceive/", include("openreceive.django.urls"))]
 ```
 
@@ -420,9 +421,9 @@ The generated host module explains this and shows the guarded transition:
 
 ```python
 def on_paid(self, settlement: PaymentSettlement) -> None:
-    claimed = Order.objects.filter(
-        pk=settlement.reference, state="awaiting_payment"
-    ).update(state="paid", paid_at=datetime.fromtimestamp(settlement.paid_at, tz=UTC))
+    claimed = Order.objects.filter(pk=settlement.reference, state="awaiting_payment").update(
+        state="paid", paid_at=datetime.fromtimestamp(settlement.paid_at, tz=UTC)
+    )
     if claimed == 0:
         return  # someone else already fulfilled it
 
@@ -450,7 +451,9 @@ instead:
 
 ```python
 def on_paid(self, settlement: PaymentSettlement) -> None:
-    order = Order.objects.select_for_update().filter(pk=settlement.reference).first()  # SELECT … FOR UPDATE
+    order = (
+        Order.objects.select_for_update().filter(pk=settlement.reference).first()
+    )  # SELECT … FOR UPDATE
     if order is None or order.state != "awaiting_payment":
         return
     order.state = "paid"
@@ -533,8 +536,9 @@ from openreceive.server import HookContext
 from openreceive.storage import PaymentSettlement
 
 from shop.models import Order  # YOUR model — it could be named anything. OpenReceive
-                               # never sees it or touches its table; these hooks are the
-                               # only bridge between the engine and your data.
+# never sees it or touches its table; these hooks are the
+# only bridge between the engine and your data.
+
 
 class Host:
     # Your policy, called before every checkout/payment/swap request. `context`
@@ -564,8 +568,11 @@ class Host:
         order = Order.objects.filter(pk=reference).first()
         if order is None:
             return None
-        return {"currency": "USD", "value": str(order.total),
-                "description": f"{order.items.count()} items"}
+        return {
+            "currency": "USD",
+            "value": str(order.total),
+            "description": f"{order.items.count()} items",
+        }
 
     # Runs inside the settlement transaction, only for the order's first settled
     # attempt. The WHERE clause is the lock: a second fulfillment path of yours

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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (FastAPI)
 
-These directions describe OpenReceive 0.4.15.
+These directions describe OpenReceive 0.4.16.
 
 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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Fastify)
 
-These directions describe OpenReceive 0.4.15.
+These directions describe OpenReceive 0.4.16.
 
 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/laravel.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Laravel)
 
-These directions describe OpenReceive 0.4.15.
+These directions describe OpenReceive 0.4.16.
 
 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/next.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Next.js)
 
-These directions describe OpenReceive 0.4.15.
+These directions describe OpenReceive 0.4.16.
 
 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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Node.js)
 
-These directions describe OpenReceive 0.4.15.
+These directions describe OpenReceive 0.4.16.
 
 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/php.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (PHP)
 
-These directions describe OpenReceive 0.4.15.
+These directions describe OpenReceive 0.4.16.
 
 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

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (Rails)
 
-These directions describe OpenReceive 0.4.15.
+These directions describe OpenReceive 0.4.16.
 
 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/woocommerce.md

@@ -1,6 +1,6 @@
 # OpenReceive agent directions (WordPress + WooCommerce)
 
-These directions describe OpenReceive 0.4.15.
+These directions describe OpenReceive 0.4.16.
 
 Install and configure the OpenReceive gateway in the existing WooCommerce
 store. Preserve its theme, checkout, customer accounts, order model and prices.
@@ -95,7 +95,7 @@ database or application.
 
 ### Get the installable archive
 
-Download [openreceive-wordpress-0.4.15.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.15/openreceive-wordpress-0.4.15.zip)
+Download [openreceive-wordpress-0.4.16.zip](https://github.com/OpenReceive/openreceive/releases/download/v0.4.16/openreceive-wordpress-0.4.16.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
@@ -104,7 +104,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.15
+git checkout v0.4.16
 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.15
+  version: 0.4.16
 platform: ruby
 authors:
 - OpenReceive