@volter/twin-stripe 3.0.0 → 3.0.1

package/src/engine/connect-settings.ts

@@ -1,23 +0,0 @@
-// The platform's Connect OAuth settings (its client_id, whether OAuth is on, its redirect URIs), which the Dashboard's
-// settings page saves (../screens/dashboard.tsx) and connect.stripe.com/oauth/authorize reads (../screens/connect-oauth.tsx).
-
-/** The platform's test client_id: the World's one platform (acct_twin_self) is the application it names. */
-export const PLATFORM_CLIENT_ID = 'ca_twin_self';
-export const SETTINGS_URL = 'https://dashboard.stripe.com/settings/connect/onboarding-options/oauth';
-/** The page's addresses: the docs' own, its test-mode link, and Connect's settings root. */
-export const CONNECT_SETTINGS_PATH = /^\/(test\/)?settings\/connect(\/onboarding-options\/oauth)?\/?$/;
-export const SETTINGS = '_connect_oauth_settings';
-
-export type ConnectOAuthSettings = { oauth_enabled: boolean; redirect_uris: string[] };
-
-/** The redirect URIs a form's field names, or the first one refused and why. */
-export function redirectUris(field: string): { uris: string[] } | { refused: string } {
-  const uris = [...new Set(field.split(/[\n,]/).map((s) => s.trim()).filter(Boolean))];
-  for (const uri of uris) {
-    let url: URL;
-    try { url = new URL(uri); } catch { return { refused: `${uri} is not a valid URL.` }; }
-    if (url.protocol !== 'https:' && url.protocol !== 'http:') return { refused: `${uri} must use http or https.` };
-    if (uri.includes('#')) return { refused: `${uri} must not contain a fragment.` };
-  }
-  return { uris };
-}

package/src/engine/coupons.ts

@@ -1,5 +0,0 @@
-// Coupon and PromotionCode semantics. A coupon is exactly one of percent_off or amount_off (with
-// its currency) over a duration; a promotion code is a customer-facing code for an existing
-// coupon, active until switched off (the machine in ../manifest.ts). Coupon list, retrieve, update
-// and delete and promotion-code retrieve and update (`active`, the machine) are the derived core's.
-

package/src/engine/credit-notes.ts

@@ -1,6 +0,0 @@
-// Credit note semantics. A credit note credits part of an invoice: pre_payment while the invoice
-// is unpaid (it lowers what is owed), post_payment once paid. The invoice carries the sums of its
-// issued credit notes, re-derived on every change so voiding one returns the invoice to where it
-// was. The machine in ../manifest.ts says a credit note is voided once. The list is the derived core's.
-
-export const CN = 'credit_note';

package/src/engine/disputes.ts

@@ -1,9 +0,0 @@
-// Dispute semantics. A dispute is Stripe's to open, when a charge's cardholder disputes it: the test cards
-// that are disputed open one as their charge succeeds (./after-payment.ts). It is then listed, retrieved,
-// updated with evidence and closed. Closing concedes it (status → lost), the machine's move in
-// ../manifest.ts. Evidence is submitted with the update unless `submit` is false
-// (docs.stripe.com/api/disputes/update#update_dispute-submit), and the bank then decides it: in test mode, evidence whose
-// uncategorized_text is `winning_evidence` wins it and `losing_evidence` loses it (docs.stripe.com/testing#evidence);
-// a won dispute returns the disputed amount. Where the documentation stops and the twin decides: the bank decides at
-// once, and any other evidence leaves the dispute under review. List is the derived core's.
-

package/src/engine/entitlements.ts

@@ -1,5 +0,0 @@
-// Entitlements semantics: features (unique by lookup_key) that products grant, and the features a
-// customer is entitled to now, derived from its live subscriptions' products. Feature retrieve is
-// the derived core's.
-
-export const FEAT = 'entitlements.feature';

package/src/engine/ephemeral-keys.ts

@@ -1,3 +0,0 @@
-// Ephemeral key semantics: the short-lived key the mobile SDKs use, scoped to exactly one object.
-// It needs the Stripe-Version header; its secret is answered only by the create; deleting it
-// expires it early.

package/src/engine/front.ts

@@ -1,31 +0,0 @@
-// What a publishable key may call, as data the handlers' shared checks read (../semantics/shared.ts
-// publishableKeyRefused, run by ../semantics/around.ts).
-import { expandOf, render, servesCurrent, withoutEndpointSecret } from './version.ts';
-
-type Row = Record<string, unknown>;
-
-// ── what a publishable key may call ──
-// "Publishable API key pk_... | Safe to expose: Yes | API key for Stripe.js, Elements, and mobile SDKs. It can identify
-// your account and create tokens or PaymentMethods from payment details, but it can't perform sensitive operations such
-// as creating charges or reading account data" (docs.stripe.com/keys). The served spec names the calls a publishable key
-// makes with an object's client secret: "You can retrieve a PaymentIntent client-side using a publishable key when the
-// client_secret is provided in the query string" (GET /v1/payment_intents/{intent}), "Client-side retrieval using a
-// publishable key is allowed when the client_secret is provided" (GET /v1/setup_intents/{intent}), "Required if a
-// publishable key is used to retrieve the source" (GET /v1/sources/{source}), and the confirm and verify_microdeposits
-// calls that take "The client secret of the PaymentIntent" (or SetupIntent). Anything else is refused with Stripe's
-// code: "secret_key_required | The API key provided is a publishable key, but a secret key is required"
-// (docs.stripe.com/error-codes), as 403, "The API key doesn't have permissions to perform the request"
-// (docs.stripe.com/api/errors).
-// Where the documentation stops and the twin decides: the list above is the whole of what a publishable key may call
-// (Stripe publishes no complete list); a client-secret call without the secret answers parameter_missing, and one with a
-// secret that is not the object's answers the object's 404, as though the key could not see it.
-export const PUBLISHABLE_CREATES = new Set(['PostTokens', 'PostPaymentMethods']);
-export const BY_CLIENT_SECRET: Record<string, { type: string; param: string }> = {
-  GetPaymentIntentsIntent: { type: 'payment_intent', param: 'intent' },
-  PostPaymentIntentsIntentConfirm: { type: 'payment_intent', param: 'intent' },
-  PostPaymentIntentsIntentVerifyMicrodeposits: { type: 'payment_intent', param: 'intent' },
-  GetSetupIntentsIntent: { type: 'setup_intent', param: 'intent' },
-  PostSetupIntentsIntentConfirm: { type: 'setup_intent', param: 'intent' },
-  PostSetupIntentsIntentVerifyMicrodeposits: { type: 'setup_intent', param: 'intent' },
-  GetSourcesSource: { type: 'source', param: 'source' },
-};

package/src/engine/payment-links.ts

@@ -1,6 +0,0 @@
-// Payment Link and Quote semantics. Both carry line items resolved from existing prices. A payment
-// link is a reusable hosted-checkout URL, active until switched off; a quote moves draft → open
-// (finalize) → accepted or canceled, the machine in ../manifest.ts. Link retrieve and update
-// (`active`, its machine), quote retrieve and the quote list are the derived core's.
-
-export const PL = 'payment_link';

package/src/engine/plans.ts

@@ -1,42 +0,0 @@
-// Plan semantics. Stripe's Prices API "replaces the Plans API and is backwards compatible" (docs.stripe.com/api/plans/create),
-// and "Existing plans can be used wherever recurring prices are accepted", a plan being one "which can be used
-// interchangeably with a price" (docs.stripe.com/billing/migration/migrating-prices). So a plan is stored as the recurring
-// price it is, under the plan's id, and the Plans API answers recurring prices in the plan's shape: a plan made here is
-// read, listed, updated and subscribed to as a price, and a recurring price made through the Prices API is a plan.
-// The plan's id: "An identifier randomly generated by Stripe ... You can optionally override this ID, but the ID must be
-// unique across all plans in your Stripe account" (the create page's `id`). `amount_decimal` is "Same as `amount`, but
-// accepts a decimal value with at most 12 decimal places. Only one of `amount` and `amount_decimal` can be set", and the
-// plan answers it as "a decimal string", its `amount` "a whole integer if possible" (spec/openapi.json.gz, the plan
-// object). Plan writes send the plan events, plan.created / plan.updated / plan.deleted, each carrying the plan object
-// (docs.stripe.com/api/events/types; the write hook renders it, ./stripe.ts afterStripeWrite). "Deleting plans
-// means new subscribers can't be added. Existing subscribers aren't affected." (docs.stripe.com/api/plans/delete), and
-// deleting one twice is an error. Where the documentation stops and the twin decides: a minted plan id is `plan_` over
-// the price counter, a duplicate id is refused with resource_already_exists, the refusals are worded by the twin, and only
-// the per_unit scheme is modelled (a tiered plan is refused, naming the gap); a deleted plan is gone from the Plans API
-// while the recurring price it was stays readable through the Prices API, inactive, so the subscription items that name
-// it still resolve (the docs do not say what the Prices API answers for it).
-import type { Row } from './common.ts';
-
-export const INTERVALS = new Set(['day', 'week', 'month', 'year']);
-
-/** A recurring price in the plan object's shape (the create page's example response). */
-export function planOf(price: Row): Row {
-  const r = (price.recurring ?? {}) as Row;
-  const amount = typeof price.unit_amount === 'number' ? price.unit_amount : null;
-  const decimal = typeof price.unit_amount_decimal === 'string' ? price.unit_amount_decimal : amount === null ? null : String(amount);
-  return {
-    id: price.id, object: 'plan', active: price.active ?? true, amount, amount_decimal: decimal,
-    billing_scheme: price.billing_scheme ?? 'per_unit', created: price.created, currency: price.currency, interval: r.interval ?? null,
-    interval_count: r.interval_count ?? 1, livemode: false, metadata: price.metadata ?? {}, meter: r.meter ?? null, nickname: price.nickname ?? null,
-    product: price.product, tiers_mode: price.tiers_mode ?? null, transform_usage: price.transform_quantity ?? null,
-    trial_period_days: r.trial_period_days ?? null, usage_type: r.usage_type ?? 'licensed',
-  };
-}
-
-/** Metadata after an update: an empty value unsets the key, an empty `metadata` unsets them all. */
-export function metadataAfter(was: Row, given: unknown): Row {
-  if (given === '' || given === null || typeof given !== 'object') return {};
-  const next: Row = { ...was };
-  for (const [k, v] of Object.entries(given as Row)) if (v === '' || v === null) delete next[k]; else next[k] = v;
-  return next;
-}

package/src/engine/platform.ts

@@ -1,47 +0,0 @@
-// Handler for Stripe's smaller products: Climate (a fixed product and supplier catalog, and
-// orders against it), Financial Connections (sessions, linked accounts, their transactions),
-// PAN forwarding requests, and Reporting (a report-type catalog and report runs, which the twin
-// completes at once). Lists and retrieves of what is stored are the derived core's.
-import type { Handler } from '@volter/world-core';
-import type { Row } from './common.ts';
-
-// ── Climate: Stripe's catalog is managed and account-independent. The twin serves the catalog Stripe's reference
-// publishes (docs.stripe.com/api/climate/product/object, /api/climate/supplier/object): Frontier's 2027 offtake
-// portfolio at $550 a ton plus Frontier's service fees of $16.50 (3%), 18,000 tons, from Charm Industrial.
-// Where the documentation stops and the twin decides: the catalog is that one product and supplier. ──
-
-export const CLIMATE_SUPPLIERS = [
-  { id: 'climsup_charm_industrial', name: 'Charm Industrial', removal_pathway: 'biomass_carbon_removal_and_storage', info_url: 'https://frontierclimate.com/portfolio/charm-industrial', locations: [{ city: 'San Francisco', country: 'US', latitude: 37.7749, longitude: -122.4194, region: 'CA' }] },
-] as const;
-export const CLIMATE_PRODUCTS = [
-  { id: 'climsku_frontier_offtake_portfolio_2027', name: "Frontier's 2027 offtake portfolio", subtotal: 55000, fees: 1650, currency: 'usd', delivery_year: 2027, metric_tons_available: '18000', created: 1881439203, suppliers: ['climsup_charm_industrial'] },
-] as const;
-export const supplierView = (s: (typeof CLIMATE_SUPPLIERS)[number]): Row => ({ id: s.id, object: 'climate.supplier', name: s.name, removal_pathway: s.removal_pathway, info_url: s.info_url, locations: s.locations, livemode: false });
-export const productView = (p: (typeof CLIMATE_PRODUCTS)[number]): Row => ({
-  id: p.id, object: 'climate.product', name: p.name, livemode: false, delivery_year: p.delivery_year,
-  metric_tons_available: p.metric_tons_available, created: p.created,
-  current_prices_per_metric_ton: { [p.currency]: { amount_fees: p.fees, amount_subtotal: p.subtotal, amount_total: p.subtotal + p.fees } },
-  suppliers: p.suppliers.map((id) => supplierView(CLIMATE_SUPPLIERS.find((s) => s.id === id)!)),
-});
-
-export const ORDER = 'climate.order';
-
-// ── Financial Connections: a session is created for an account holder and its permissions; accounts
-// are linked in the authentication flow Stripe.js opens (../screens/financial-connections.tsx) ──
-
-export const FCS = 'financial_connections.session';
-export const FCA = 'financial_connections.account';
-export const FCT = 'financial_connections.transaction';
-
-// ── Reporting: a representative subset of Stripe's report types; a run succeeds at once ──
-
-export const REPORT_TYPES: Array<{ id: string; name: string }> = [
-  { id: 'balance.summary.1', name: 'Balance summary' },
-  { id: 'balance_change_from_activity.summary.1', name: 'Balance change from activity (summary)' },
-  { id: 'payouts.summary.1', name: 'Payouts (summary)' },
-  { id: 'payout_reconciliation.by_id.itemized.4', name: 'Payout reconciliation (itemized)' },
-];
-export const reportTypeView = (t: { id: string; name: string }): Row => ({
-  id: t.id, object: 'reporting.report_type', name: t.name, version: 1,
-  data_available_start: 0, data_available_end: 0, default_columns: null, updated: 0, livemode: false,
-});

package/src/engine/products.ts

@@ -1,3 +0,0 @@
-// Product and Price semantics, with the entitlement features granted to a product. Retrieve of a
-// product and the product and price updates (archiving and restoring by `active`, the machines in
-// ../manifest.ts) are the derived core's.

package/src/engine/setup-intents.ts

@@ -1,5 +0,0 @@
-// SetupIntent semantics. The machine in ../manifest.ts says which moves of `status` are legal and
-// what Stripe answers otherwise; these handlers compute what each move does. List, retrieve and
-// update are the derived core's.
-
-export const SI = 'setup_intent';

package/src/engine/subscription-schedules.ts

@@ -1,10 +0,0 @@
-// Subscription schedule semantics: a schedule drives a subscription through phases (items for a
-// duration). One made for a customer starts its subscription at once on the first phase's items. Cancel and
-// release end it, the machine's moves in ../manifest.ts. List and update are the derived core's.
-//
-// Where the documentation stops and the twin decides: the subscription a schedule starts raises no first invoice.
-import { addBillingInterval } from './stripe.ts';
-
-export const SS = 'subscription_schedule';
-
-export type Interval = Parameters<typeof addBillingInterval>[1];

package/src/engine/tax.ts

@@ -1,39 +0,0 @@
-// Stripe Tax semantics: tax rates, the account's tax settings (a singleton), calculations,
-// registrations, and the transactions that commit a calculation or reverse one. A calculation's
-// tax comes from one flat default rate so its amounts are stable (Stripe derives it from the
-// customer's jurisdiction and the account's registrations). Rate, calculation, registration and
-// transaction retrieves and the registration list are the derived core's.
-import type { Row } from './common.ts';
-
-export const TWIN_TAX_RATE_PCT = 10;
-
-// ── settings: active once a head office is set; the answer has no id ──
-
-// the defaults' provider: "The tax calculation provider this account uses. Defaults to `stripe` when not using a
-// third-party provider" (the served spec's tax settings defaults); the head office's address answers each line, the
-// lines not given null (the served spec's address: each "(string, nullable)"; the settings page's example answers
-// line2 null)
-export const ADDRESS_LINES = ['city', 'country', 'line1', 'line2', 'postal_code', 'state'];
-export function settingsBody(stored: Row | undefined): Row {
-  const given = (stored?.head_office ?? null) as Row | null;
-  const address = given && typeof given.address === 'object' && given.address ? (given.address as Row) : undefined;
-  const headOffice = given ? { ...given, ...(address ? { address: Object.fromEntries(ADDRESS_LINES.map((k) => [k, address[k] ?? null])) } : {}) } : null;
-  const active = !!headOffice;
-  return {
-    object: 'tax.settings', livemode: false,
-    defaults: { provider: 'stripe', ...((stored?.defaults as Row) ?? { tax_behavior: null, tax_code: null }) }, head_office: headOffice,
-    status: active ? 'active' : 'pending',
-    status_details: active ? { active: {} } : { pending: { missing_fields: ['head_office'] } },
-  };
-}
-
-// ── transactions: committing a calculation, or reversing a transaction with negated amounts ──
-
-export const TX = 'tax.transaction';
-export const txLine = (id: string, i: number, l: Row, sign: 1 | -1, reversal: Row | null, type: string): Row => ({
-  object: 'tax.transaction_line_item', id: `tax_li_${id}_${i + 1}`,
-  amount: sign === 1 ? l.amount : -(Number(l.amount) || 0), amount_tax: sign === 1 ? l.amount_tax : -(Number(l.amount_tax) || 0),
-  reference: l.reference ?? null, tax_behavior: l.tax_behavior ?? 'exclusive', tax_code: l.tax_code ?? 'txcd_99999999',
-  quantity: l.quantity ?? 1, reversal, type, livemode: false, metadata: {},
-});
-export const linesOf = (holder: Row): Row[] => (holder.line_items as { data?: Row[] } | undefined)?.data ?? [];

package/src/engine/terminal.ts

@@ -1,23 +0,0 @@
-// Terminal and top-up semantics: in-person locations, readers (handed a PaymentIntent to process)
-// and their configurations, the reader SDK's connection tokens, and top-ups that fund the balance
-// (a test top-up succeeds at once; only a pending one cancels, the machine in ../manifest.ts). In test mode a
-// simulated reader is presented a card by a test helper: the PaymentIntent the reader is processing is paid with a
-// card_present payment method (succeeded, or requires_capture under manual capture) and the reader's action succeeds
-// (docs.stripe.com/terminal/references/testing#simulated-test-cards,
-// docs.stripe.com/api/terminal/readers/present_payment_method). Where the documentation stops and the twin decides:
-// the presented card is the simulated reader's default Visa, and the reader answers at once.
-// Lists and retrieves are the derived core's.
-
-export const LOC = 'terminal.location';
-export const READER = 'terminal.reader';
-export const CONF = 'terminal.configuration';
-
-// ── top-ups ──
-
-// a top-up adds money to the balance it names, through the ledger, once its funds arrive: "USA (USD) ACH Debit Transfer
-// 5 days" (docs.stripe.com/connect/top-ups), and to the Issuing balance alike: "Top-ups debit your bank account. Your
-// top-ups can take up to 5 business days to become available. While they're pending, they won't be added to your
-// Issuing balance" (docs.stripe.com/issuing/funding/balance). It is pending until its expected_availability_date, then
-// settled by settleTopups. Where the documentation stops and the twin decides: every top-up takes exactly five days,
-// whatever its currency and balance, and succeeds.
-export const TOPUP_DAYS = 5;

package/src/engine/test-clocks.ts

@@ -1,11 +0,0 @@
-// Test clock semantics. A test clock is Stripe's own door for a transition no API verb makes: the
-// passage of time. Advancing it moves the subscriptions of the clock's customers as a real clock tick does:
-// trials that ended end, and periods that ended renew (./renewals.ts advanceBilling). List, retrieve and delete are
-// the derived core's.
-
-export const CLOCK = 'test_helpers.test_clock';
-
-/** How long an advance takes: "it takes a few seconds to advance to the specified time"
- *  (docs.stripe.com/billing/testing/test-clocks/api-advanced-usage). Where the documentation stops and the twin decides:
- *  five seconds of World time from the advance. */
-export const ADVANCE_SECONDS = 5;

package/src/engine/tokens.ts

@@ -1,22 +0,0 @@
-// Token semantics: the older integrations' single-use tokens for a card, a bank account or PII. A
-// token carries only the safe fields of its instrument, never the card or account number. Retrieve
-// is the derived core's.
-import { paymentMethodSubObject } from './stripe.ts';
-import type { Row } from './common.ts';
-
-/** The Card object a card token carries, as the served spec's `card` describes it: its brand as a name ("Card brand.
- *  Can be `American Express`, ... `MasterCard`, `UnionPay`, `Visa`, or `Unknown`"), the holder's name and address as
- *  given ("Cardholder name"), and the CVC's check when one was given ("If a CVC was provided, results of the check:
- *  pass, fail, unavailable, or unchecked"). Where the documentation stops and the twin decides: a test card's CVC passes. */
-export const BRAND_NAMES: Record<string, string> = { amex: 'American Express', cartes_bancaires: 'Cartes Bancaires', diners: 'Diners Club', discover: 'Discover', eftpos_au: 'Eftpos Australia', girocard: 'Girocard', jcb: 'JCB', mastercard: 'MasterCard', unionpay: 'UnionPay', visa: 'Visa' };
-export function legacyCard(id: string, card: Row): Row {
-  const pm = paymentMethodSubObject('card', { card }).card as Row;
-  const given = (k: string): unknown => (typeof card[k] === 'string' && card[k] !== '' ? card[k] : null);
-  return {
-    id, object: 'card', brand: BRAND_NAMES[String(pm.brand)] ?? 'Unknown', last4: pm.last4, exp_month: pm.exp_month, exp_year: pm.exp_year,
-    funding: pm.funding ?? 'credit', country: pm.country ?? null, fingerprint: pm.fingerprint ?? null, name: given('name'),
-    address_line1: given('address_line1'), address_line2: given('address_line2'), address_city: given('address_city'), address_state: given('address_state'),
-    address_zip: given('address_zip'), address_country: given('address_country'), address_line1_check: null, address_zip_check: null,
-    cvc_check: card.cvc !== undefined && card.cvc !== '' ? 'pass' : null, dynamic_last4: null, tokenization_method: null, metadata: {}, customer: null,
-  };
-}

package/src/engine/treasury.ts

@@ -1,47 +0,0 @@
-// Treasury semantics: financial accounts and the flows that move their money (outbound payments
-// and transfers, inbound transfers), each posting a double entry to the account's ledger (a
-// transaction and its entry). An outbound flow stays processing (cancelable) until the network
-// settles it; an inbound transfer settles at once, as in test mode. The machines in
-// ../manifest.ts say which flows cancel. Lists and retrieves with no required scope are the
-// derived core's.
-import type { Row } from './common.ts';
-
-export const FA = 'treasury.financial_account';
-export const TX = 'treasury.transaction';
-export const ENTRY = 'treasury.transaction_entry';
-export const ENTRY_TYPES = new Set(['credit_reversal', 'debit_reversal', 'inbound_transfer', 'inbound_transfer_return', 'issuing_authorization_hold', 'issuing_authorization_release', 'outbound_payment', 'outbound_transfer', 'received_credit', 'received_debit']);
-
-/** A financial account's features as the served spec's treasury.financial_account_features gives them: a toggle
- *  (card_issuing, deposit_insurance, intra_stripe_flows) or a feature per network (financial_addresses.aba,
- *  inbound_transfers.ach, outbound_payments.ach and .us_domestic_wire, outbound_transfers likewise), each
- *  { requested, status, status_details }. What a request asks for is laid over what the account had. Where the
- *  documentation stops and the twin decides: a requested feature is active at once (test mode), and one never requested
- *  is left out (each is optional in the served spec). Answers the features and the active features' paths. */
-export const NETWORKS: Record<string, string[]> = { financial_addresses: ['aba'], inbound_transfers: ['ach'], outbound_payments: ['ach', 'us_domestic_wire'], outbound_transfers: ['ach', 'us_domestic_wire'] };
-export const TOGGLES = ['card_issuing', 'deposit_insurance', 'intra_stripe_flows'];
-export function featuresOf(requested: Row, had: Row = {}): { features: Row; active: string[] } {
-  const on = (v: unknown): boolean => v === true || v === 'true';
-  const setting = (asked: boolean) => ({ requested: asked, status: asked ? 'active' : 'restricted', status_details: [] });
-  const features: Row = { ...had };
-  for (const t of TOGGLES) {
-    const r = requested[t] as Row | undefined;
-    if (r && typeof r === 'object' && r.requested !== undefined) features[t] = setting(on(r.requested));
-  }
-  for (const [f, nets] of Object.entries(NETWORKS)) {
-    const r = requested[f] as Row | undefined;
-    if (!r || typeof r !== 'object') continue;
-    const current = (features[f] as Row | undefined) ?? {};
-    const next: Row = { ...current };
-    for (const n of nets) {
-      const nr = r[n] as Row | undefined;
-      if (nr && typeof nr === 'object' && nr.requested !== undefined) next[n] = setting(on(nr.requested));
-    }
-    features[f] = next;
-  }
-  const active: string[] = [];
-  for (const t of TOGGLES) if ((features[t] as Row | undefined)?.status === 'active') active.push(t);
-  for (const [f, nets] of Object.entries(NETWORKS)) for (const n of nets) if (((features[f] as Row | undefined)?.[n] as Row | undefined)?.status === 'active') active.push(`${f}.${n}`);
-  return { features, active };
-}
-
-export const noTransitions = { canceled_at: null, failed_at: null, posted_at: null, returned_at: null };