sinfactura-types 1.10.642 → 1.10.643

package/dist/cjs/socket.js

@@ -581,7 +581,7 @@ exports.SOCKET_ACTIONS = [
     // ⚠️ A frame for a period whose `periodStatus` is `'OPEN'` carries numbers
     // ML will still restate; a consumer must not render one as final.
     'mercadolibre_settlement_period',
-    // BE → all store users when an EMPRESA custom domain's provisioning state
+    // BE → all store users when an avanzado custom domain's provisioning state
     // moves (`CustomDomainSocketPayload`). Status only: the row's
     // `verificationToken` is an ownership credential and is never re-sent here.
     'customDomain',

package/dist/cjs/store.js

@@ -1,2 +1,20 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.CUSTOM_DOMAIN_ROW_LIMIT = exports.CUSTOM_DOMAIN_SLOT_LIMIT = void 0;
+/**
+ * How many custom-domain rows a store may hold that count: one active domain
+ * and one spare, so a replacement can be verified and provisioned before the
+ * current domain is revoked. `www` and the apex are one row. REVOKED rows and
+ * expired PENDING claims never count. `POST /store/domains { mode: 'register' }`
+ * refuses the next one `409 DOMAIN_SLOT_LIMIT` with this value as `limit`.
+ */
+exports.CUSTOM_DOMAIN_SLOT_LIMIT = 2;
+/**
+ * How many DOMAIN rows a store may hold in total, whatever their status:
+ * REVOKED rows free their `CUSTOM_DOMAIN_SLOT_LIMIT` slot but a
+ * VERIFIED-then-revoked row is kept, so without this ceiling a store cycling
+ * register → verify → revoke over fresh hosts would grow its rows without
+ * bound. `POST /store/domains { mode: 'register' }` refuses the next one
+ * `409 DOMAIN_ROW_LIMIT` with this value as `limit`.
+ */
+exports.CUSTOM_DOMAIN_ROW_LIMIT = 10;

package/dist/socket.d.ts

@@ -42,7 +42,15 @@ export interface CustomDomainSocketPayload {
     host: string;
     provisioning: {
         state: DomainProvisioningState;
+        /** 1-based; see `DomainProvisioning.step`. */
+        step?: number;
+        /** See `DomainProvisioning.total`. */
+        total?: number;
+        /** See `DomainProvisioning.records`. */
+        records?: DomainDnsRecord[];
+        /** @deprecated Read `records`; see `DomainProvisioning.certificateVerificationDnsRecord`. */
         certificateVerificationDnsRecord?: string;
+        /** @deprecated Read `records`; see `DomainProvisioning.subDomains`. */
         subDomains?: DomainSubDomainRecord[];
         /** Unix MILLISECONDS. Present once `state` reaches `active`. */
         activatedAt?: number;

package/dist/socket.js

@@ -578,7 +578,7 @@ export const SOCKET_ACTIONS = [
     // ⚠️ A frame for a period whose `periodStatus` is `'OPEN'` carries numbers
     // ML will still restate; a consumer must not render one as final.
     'mercadolibre_settlement_period',
-    // BE → all store users when an EMPRESA custom domain's provisioning state
+    // BE → all store users when an avanzado custom domain's provisioning state
     // moves (`CustomDomainSocketPayload`). Status only: the row's
     // `verificationToken` is an ownership credential and is never re-sent here.
     'customDomain',

package/dist/store.d.ts

@@ -1515,28 +1515,45 @@ declare global {
      * Lifecycle of a tenant custom-domain claim.
      *
      * `REVOKED` is terminal but reclaimable BY THE SAME STORE only: re-registering
-     * a REVOKED host the caller already owns succeeds, while a PENDING or
-     * VERIFIED row owned by anyone else refuses the write. Revoked rows are kept
-     * for audit and squatter-protection and still consume one of the store's
-     * domain slots — see `DomainErrorCode`.
+     * a REVOKED or PENDING host the caller already owns succeeds (a PENDING one is
+     * re-minted with a fresh token and a fresh seven-day claim), while a PENDING
+     * or VERIFIED row owned by anyone else — or the caller's own VERIFIED row —
+     * refuses the write. A row revoked AFTER verification is kept for audit and
+     * squatter-protection and does NOT count against the store's domain slots
+     * (`CUSTOM_DOMAIN_SLOT_LIMIT`): revoking a row frees its slot. It does count
+     * against `CUSTOM_DOMAIN_ROW_LIMIT`. A claim revoked by its store BEFORE
+     * verification is deleted instead — it proved no ownership, so it protects
+     * nothing — and stops appearing in the listing.
+     * A PENDING row counts while its seven-day claim is unexpired, and cannot be
+     * verified once that claim has expired; a VERIFIED row always counts — see
+     * `DomainErrorCode`.
      */
     type DomainStatus = 'PENDING' | 'VERIFIED' | 'REVOKED';
     /**
-     * Where EMPRESA custom-domain provisioning stands for a VERIFIED host. The
-     * ownership flow (register → DNS-TXT verify) is unchanged and precedes this;
-     * provisioning is what the platform does with a host once it is proven.
+     * Where custom-domain provisioning stands for a VERIFIED host. The ownership
+     * flow (register → DNS-TXT verify) is unchanged and precedes this;
+     * provisioning is what the platform does with a host once it is proven. The
+     * states name no hosting provider and keep their meaning whichever one serves
+     * the host.
      *
-     * - `pending_dns` — the association exists; waiting on the tenant to add the
-     *   CNAME records the hosting provider asked for.
+     * - `pending_dns` — provisioning has started; waiting on the tenant to publish
+     *   the DNS records in `DomainProvisioning.records`.
      * - `in_progress` — DNS looks right; the certificate is being issued and the
      *   domain deployed.
-     * - `active` — the provider reports the domain live.
-     * - `failed` — the provider reported a failure, or no progress for 48 h.
-     * - `unconfigured` — this stage has no hosting-app id configured, so
-     *   provisioning cannot start here. A deployment fact, not a tenant fault.
+     * - `active` — the domain is live.
+     * - `failed` — provisioning failed, including the certificate not issuing
+     *   within 72 h. A new `provision` call starts a fresh attempt.
+     * - `unconfigured` — this stage cannot onboard custom domains. A deployment
+     *   fact, not a tenant fault: offer no retry.
      */
     type DomainProvisioningState = 'pending_dns' | 'in_progress' | 'active' | 'failed' | 'unconfigured';
-    /** One sub-domain of a provisioned host, mirroring the hosting provider's own per-prefix record. */
+    /**
+     * One sub-domain of a provisioned host, mirroring a hosting provider's own
+     * per-prefix record.
+     *
+     * @deprecated Read `DomainProvisioning.records` (`DomainDnsRecord`). Kept
+     * readable until rows written in this shape are gone; no new writer.
+     */
     interface DomainSubDomainRecord {
         /** `''` for the apex, `'www'` etc. */
         prefix: string;
@@ -1547,18 +1564,54 @@ declare global {
         dnsRecord?: string;
         verified: boolean;
     }
+    /**
+     * One DNS record the tenant must publish for a custom domain to provision.
+     * Show `name` and `value` verbatim; never re-derive or re-prefix either.
+     */
+    interface DomainDnsRecord {
+        /**
+         * The normalised host this record serves (`www.example.com`,
+         * `example.com`). Group the records by it.
+         */
+        host: string;
+        type: 'CNAME' | 'TXT' | 'ALIAS';
+        /** Fully qualified: most DNS forms append the zone, so say so when showing it. */
+        name: string;
+        value: string;
+        /** The per-record DNS check. */
+        status: 'pending' | 'verified';
+    }
     /**
      * Provisioning sub-state carried on the SAME `DomainRecord` row — a domain is
      * one entity, not two. Absent until provisioning has been attempted for the
      * host, which is every row written before this shipped.
      *
+     * Provider-neutral: `step`/`total` and `records` describe progress without
+     * naming who serves the host. A row may carry neither, in which case show no
+     * step counter and no record list — never a client-side step constant.
+     *
      * Timestamps are **Unix MILLISECONDS**, the same unit as `createdAt` /
      * `verifiedAt` on the enclosing row.
      */
     interface DomainProvisioning {
         state: DomainProvisioningState;
-        /** The provider's certificate-validation CNAME instruction — shown to the tenant once, verbatim. */
+        /** 1-based position of the current step. Hide the counter when this or `total` is absent. */
+        step?: number;
+        /** Number of steps, decided by the server. */
+        total?: number;
+        /** The DNS records the tenant must publish, one or more per host. */
+        records?: DomainDnsRecord[];
+        /**
+         * A certificate-validation CNAME instruction — shown to the tenant once, verbatim.
+         *
+         * @deprecated Read `records`. Kept readable until rows written in this
+         * shape are gone; no new writer.
+         */
         certificateVerificationDnsRecord?: string;
+        /**
+         * @deprecated Read `records`. Kept readable until rows written in this
+         * shape are gone; no new writer.
+         */
         subDomains?: DomainSubDomainRecord[];
         /** Unix MILLISECONDS — last time the poller checked the provider. Operator diagnostic, not tenant-facing. */
         lastCheckedAt?: number;
@@ -1604,7 +1657,7 @@ declare global {
         verifiedAt?: number;
         /** Unix MILLISECONDS. Present once the claim has been revoked. */
         revokedAt?: number;
-        /** Present only once EMPRESA provisioning has been attempted for this VERIFIED host. */
+        /** Present only once avanzado provisioning has been attempted for this VERIFIED host. */
         provisioning?: DomainProvisioning;
     }
     /**
@@ -1700,9 +1753,18 @@ declare global {
      * deliberately NOT gated by the unclaimable-host guard that `register` and
      * `verify` apply — a row that should never have existed can always be undone.
      *
-     * ⚠️ Revoking does not free a domain slot. The row survives as `REVOKED` for
-     * audit and squatter-protection and still counts against the per-store cap,
-     * so `DOMAIN_LIMIT_REACHED` cannot be cleared by revoking.
+     * Revoking frees the row's domain slot: a VERIFIED row survives as
+     * `REVOKED` for audit and squatter-protection but no longer counts against
+     * `CUSTOM_DOMAIN_SLOT_LIMIT`, so revoking clears `DOMAIN_SLOT_LIMIT`. A
+     * claim that was never verified is deleted rather than kept — the same 200,
+     * and the host is gone from the next listing — which also gives back its
+     * `CUSTOM_DOMAIN_ROW_LIMIT` row.
+     *
+     * Revoking a provisioned row deprovisions it first, in the same request —
+     * there is no refusal asking the tenant to deprovision before revoking. When
+     * the revoked row was the store's public custom domain, `publicStorefront`
+     * moves to the next active row, else back to the slug host, and one `stores`
+     * frame announces it.
      */
     interface DomainRevokeResult {
         /**
@@ -1721,14 +1783,24 @@ declare global {
      * `body.error` codes a `POST /store/domains` refusal can carry, each verified
      * against a return site in the handler.
      *
-     * - `DOMAIN_LIMIT_REACHED` (**429**, `register`) — the store already holds its
-     *   maximum number of DOMAIN rows. ⚠️ REVOKED rows still occupy a slot, so a
-     *   store can hit this with no live domain at all, and revoking more does not
-     *   free capacity. Carries a numeric `limit` alongside `error` and — alone
-     *   among these codes — NO `message`, so a UI rendering `body.message`
-     *   verbatim shows an empty error here.
+     * - `DOMAIN_SLOT_LIMIT` (**409**, `register`) — the store already holds
+     *   `CUSTOM_DOMAIN_SLOT_LIMIT` rows that count: every row that is not REVOKED,
+     *   except a PENDING row whose seven-day claim has expired and the row of the
+     *   host being registered. Body `{ message, error, limit }`, `limit` being
+     *   `CUSTOM_DOMAIN_SLOT_LIMIT`. Revoking a row frees its slot.
+     * - `DOMAIN_ROW_LIMIT` (**409**, `register`) — the store already holds
+     *   `CUSTOM_DOMAIN_ROW_LIMIT` DOMAIN rows of any status, REVOKED and expired
+     *   PENDING included, other than the row of the host being registered.
+     *   Body `{ message, error, limit }`, `limit` being `CUSTOM_DOMAIN_ROW_LIMIT`.
+     *   Checked before `DOMAIN_SLOT_LIMIT`. Revoking a VERIFIED row does not
+     *   clear it (that row is kept); revoking a never-verified claim does
+     *   (that row is deleted). Otherwise it needs support, not a retry.
+     * - `DOMAIN_LIMIT_REACHED` (**429**, `register`) — the previous cap's code.
+     *   No current writer; a stage one release behind still answers it, with a
+     *   `message` and a numeric `limit`, and counted REVOKED rows too.
      * - `DOMAIN_OWNED_BY_OTHER_STORE` (**409**, `register`) — a PENDING or
-     *   VERIFIED row for this host belongs to a different store.
+     *   VERIFIED row for this host belongs to a different store, or the host is
+     *   already this store's VERIFIED domain.
      * - `DOMAIN_NOT_CLAIMABLE` (**409**, `register` AND `verify`) — the host is
      *   not any single store's: a storefront apex serving many tenants, or a
      *   platform origin already on the static CORS allowlist. Permanent for that
@@ -1743,6 +1815,24 @@ declare global {
      * present at all. A consumer switching on `body.error` alone silently misses
      * the verify case and falls through to a generic message.
      */
-    type DomainErrorCode = 'DOMAIN_LIMIT_REACHED' | 'DOMAIN_OWNED_BY_OTHER_STORE' | 'DOMAIN_NOT_CLAIMABLE' | 'NOT_OWNER';
+    type DomainErrorCode = 'DOMAIN_SLOT_LIMIT' | 'DOMAIN_ROW_LIMIT'
+    /** @deprecated No writer; answered only by a stage one release behind. Map it like `DOMAIN_SLOT_LIMIT`. */
+     | 'DOMAIN_LIMIT_REACHED' | 'DOMAIN_OWNED_BY_OTHER_STORE' | 'DOMAIN_NOT_CLAIMABLE' | 'NOT_OWNER';
 }
-export {};
+/**
+ * How many custom-domain rows a store may hold that count: one active domain
+ * and one spare, so a replacement can be verified and provisioned before the
+ * current domain is revoked. `www` and the apex are one row. REVOKED rows and
+ * expired PENDING claims never count. `POST /store/domains { mode: 'register' }`
+ * refuses the next one `409 DOMAIN_SLOT_LIMIT` with this value as `limit`.
+ */
+export declare const CUSTOM_DOMAIN_SLOT_LIMIT = 2;
+/**
+ * How many DOMAIN rows a store may hold in total, whatever their status:
+ * REVOKED rows free their `CUSTOM_DOMAIN_SLOT_LIMIT` slot but a
+ * VERIFIED-then-revoked row is kept, so without this ceiling a store cycling
+ * register → verify → revoke over fresh hosts would grow its rows without
+ * bound. `POST /store/domains { mode: 'register' }` refuses the next one
+ * `409 DOMAIN_ROW_LIMIT` with this value as `limit`.
+ */
+export declare const CUSTOM_DOMAIN_ROW_LIMIT = 10;

package/dist/store.js

@@ -1 +1,17 @@
-export {};
+/**
+ * How many custom-domain rows a store may hold that count: one active domain
+ * and one spare, so a replacement can be verified and provisioned before the
+ * current domain is revoked. `www` and the apex are one row. REVOKED rows and
+ * expired PENDING claims never count. `POST /store/domains { mode: 'register' }`
+ * refuses the next one `409 DOMAIN_SLOT_LIMIT` with this value as `limit`.
+ */
+export const CUSTOM_DOMAIN_SLOT_LIMIT = 2;
+/**
+ * How many DOMAIN rows a store may hold in total, whatever their status:
+ * REVOKED rows free their `CUSTOM_DOMAIN_SLOT_LIMIT` slot but a
+ * VERIFIED-then-revoked row is kept, so without this ceiling a store cycling
+ * register → verify → revoke over fresh hosts would grow its rows without
+ * bound. `POST /store/domains { mode: 'register' }` refuses the next one
+ * `409 DOMAIN_ROW_LIMIT` with this value as `limit`.
+ */
+export const CUSTOM_DOMAIN_ROW_LIMIT = 10;

package/package.json

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