@volter/twin-polar

Local Polar twin for app tests that need customer, checkout, subscription, meter, and usage-event behavior without real Polar credentials.

bun packages/twin/polar/src/cli.ts

Coverage

The capability manifest (src/polar-capabilities.ts) is an honest partial denominator for Polar's merchant-of-record API. Coverage is partial and will read low as the denominator grows — see the manifest's todo entries for what is enumerated but not yet modeled.

Modeled: customers, products, checkouts, subscriptions, orders, benefits, meters and usage-events, license keys, discounts, webhooks, OAuth, and the connector's pull/push.

Out of scope (each genuinely impossible for a local twin, with the reason recorded on the capability):

• polar.payments.real_processing — a local twin must not contact or emulate real card networks; it returns deterministic checkout/order shapes and "confirms" payment offline.
• polar.tax.real_calculation — tax-authority integrations and live jurisdiction rules are outside a deterministic local twin.

UI mirror — a tracked gap

This pack ships no mirror UI, and that is an unfinished gap rather than a decision. Polar is a merchant-of-record billing product with a real operator dashboard — the same shape as stripe, which does mirror — so under the rule in ../../../docs/contributing/adding-a-twin.md ("Does this vendor get a mirror?") it should have one. The work is tracked in the manifest as polar.mirror.ui (operator mirror for customers/subscriptions/orders/events).

Do not cite this pack as precedent for omitting a mirror.