@volter/twin-stripe 0.1.2 → 2.0.0

package/dist/test-fixtures/stripe-schemas.SOURCE.md

@@ -0,0 +1,35 @@
+# stripe-schemas.json — provenance
+
+Per-object JSON Schemas for the Stripe resources the twin serves, used by the
+Stripe spec-conformance gate (`src/stripe-conformance.ts`). Stripe is the twin we
+CANNOT dual-run against a live sandbox, so the published OpenAPI is the authority.
+
+- **Source:** `https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json`
+- **Repo:** `stripe/openapi` (Stripe's public OpenAPI) — MIT licensed
+- **Fetched:** 2026-06-14 (base set); 2026-08-24 (Issuing objects: `issuing.authorization`,
+  `issuing.card`, `issuing.cardholder`, `issuing.transaction` — spec version `2026-07-29.dahlia`,
+  same projection: `required` + per top-level property `type`/`enum`/`nullable`,
+  polymorphic `anyOf`/`oneOf`/`$ref` fields left untyped)
+- **Projection (`components.schemas.<object>` → flat schema):** for each served object
+  (charge, customer, payment_intent, refund, subscription, setup_intent,
+  payment_method, price, product, invoice, invoiceitem, dispute, payout,
+  balance_transaction, balance, event, `checkout.session`, `billing_portal.session`,
+  `billing_portal.configuration`) we keep `required` plus, per
+  top-level property: its `type`, `enum`, and `nullable`. Polymorphic Stripe fields
+  (`anyOf`/`oneOf`/`$ref` — e.g. `customer` is id|object|null) are left UNTYPED so the
+  harness treats them as "any" (no false type/extra positives on opaque sub-objects).
+
+## Why this replaces stripe-schema-fields.json
+
+The old fixture kept `{ object: { field: type } }` — names + types, but no `required`
+and no `enum`. So the gate was blind to OMISSION (a required field the twin fails to
+emit) and to enum violations. This projection adds both, validated through the shared
+`specConformance` harness. Surfaced + fixed real drift: a fabricated `livemode` on
+`refund`, and `invoiceitem` emitting `created` where Stripe uses `date`.
+
+Fields the twin does not emit are declared in `stripe-known-deviations.json`.
+
+## Refresh
+
+Re-fetch spec3.json, re-run the projection (see stripe-conformance history), and
+re-run `bun test src/stripe-conformance.test.ts` when Stripe ships schema changes.