@shipstatic/types 2.17.0 → 2.18.0

package/dist/index.d.ts

@@ -1966,12 +1966,13 @@ export interface BillingSyncResponse {
  * All activity event types logged in the system.
  * Uses dot notation consistently: {resource}.{action}
  *
- * Retention: activity rows are permanent — the account's own history and
- * the platform's audit ledgers are one table, kept for the life of the
- * account (deletion removes them). Only the personal payload is
- * time-bounded: past 90 days each row sheds its IP.
+ * Retention: activity rows age out. An account keeps a recent window and,
+ * beneath it, never fewer than its most recent handful — so a dormant
+ * account's history is never empty — and a row that outlives the window
+ * keeps no IP address. Activity from deploys made without an account ages
+ * out sooner, and deleting an account removes its rows outright, at any age.
  */
-export type ActivityEvent = 'account.create' | 'account.delete' | 'account.key.generate' | 'account.plan.transition' | 'deployment.create' | 'deployment.update' | 'deployment.delete' | 'deployment.claim' | 'deployment.flagged' | 'deployment.open' | 'domain.create' | 'domain.update' | 'domain.delete' | 'domain.verify' | 'token.create' | 'token.consume' | 'token.delete' | 'admin.account.plan.update' | 'admin.account.suspended.update' | 'admin.account.ref.update' | 'admin.account.labels.update' | 'admin.deployment.delete' | 'admin.domain.delete' | 'admin.impersonate';
+export type ActivityEvent = 'account.create' | 'account.delete' | 'account.key.generate' | 'account.plan.transition' | 'deployment.create' | 'deployment.update' | 'deployment.delete' | 'deployment.claim' | 'deployment.flagged' | 'deployment.open' | 'domain.create' | 'domain.update' | 'domain.delete' | 'domain.verify' | 'token.create' | 'token.consume' | 'token.delete' | 'checkout.open' | 'admin.account.plan.update' | 'admin.account.suspended.update' | 'admin.account.ref.update' | 'admin.account.labels.update' | 'admin.deployment.delete' | 'admin.domain.delete' | 'admin.impersonate';
 /**
  * Activity events visible to users in the dashboard
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shipstatic/types",
-  "version": "2.17.0",
+  "version": "2.18.0",
   "description": "Shared types for ShipStatic platform",
   "type": "module",
   "main": "./dist/index.js",

package/src/index.ts

@@ -2832,10 +2832,11 @@ export interface BillingSyncResponse {
  * All activity event types logged in the system.
  * Uses dot notation consistently: {resource}.{action}
  *
- * Retention: activity rows are permanent — the account's own history and
- * the platform's audit ledgers are one table, kept for the life of the
- * account (deletion removes them). Only the personal payload is
- * time-bounded: past 90 days each row sheds its IP.
+ * Retention: activity rows age out. An account keeps a recent window and,
+ * beneath it, never fewer than its most recent handful — so a dormant
+ * account's history is never empty — and a row that outlives the window
+ * keeps no IP address. Activity from deploys made without an account ages
+ * out sooner, and deleting an account removes its rows outright, at any age.
  */
 export type ActivityEvent =
   // Account events
@@ -2859,6 +2860,10 @@ export type ActivityEvent =
   | 'token.create'
   | 'token.consume'
   | 'token.delete'
+  // Billing events (internal: the operator's stream, never the customer's
+  // feed — the feed's copy of this fact is the `account.plan.transition` it
+  // may become)
+  | 'checkout.open'
   // Admin events (not user-visible)
   | 'admin.account.plan.update'
   | 'admin.account.suspended.update'
@@ -2868,10 +2873,17 @@ export type ActivityEvent =
   | 'admin.domain.delete'
   | 'admin.impersonate';
 
-// A subscription's own history is not logged here. What a plan change MEANS
-// is recorded once, as `account.plan.transition`; everything behind it
-// (invoices, refunds, disputes, retries) belongs to Stripe, which owns the
-// record and shows it to the customer in the Customer Portal.
+// The billing boundary: the stream records the PLATFORM'S own acts, and
+// Stripe records the subscription's life. `checkout.open` is ours — the
+// platform mints the Session, and it is the one billing act that exists
+// before Stripe holds anything. `account.plan.transition` is ours — what a
+// change MEANS, entitlement crossing our threshold. Everything between those
+// two edges (invoices, refunds, disputes, retries, scheduled changes) is the
+// subscription's own history, which belongs to Stripe as merchant of record
+// and is shown to the customer in the Customer Portal; none of it is
+// restated here. Refusals write no history either: the stream records what
+// happened to resources, never what was declined — a detection
+// (`deployment.flagged`) is a fact discovered about content, not a refusal.
 
 /**
  * Activity events visible to users in the dashboard