webhookgate-sdk 1.0.3 → 1.0.4

package/README.md

@@ -4,6 +4,10 @@ WebhookGate guarantees **no duplicate webhook side effects**.
 
 https://webhookgate.com
 
+WebhookGate exists to draw a hard line in reality:
+
+> **Past this point, duplicate side effects cannot exist.**
+
 It does this by combining:
 - **durable webhook intake and de-duplication** at the gateway layer, and
 - a **consumer-side idempotency SDK** that makes duplicate side effects **structurally impossible** within the consumer.
@@ -14,7 +18,7 @@ WebhookGate sits in front of webhook consumers and ensures that each `(provider,
 
 ## Documentation (problem-first)
 
-If you want to understand *why* WebhookGate exists — not just how to use it — these documents explain the underlying failure modes and constraints:
+If you want to understand *why* WebhookGate exists — not just how to use it — start here:
 
 - **Why Webhook Retries Cause Duplicate Side Effects**  
   https://webhookgate.com/docs/why-retries-cause-duplicates
@@ -25,24 +29,27 @@ If you want to understand *why* WebhookGate exists — not just how to use it
 - **What a Real Guarantee Requires**  
   https://webhookgate.com/docs/what-a-real-guarantee-requires
 
-These explain the distributed-systems constraints that make ad-hoc idempotency fragile,
+These documents explain the distributed-systems constraints that make ad-hoc idempotency fragile,
 and the architectural boundaries required to make duplicate side effects impossible.
 
 ---
 
 ## What WebhookGate guarantees (MVP)
 
-WebhookGate provides a durable webhook “inbox” in front of your consumer.
+WebhookGate provides a durable webhook **inbox** in front of your consumer.
 
 ### Gateway guarantees
 
 - **Exactly-once acceptance** per `(provider, eventId)`
 - **De-duplication at intake**: repeated deliveries of the same event are not re-accepted
-- **Durable delivery jobs + transport retries**: downstream delivery is retried on network/transport failure
+- **Durable delivery jobs + transport retries**
 - **Deterministic Idempotency-Key propagation** on every downstream delivery
 
-The gateway delivers events **at-least-once** downstream, always with the same
-Idempotency-Key, even across retries, crashes, or restarts.
+The gateway delivers events **at-least-once** downstream, always with the same Idempotency-Key, even across retries, crashes, or restarts.
+
+> Intake is exactly-once.  
+> Delivery is at-least-once.  
+> Side effects are at-most-once.
 
 ---
 
@@ -54,23 +61,24 @@ The consumer SDK converts delivery guarantees into **hard correctness**.
 
 - **At-most-once execution** of the handler per Idempotency-Key
 - **Duplicate deliveries never re-run side effects**
-- **Crash-safe behavior**: if the process crashes mid-handler, the handler is never re-entered (row remains processing)
-- **Error behavior (terminal)**: if the handler throws, the idempotency row transitions to 'failed' and is never re-entered automatically
-- **Transactional DB effects** for database operations performed via the provided db client
+- **Crash-safe behavior**: if the process crashes mid-handler, the handler is never re-entered
+- **Terminal failure semantics**: if the handler throws, the idempotency row transitions to 'failed' and is never re-entered automatically
+- **Transactional DB effects** for database operations performed via the provided DB client
 
 Once a key is successfully claimed, the handler will **never** be executed again — even if the process crashes, restarts, or receives the same event repeatedly.
 
-> Result: side effects are never duplicated.
+> Result: **side effects are never duplicated**.
 
 ---
 
 ## Exactly-once effects (clarified)
 
-WebhookGate guarantees that your handler runs at most once per Idempotency-Key.
+WebhookGate guarantees that your handler runs **at most once** per Idempotency-Key.
 
 If your handler calls external systems (payments, email providers, APIs), those systems must respect idempotency keys to achieve end-to-end exactly-once effects across system boundaries.
 
 This design deliberately favors **safety over re-execution**:
+
 WebhookGate will never risk double-charging, double-emailing, or double-writing.
 
 ---
@@ -99,36 +107,70 @@ app.post(
 );
 ```
 
+There are no flags, retries, or callbacks to manage.
+
+If safety cannot be proven, execution is refused (fail-closed).
+
 ---
 
-## Proof: No duplicate side effects (60 seconds)
+## Proof: no duplicate side effects (60 seconds)
 
-1. Start Postgres
-2. Install dependencies
+1. Start Postgres  
+2. Install dependencies  
+   ```bash
    npm install
-3. Start the consumer
+   ```
+3. Start the consumer  
+   ```bash
    npm run consumer
-4. Start the gateway
+   ```
+4. Start the gateway  
+   ```bash
    npm run dev
-5. Send a replay storm
+   ```
+5. Send a replay storm  
+   ```bash
    npm run chaos -- evt_test_1
+   ```
 
-Result:
+**Result**
 - Gateway receives 50 duplicate events
-- Consumer executes the handler once
-- /stats shows charges = 1
+- Consumer executes the handler **once**
+- `/stats` shows `charges = 1`
+
+### Crash test
 
-Crash test:
-- Start consumer with CRASH_ONCE=true
+- Start consumer with `CRASH_ONCE=true`
 - Re-run chaos
 - Restart consumer
-- Charges still = 1
+
+**Charges still = 1**
+
+---
+
+## Relationship to webhook-replay
+
+- **webhook-replay** detects unsafe handlers (local / CI)
+- **WebhookGate** enforces safety in production
+
+If `webhook-replay` reports:
+
+```
+❌ UNSAFE UNDER RETRY
+```
+
+WebhookGate is the production fix.
 
 ---
 
 ## When you need production-grade durability
 
-WebhookGate adds durable intake, replay protection, and operational safeguards for environments where local correctness is no longer sufficient.
+Local correctness is not enough once retries, crashes, and distributed failure enter the picture.
+
+WebhookGate adds:
+- durable intake
+- replay protection
+- enforcement instead of best-effort guarantees
 
 Learn more:
 - Overview: https://webhookgate.com

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "webhookgate-sdk",
-  "version": "1.0.3",
+  "version": "1.0.4",
   "type": "module",
   "main": "index.js",
   "exports": {