platform-types 1.10.699 → 1.10.701

package/dist/subscription.js

@@ -22,4 +22,71 @@
  *   declared here even when their epics haven't shipped — the matrix can set
  *   enabled:false until they do.
  */
-export {};
+/*
+ * Runtime tuples for the unions above.
+ *
+ * A union alone cannot be iterated, and any consumer that needs to enumerate
+ * every tier or key — zeroing a breakdown, fanning a query across tiers,
+ * rendering a pricing table's rows — otherwise hand-rolls its own copy that
+ * compiles fine while silently omitting a member. A missing member is not a
+ * visible break: it is a bucket that reads zero forever, or a row that never
+ * renders.
+ *
+ * ⚠️ `satisfies readonly PlanTier[]` alone does NOT catch that — it checks each
+ * element IS a tier, never that every tier is present. Hence `exhaustiveTuple`,
+ * whose second type parameter fails to resolve unless the tuple covers the
+ * union, making an omission a compile error at the tuple itself. Module-private
+ * on purpose: it is a type-level trick, not part of the published surface.
+ */
+const exhaustiveTuple = () => (tuple) => tuple;
+/** Every plan tier, in rank order (lowest first). */
+export const PLAN_TIERS = exhaustiveTuple()(['basico', 'emprendedor', 'profesional', 'avanzado']);
+/**
+ * Every gated feature key.
+ *
+ * ⚠️ Adding a member here is not the whole change, and `typecheck` is what
+ * stops it shipping half-done. In the api, a new key needs a grant in **every
+ * tier** of `PLAN_FEATURES` (`stacks/services/planFeatureMatrix.ts`): that
+ * constant is typed total over every `PlanTier` × `FeatureKey` cell, so a tier
+ * missing the new key's grant, or a grant of the wrong shape for the key's
+ * declared `type`, fails `typecheck` at the `PLAN_FEATURES` declaration
+ * itself. It also widens the api's per-store override key schema, so a new key
+ * immediately becomes a valid override target.
+ *
+ * ⚠️ **A new member also obliges an api PLATFORM-STACK deploy.** Entitlements
+ * resolve inside the Lambda authorizer, built in `PlatformStack`. Deploying only
+ * the handler stacks leaves a STALE authorizer running the previous matrix: the
+ * key is absent from the resolved map, where a boolean gate refuses but a
+ * metered / lifetime cap PASSES THROUGH — a new cap silently unbounded.
+ * Checklist: `docs/PLANS_AND_ENTITLEMENTS.md` in the api repo.
+ */
+export const FEATURE_KEYS = [
+    'afipInvoicing',
+    'suppliers',
+    'advancedReports',
+    'cashManagement',
+    'importExport',
+    'domesticPayments',
+    'stripePayments',
+    'whatsappCommerce',
+    'aiFeatures',
+    'mobileApp',
+    'customBranding',
+    'customDomain',
+    'prioritySupport',
+    'advancedPricing',
+    'marketplaceChannels',
+    'storefront',
+    'loyalty',
+    'marketing',
+    'mandatory2fa',
+    'maxUsers',
+    'maxProducts',
+    'maxCustomers',
+    'maxWarehouses',
+    'priceListsMax',
+    'webhooks',
+    'maxOrdersMonth',
+    'maxInvoicesMonth',
+    'whatsappMessages',
+];

package/dist/terminal.d.ts

@@ -452,8 +452,7 @@ declare global {
          * - `'mercadopago.refund'` — the MercadoPago `paymentId` being refunded. Required.
          * - `'shift.refund'` / `'shift.cash-out'` — the path `{id}` (the `shiftId`) of
          *   `POST /shifts/{id}/movements` ({@link ShiftMovementRequest}). Required.
-         * - `'cash.withdrawal'` ({@link CashPostRequest}), `'tip.cash-payout'`
-         *   ({@link TipPayoutRequest}) and `'account.cash-debit'`
+         * - `'cash.withdrawal'` ({@link CashPostRequest}) and `'account.cash-debit'`
          *   ({@link AccountPostRequest}) — the drawer (`shiftId`) the write itself
          *   resolves. **Omit it**: the API computes it at mint from the same `body`,
          *   READ-ONLY, with the derivation the write uses — the operator's own OPEN
@@ -464,7 +463,7 @@ declare global {
          *   A client never computes a drawer id.
          *
          * The four required subjects are refused by the mint's validation when
-         * missing (`400`). For the three drawer-bound actions the mint checks, before
+         * missing (`400`). For the two drawer-bound actions the mint checks, before
          * any PIN work, only the body fields it reads (`400 VALIDATION_FAILED`, paths
          * under `body`): `currency`, a cash edit's `cashId`, an account debit's
          * `customerId`. A `subjectId` naming any drawer other than the computed one
@@ -495,11 +494,11 @@ declare global {
      * fingerprint of the cash, account, shift-movement and deposit-refund
      * writes, so a retry carrying a FRESH token with the same key replays the
      * committed response instead of answering `422 IDEMPOTENCY_KEY_REUSE`. A
-     * body without a token fingerprints exactly as before. A tip payout replays
-     * by its `operationId`. A MercadoPago refund has no stored-response replay:
-     * its elevation is consumed before the refund claim, so a retry with the
-     * same token answers `403 ELEVATION_INVALID`, and a retry with a fresh one
-     * spends that approval and then meets the refund's own state (`409
+     * body without a token fingerprints exactly as before. A MercadoPago refund
+     * has no stored-response replay: its elevation is consumed before the refund
+     * claim, so a retry with the same token answers `403 ELEVATION_INVALID`, and
+     * a retry with a fresh one spends that approval and then meets the refund's
+     * own state (`409
      * MP_ALREADY_REFUNDED` once the payment is exhausted, `409
      * MP_REFUND_IN_PROGRESS` while another attempt holds the claim).
      */
@@ -647,7 +646,7 @@ export declare const PRINT_AGENT_SESSION_TTL_SECONDS: number;
 export declare const TERMINAL_ENROLMENT_TTL_SECONDS: number;
 export declare const TERMINAL_PAIRING_CODE_TTL_SECONDS: number;
 /** Money-out actions whose operator sessions require a different ADMIN-or-higher approver. */
-export declare const TERMINAL_ELEVATION_ACTIONS: readonly ["order.deposit-refund", "mercadopago.refund", "shift.refund", "shift.cash-out", "cash.withdrawal", "account.cash-debit", "tip.cash-payout"];
+export declare const TERMINAL_ELEVATION_ACTIONS: readonly ["order.deposit-refund", "mercadopago.refund", "shift.refund", "shift.cash-out", "cash.withdrawal", "account.cash-debit"];
 export type TerminalElevationAction = (typeof TERMINAL_ELEVATION_ACTIONS)[number];
 /**
  * Existing PIN, validation and idempotency refusals retain their current

package/dist/terminal.js

@@ -182,7 +182,6 @@ export const TERMINAL_ELEVATION_ACTIONS = [
     'shift.cash-out',
     'cash.withdrawal',
     'account.cash-debit',
-    'tip.cash-payout',
 ];
 /**
  * Existing PIN, validation and idempotency refusals retain their current

package/dist/webhook.d.ts

@@ -281,11 +281,6 @@ export interface PaymentReceivedWebhookPayload {
     invoiceId?: string;
     /** MP/Stripe-side `external_reference`, when the provider carried one. */
     externalReference?: string;
-    /** Goods and tip split, without worker or ledger operation identity. */
-    paymentTip?: {
-        orderAmount: number;
-        tipAmount: number;
-    };
 }
 /**
  * Payload for `product.stock_low` — a sale CROSSED `Product.minStock`

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "platform-types",
-	"version": "1.10.699",
+	"version": "1.10.701",
 	"description": "Shared wire and entity contracts for the platform.",
 	"type": "module",
 	"main": "dist/index.js",