foldrun 2.10.9 → 2.10.11

package/docs/budgets-and-billing.md

@@ -370,9 +370,11 @@ when. If the invoice is still unpaid when the grace ends, the hourly sweep
 suspends the account for new runs with the reason **payment overdue**, and
 one more email says so; the banner turns red. Runs in flight finish, people
 can still sign in, nothing is deleted. The moment `invoice.paid` arrives
-for it — or `invoice.voided`, `invoice.marked_uncollectible`, or Stripe
-cancelling the subscription — the suspension is lifted, and a payment
-gets a thank-you email. Every step is once per invoice, however often
+for it — or `invoice.voided` or `invoice.marked_uncollectible`, which is
+how a debt is written off — the suspension is lifted, and a payment gets a
+thank-you email. The subscription ending does not settle it: the plan
+ends, but an invoice it left unpaid is still owed and still payable, and
+the account stays paused until it is paid or written off. Every step is once per invoice, however often
 Stripe retries or redelivers; a second invoice failing during the grace
 does not restart it. Dunning lifts only a suspension it placed: an account
 the super admin suspended for another reason stays suspended. The super
@@ -496,7 +498,7 @@ is `<public url>/api/billing/stripe`, sending exactly:
 | `invoice.voided` | an overdue invoice cancelled; dunning ends |
 | `invoice.marked_uncollectible` | an overdue invoice written off; dunning ends |
 | `customer.subscription.updated` | a plan swap, or a status change |
-| `customer.subscription.deleted` | the plan it paid for ends; its dunning ends |
+| `customer.subscription.deleted` | the plan it paid for ends; what it left unpaid stays owed (dunning and its pause stay) |
 | `payment_intent.succeeded` | an auto top-up credited |
 | `payment_intent.payment_failed` | an auto top-up refused; the warning goes |
 | `charge.refunded` | a refunded top-up's credits come off |
@@ -504,12 +506,17 @@ is `<public url>/api/billing/stripe`, sending exactly:
 | `charge.dispute.closed` | won: it goes back on; lost: it stays off |
 
 Every delivery is logged — the event, the account, what was done or the
-error, and a hash of the payload (never the payload, which carries names
-and addresses). The super admin lists the log at `GET
-/api/admin/stripe-events` and replays one event with `POST
-/api/admin/stripe-events/<id>/replay`, which re-fetches it from Stripe and
-runs it through the same handler; every write it makes is keyed once, so a
-replay of an event that was handled changes nothing.
+error, and a hash of the payload. Since 28 Oct 2026 the event itself is
+kept too, for the types above only, up to 256 KB, set when it first
+arrives and emptied after **180 days**: Stripe keeps events for 30, and a
+replay after that needs a copy. It carries what Stripe sends (names,
+emails, addresses, a card's last four digits — never a full card number),
+so only the super admin's console reads it and lists never load it. The
+super admin lists the log at `GET /api/admin/stripe-events` and replays
+one event with `POST /api/admin/stripe-events/<id>/replay` — Stripe's copy
+while Stripe has it, the kept copy after — through the same handler; every
+write it makes is keyed once, so a replay of an event that was handled
+changes nothing.
 
 ## Plan gates
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "foldrun",
-  "version": "2.10.9",
+  "version": "2.10.11",
   "description": "Agents are just folders. Write them, check them, run them — on your machine.",
   "license": "FSL-1.1-ALv2",
   "type": "module",