foldrun 2.10.8 → 2.10.10

package/docs/budgets-and-billing.md

@@ -174,8 +174,9 @@ credit closest to expiring is always the credit being used. Spend draws on the c
 on the balance. A new account starts with **300 trial credits**, no card
 asked. Without a plan, credit costs 1¢ each, one run at a time, up to 3
 workspaces, standard lane — a plan is cheaper from the first month you would have spent its fee
-anyway. Changing plan happens at once, prorated by Stripe, and the new
-bundle lands with the invoice; ending one ends it with the cycle.
+anyway. Changing plan is charged at once, prorated by Stripe; the new plan
+and its bundle land when that invoice is paid — a change whose payment
+fails leaves you on the plan you had. Ending one ends it with the cycle.
 
 **Seats are unlimited** on every plan: agents work, people supervise, and a
 per-seat fee would tax the approver the safety story depends on.
@@ -419,13 +420,16 @@ The bookkeeping rules behind the numbers, for whoever has to answer "why is
 my balance this".
 
 **One grant per plan cycle.** A cycle is the subscription, the plan and the
-end of the period it pays for, and that is the grant's key. Stripe tells us
-about a paid cycle several ways — the checkout returning, the checkout
-webhook, `invoice.paid`, `customer.subscription.updated` — and in no fixed
-order; whichever arrives first grants and the rest find it done. A plan
-change inside a period is a new cycle on the new plan (the prorated invoice
-and the updated event are the same cycle, one grant); a renewal is a new
-period. A change inside a period grants the new plan's bundle **pro-rated
+end of the period it pays for, and that is the grant's key. A grant needs
+the money: a paid checkout (or one with nothing to pay), the checkout
+returning paid, or `invoice.paid` — whichever arrives first grants and the
+rest find it done. `customer.subscription.updated` moves the plan's
+status, never its credits: Stripe applies a price change even when its
+invoice then fails. Each invoice grants the plan **it** paid for, read off
+its own lines, not whatever the subscription has moved to since; and a
+paid invoice for a period older than the one already granted grants
+nothing. A plan change inside a period is a new cycle on the new plan; a
+renewal is a new period. A change inside a period grants the new plan's bundle **pro-rated
 by the share of the period left**, the way Stripe prorates the charge; a
 renewal grants it whole. Going back to a plan already granted this period
 switches the plan and its gates back but grants nothing again. Downgrades
@@ -500,12 +504,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.8",
+  "version": "2.10.10",
   "description": "Agents are just folders. Write them, check them, run them — on your machine.",
   "license": "FSL-1.1-ALv2",
   "type": "module",