@endora-commerce/platform 0.100.0

package/dist/migrations/20260721T011510_core_settings_credential_ref_value_type.js

@@ -0,0 +1,57 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Settings `credential_ref` value type (feature 058, US2).
+ *
+ * 1. Extends the `setting_value_type` Postgres enum with `'credential_ref'`.
+ *    The enum is recreated (rename → create → re-point column → drop old)
+ *    instead of `ALTER TYPE ... ADD VALUE` because the migrator runs with
+ *    `allOrNothing: true` (one master transaction) and PostgreSQL forbids
+ *    using an enum value added via ADD VALUE inside the same transaction.
+ *    Mirrors `069_settings_secret_value_type.ts`.
+ * 2. Adds the nullable `settings.configuration_type` column — the configuration
+ *    type a `credential_ref` setting is constrained to (upserted by the
+ *    reconciler from the manifest entry's `configurationType`).
+ *
+ * Filed under `core` since feature 072 T020. The kernel owns the tables this
+ * migration writes to, and a hard uninstall reverts by registry `moduleId`, so
+ * leaving it under `settings` made `modules:uninstall --hard settings` drop
+ * kernel schema.
+ */
+export class Migration20260721T011510CoreSettingsCredentialRefValueType extends Migration {
+    async up() {
+        this.addSql(`alter type "setting_value_type" rename to "setting_value_type_old";`);
+        this.addSql(`
+      create type "setting_value_type" as enum
+        ('string', 'number', 'boolean', 'json', 'string_list', 'secret', 'credential_ref');
+    `);
+        this.addSql(`
+      alter table "settings"
+        alter column "value_type" type "setting_value_type"
+        using "value_type"::text::"setting_value_type";
+    `);
+        this.addSql(`drop type "setting_value_type_old";`);
+        this.addSql(`alter table "settings" add column "configuration_type" varchar(64) null;`);
+    }
+    async down() {
+        this.addSql(`alter table "settings" drop column "configuration_type";`);
+        // Every credential_ref row must leave the enum value before the narrowing
+        // cast below.
+        this.addSql(`
+      update "settings"
+        set "value_type" = 'string'
+        where "value_type" = 'credential_ref';
+    `);
+        this.addSql(`alter type "setting_value_type" rename to "setting_value_type_old";`);
+        this.addSql(`
+      create type "setting_value_type" as enum
+        ('string', 'number', 'boolean', 'json', 'string_list', 'secret');
+    `);
+        this.addSql(`
+      alter table "settings"
+        alter column "value_type" type "setting_value_type"
+        using "value_type"::text::"setting_value_type";
+    `);
+        this.addSql(`drop type "setting_value_type_old";`);
+    }
+}
+//# sourceMappingURL=20260721T011510_core_settings_credential_ref_value_type.js.map

package/dist/migrations/20260721T011510_core_settings_credential_ref_value_type.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260721T011510_core_settings_credential_ref_value_type.js","sourceRoot":"","sources":["../../src/migrations/20260721T011510_core_settings_credential_ref_value_type.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,OAAO,0DAA2D,SAAQ,SAAS;IAC9E,KAAK,CAAC,EAAE;QACf,IAAI,CAAC,MAAM,CAAC,qEAAqE,CAAC,CAAC;QACnF,IAAI,CAAC,MAAM,CAAC;;;KAGX,CAAC,CAAC;QACH,IAAI,CAAC,MAAM,CAAC;;;;KAIX,CAAC,CAAC;QACH,IAAI,CAAC,MAAM,CAAC,qCAAqC,CAAC,CAAC;QAEnD,IAAI,CAAC,MAAM,CAAC,0EAA0E,CAAC,CAAC;IAC1F,CAAC;IAEQ,KAAK,CAAC,IAAI;QACjB,IAAI,CAAC,MAAM,CAAC,0DAA0D,CAAC,CAAC;QAExE,0EAA0E;QAC1E,cAAc;QACd,IAAI,CAAC,MAAM,CAAC;;;;KAIX,CAAC,CAAC;QACH,IAAI,CAAC,MAAM,CAAC,qEAAqE,CAAC,CAAC;QACnF,IAAI,CAAC,MAAM,CAAC;;;KAGX,CAAC,CAAC;QACH,IAAI,CAAC,MAAM,CAAC;;;;KAIX,CAAC,CAAC;QACH,IAAI,CAAC,MAAM,CAAC,qCAAqC,CAAC,CAAC;IACrD,CAAC;CACF"}

package/dist/migrations/20260816T203339_core_retire_core_activation_settings.d.ts

@@ -0,0 +1,39 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Feature 074, FR-010a — delete the six activation Setting rows whose modules
+ * became core.
+ *
+ * `settings`, `sales_channels`, `carts`, `taxes`, `price_lists` and
+ * `audit_logs` each declared `<module>.enabled` and pointed
+ * `activation.settingCode` at it. Phase 1 replaces those controls with
+ * `nonDeactivatable`, which resolves `settingCode` to `null` — and that is
+ * exactly what makes the leftover rows harmful rather than merely stale:
+ * `SettingsAdminService.classify()` marks a row activation-protected only while
+ * `activationControlOwner(code)` still matches its owner, so the moment the
+ * declaration goes the row falls through to `{ editable: true,
+ * activationControl: false }`. A core module is always present, so `editable`
+ * is `true`. The result would be a live boolean on the Settings screen,
+ * labelled as the module's enablement, that changes nothing — the
+ * present-but-ignored shape Principle XVII prohibits, and strictly worse than
+ * the locked control it replaced.
+ *
+ * Dropping the manifest declaration does not remove the row.
+ * `kernel/settings/manifest-reconciler.ts` detects rows a module no longer
+ * declares and reports them as `orphanSettings` **for warning purposes only**,
+ * deliberately, so a boot process never destroys an operator's stored values.
+ * Every existing database therefore keeps all six rows forever unless a
+ * migration removes them, which is what this one does.
+ *
+ * It is filed under `core` rather than as six per-module migrations because the
+ * `settings` table is kernel-owned (see `*_core_settings_*.ts` in this
+ * directory) and a module migration must not write another owner's table.
+ *
+ * No schema change. `setting_values` and `setting_sales_channels` both
+ * reference `settings (id)` with `on delete cascade`, so the per-channel
+ * overrides and channel scopes of these rows go with them.
+ */
+export declare class Migration20260816T203339CoreRetireCoreActivationSettings extends Migration {
+    up(): Promise<void>;
+    down(): Promise<void>;
+}
+//# sourceMappingURL=20260816T203339_core_retire_core_activation_settings.d.ts.map

package/dist/migrations/20260816T203339_core_retire_core_activation_settings.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260816T203339_core_retire_core_activation_settings.d.ts","sourceRoot":"","sources":["../../src/migrations/20260816T203339_core_retire_core_activation_settings.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,qBAAa,wDAAyD,SAAQ,SAAS;IACtE,EAAE,IAAI,OAAO,CAAC,IAAI,CAAC;IAcnB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;CASrC"}

package/dist/migrations/20260816T203339_core_retire_core_activation_settings.js

@@ -0,0 +1,59 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Feature 074, FR-010a — delete the six activation Setting rows whose modules
+ * became core.
+ *
+ * `settings`, `sales_channels`, `carts`, `taxes`, `price_lists` and
+ * `audit_logs` each declared `<module>.enabled` and pointed
+ * `activation.settingCode` at it. Phase 1 replaces those controls with
+ * `nonDeactivatable`, which resolves `settingCode` to `null` — and that is
+ * exactly what makes the leftover rows harmful rather than merely stale:
+ * `SettingsAdminService.classify()` marks a row activation-protected only while
+ * `activationControlOwner(code)` still matches its owner, so the moment the
+ * declaration goes the row falls through to `{ editable: true,
+ * activationControl: false }`. A core module is always present, so `editable`
+ * is `true`. The result would be a live boolean on the Settings screen,
+ * labelled as the module's enablement, that changes nothing — the
+ * present-but-ignored shape Principle XVII prohibits, and strictly worse than
+ * the locked control it replaced.
+ *
+ * Dropping the manifest declaration does not remove the row.
+ * `kernel/settings/manifest-reconciler.ts` detects rows a module no longer
+ * declares and reports them as `orphanSettings` **for warning purposes only**,
+ * deliberately, so a boot process never destroys an operator's stored values.
+ * Every existing database therefore keeps all six rows forever unless a
+ * migration removes them, which is what this one does.
+ *
+ * It is filed under `core` rather than as six per-module migrations because the
+ * `settings` table is kernel-owned (see `*_core_settings_*.ts` in this
+ * directory) and a module migration must not write another owner's table.
+ *
+ * No schema change. `setting_values` and `setting_sales_channels` both
+ * reference `settings (id)` with `on delete cascade`, so the per-channel
+ * overrides and channel scopes of these rows go with them.
+ */
+export class Migration20260816T203339CoreRetireCoreActivationSettings extends Migration {
+    async up() {
+        this.addSql(`
+      delete from "settings"
+      where "code" in (
+        'settings.enabled',
+        'sales_channels.enabled',
+        'carts.enabled',
+        'taxes.enabled',
+        'price_lists.enabled',
+        'audit_logs.enabled'
+      );
+    `);
+    }
+    async down() {
+        // Deliberately empty, and it is not an oversight. The rows are not schema:
+        // the boot reconciler creates a declared Setting from its manifest, so the
+        // way back is to restore the six `activation: { settingCode, default }`
+        // declarations and let the reconciler re-create the rows on the next start.
+        // Re-inserting them here would need a group id, an owner and a default that
+        // this migration would have to invent, and would produce rows no manifest
+        // declares — the orphan state the `up` exists to clear.
+    }
+}
+//# sourceMappingURL=20260816T203339_core_retire_core_activation_settings.js.map

package/dist/migrations/20260816T203339_core_retire_core_activation_settings.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260816T203339_core_retire_core_activation_settings.js","sourceRoot":"","sources":["../../src/migrations/20260816T203339_core_retire_core_activation_settings.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,MAAM,OAAO,wDAAyD,SAAQ,SAAS;IAC5E,KAAK,CAAC,EAAE;QACf,IAAI,CAAC,MAAM,CAAC;;;;;;;;;;KAUX,CAAC,CAAC;IACL,CAAC;IAEQ,KAAK,CAAC,IAAI;QACjB,2EAA2E;QAC3E,2EAA2E;QAC3E,wEAAwE;QACxE,4EAA4E;QAC5E,4EAA4E;QAC5E,0EAA0E;QAC1E,wDAAwD;IAC1D,CAAC;CACF"}

package/dist/migrations/20260919T101500_core_module_registrations_boot_converged.d.ts

@@ -0,0 +1,34 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * `module_registrations.boot_converged_at` — the marker that says a row was
+ * written by boot convergence and no install has run.
+ *
+ * ## What it closes
+ *
+ * `reconcileExistingModules` inserts `state='installed'` for every shipped
+ * manifest with no row, from `composeApp`, and runs no install hook. `install`
+ * then short-circuited on `state === 'installed'` and answered
+ * `already-installed`, so a database whose first action after the migrations was
+ * a boot could never run any `installHook`, and nothing said so. This column is
+ * the one datum that tells the two kinds of `installed` row apart.
+ *
+ * ## Purely additive, and the absence of a backfill is provable
+ *
+ * The column is nullable and every existing row keeps `null`, which reads as
+ * *"an install produced this"*. That is correct for all of them: until feature
+ * 134's W7 the tree had **no `installHook` at all** — `custom_fields`'
+ * `uninstallHook` was the only lifecycle hook in it — so no historical
+ * `installed` row can have skipped one. A blanket backfill would assert the
+ * opposite of the truth for every row a real `module:install` wrote.
+ *
+ * The four-state FSM is untouched: this says nothing about `state` and adds no
+ * constraint to it. Filed under `core` like every other migration in this
+ * package — the kernel owns the table, and a hard uninstall reverts by registry
+ * `moduleId`, so filing it under a module would make that module's
+ * `--hard` uninstall drop kernel schema.
+ */
+export declare class Migration20260919T101500CoreModuleRegistrationsBootConverged extends Migration {
+    up(): Promise<void>;
+    down(): Promise<void>;
+}
+//# sourceMappingURL=20260919T101500_core_module_registrations_boot_converged.d.ts.map

package/dist/migrations/20260919T101500_core_module_registrations_boot_converged.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260919T101500_core_module_registrations_boot_converged.d.ts","sourceRoot":"","sources":["../../src/migrations/20260919T101500_core_module_registrations_boot_converged.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,qBAAa,4DAA6D,SAAQ,SAAS;IAC1E,EAAE,IAAI,OAAO,CAAC,IAAI,CAAC;IAMnB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;CAGrC"}

package/dist/migrations/20260919T101500_core_module_registrations_boot_converged.js

@@ -0,0 +1,38 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * `module_registrations.boot_converged_at` — the marker that says a row was
+ * written by boot convergence and no install has run.
+ *
+ * ## What it closes
+ *
+ * `reconcileExistingModules` inserts `state='installed'` for every shipped
+ * manifest with no row, from `composeApp`, and runs no install hook. `install`
+ * then short-circuited on `state === 'installed'` and answered
+ * `already-installed`, so a database whose first action after the migrations was
+ * a boot could never run any `installHook`, and nothing said so. This column is
+ * the one datum that tells the two kinds of `installed` row apart.
+ *
+ * ## Purely additive, and the absence of a backfill is provable
+ *
+ * The column is nullable and every existing row keeps `null`, which reads as
+ * *"an install produced this"*. That is correct for all of them: until feature
+ * 134's W7 the tree had **no `installHook` at all** — `custom_fields`'
+ * `uninstallHook` was the only lifecycle hook in it — so no historical
+ * `installed` row can have skipped one. A blanket backfill would assert the
+ * opposite of the truth for every row a real `module:install` wrote.
+ *
+ * The four-state FSM is untouched: this says nothing about `state` and adds no
+ * constraint to it. Filed under `core` like every other migration in this
+ * package — the kernel owns the table, and a hard uninstall reverts by registry
+ * `moduleId`, so filing it under a module would make that module's
+ * `--hard` uninstall drop kernel schema.
+ */
+export class Migration20260919T101500CoreModuleRegistrationsBootConverged extends Migration {
+    async up() {
+        this.addSql(`alter table "module_registrations" add column "boot_converged_at" timestamptz null;`);
+    }
+    async down() {
+        this.addSql(`alter table "module_registrations" drop column "boot_converged_at";`);
+    }
+}
+//# sourceMappingURL=20260919T101500_core_module_registrations_boot_converged.js.map

package/dist/migrations/20260919T101500_core_module_registrations_boot_converged.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260919T101500_core_module_registrations_boot_converged.js","sourceRoot":"","sources":["../../src/migrations/20260919T101500_core_module_registrations_boot_converged.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,MAAM,OAAO,4DAA6D,SAAQ,SAAS;IAChF,KAAK,CAAC,EAAE;QACf,IAAI,CAAC,MAAM,CACT,qFAAqF,CACtF,CAAC;IACJ,CAAC;IAEQ,KAAK,CAAC,IAAI;QACjB,IAAI,CAAC,MAAM,CAAC,qEAAqE,CAAC,CAAC;IACrF,CAAC;CACF"}

package/dist/migrations/baseline-migrations.generated.d.ts

@@ -0,0 +1,2 @@
+export declare const BASELINE_MIGRATIONS: readonly string[];
+//# sourceMappingURL=baseline-migrations.generated.d.ts.map

package/dist/migrations/baseline-migrations.generated.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"baseline-migrations.generated.d.ts","sourceRoot":"","sources":["../../src/migrations/baseline-migrations.generated.ts"],"names":[],"mappings":"AAsBA,eAAO,MAAM,mBAAmB,EAAE,SAAS,MAAM,EAiHhD,CAAC"}

package/dist/migrations/baseline-migrations.generated.js

@@ -0,0 +1,136 @@
+// AUTO-GENERATED by scripts/generate-composer.ts — DO NOT EDIT.
+// Run `pnpm --filter backend run composer:generate` (or rebuild the backend)
+// to refresh. Editing this file by hand is undone by the next build, and
+// `pnpm --filter backend run overlay:check` fails on the drift.
+//
+// The frozen historical prefix, by identity — every migration whose position is
+// history rather than a consequence of the manifest graph, in the order history
+// applied it.
+//
+// Normative: specs/110-instance-repository/contracts/instance-migration-order.md.
+// The reason it is the platform's, and the reason membership is a name rather
+// than an origin, are in ./index.ts. The reason it may not be recomputed from
+// the manifest graph is BASELINE_THROUGH's own doc block: that block predates
+// feature 065, its modules' `dependencies` arrays contradict the order it was
+// applied in in 37 places, and re-deriving it produces an order a fresh database
+// cannot apply.
+//
+// **Closed. It never grows or drains** (R1.4): it holds the immutable platform
+// history through BASELINE_THROUGH (20260801T000000). A deployment projects
+// this order onto the owners it installed; extraction cannot delete an identity
+// an existing database already recorded.
+export const BASELINE_MIGRATIONS = [
+    'Migration20260424T165847CoreFoundationInit',
+    'Migration20260424T190112QuoteRequestsInit',
+    'Migration20260424T205317OrganizationsInit',
+    'Migration20260425T050720CoreCommerceInit',
+    'Migration20260425T051700OrganizationsInvitationsInit',
+    'Migration20260425T053028AdminUsersInit',
+    'Migration20260425T055041CustomerAccountsPasswordResetTokens',
+    'Migration20260425T063333CreditLimitsInit',
+    'Migration20260425T091359WebhooksUs7Init',
+    'Migration20260425T143139AnalyticsInit',
+    'Migration20260425T154404SeoInit',
+    'Migration20260425T161557LanguagesCurrenciesInit',
+    'Migration20260425T162418CmsPagesInit',
+    'Migration20260426T075235PriceListsPricingInit',
+    'Migration20260426T081516TaxesPromotionsInit',
+    'Migration20260426T135443ShoppingListsInit',
+    'Migration20260429T064146CatalogAttributeSetsInit',
+    'Migration20260429T070004CatalogProductAttributeExtensions',
+    'Migration20260429T102322CatalogProductTypeAndVirtualFields',
+    'Migration20260429T111839CatalogGalleryItemsAndLabels',
+    'Migration20260429T112543CatalogProductAttachments',
+    'Migration20260429T123726CatalogProductLinks',
+    'Migration20260429T130803CatalogGroupedAndBundle',
+    'Migration20260430T101450CoreSettingsInit',
+    'Migration20260430T170044CoreSalesChannelsPromote',
+    'Migration20260501T123145SearchPhraseRecordsInit',
+    'Migration20260501T185834ComparisonsInit',
+    'Migration20260501T185835CatalogProductAttributeIsComparable',
+    'Migration20260503T141344QuoteRequestsWorkflow',
+    'Migration20260503T182812InventoryWorkflow',
+    'Migration20260504T125655PriceListsEngine',
+    'Migration20260505T060113CatalogAttributeOptionsAndFlags',
+    'Migration20260505T074605PromotionsCriteria',
+    'Migration20260505T102206AssetsLibraryInit',
+    'Migration20260505T130214CmsInit',
+    'Migration20260505T193836MegamenuInit',
+    'Migration20260506T081055BlogInit',
+    'Migration20260506T112634DictionariesDictionaryInit',
+    'Migration20260506T200657CoreModuleLifecycleInit',
+    'Migration20260507T091405I18nAdminI18nInit',
+    'Migration20260507T142354AdminActionsInit',
+    'Migration20260514T111329CoreSettingsGlobalValue',
+    'Migration20260515T082629CatalogAttributeMassEditable',
+    'Migration20260526T124736CatalogProductStatusInactive',
+    'Migration20260611T140346CatalogProductValueOverridesInit',
+    'Migration20260611T140347InventoryWarehouseDefaultLowStockThreshold',
+    'Migration20260611T140348InventoryPerWarehouseLowStockThresholds',
+    'Migration20260611T140349OrganizationsConsolidation',
+    'Migration20260611T140350AdminNotificationsInit',
+    'Migration20260611T140351CustomerAccountsOrganizationOptional',
+    'Migration20260611T140352CartsConsolidation',
+    'Migration20260611T140353PaymentMethodsAdapter',
+    'Migration20260611T140354DeliveryMethodsShippingMethodsAdapterAndShipments',
+    'Migration20260611T140355OrdersBusinessId',
+    'Migration20260611T140356OrdersStatusModel',
+    'Migration20260611T140357OrdersOrderCommentsAndSavedViews',
+    'Migration20260611T140358OrganizationsOrgOrderConfirmationEmails',
+    'Migration20260611T140359QuickOrderDefaultPreferences',
+    'Migration20260611T140400CatalogAttributeQuickSearchable',
+    'Migration20260611T140401OrdersOrderStatusDefaultName',
+    'Migration20260611T140402OrganizationsOrgFulfilmentStrategy',
+    'Migration20260611T140403CustomerAccountsLifecycle',
+    'Migration20260611T140404CustomersCustomerAddressesInit',
+    'Migration20260611T140405OrdersOrderStatusColor',
+    'Migration20260611T140406OrdersOrderSavedViewColumns',
+    'Migration20260611T140407CatalogBulkOperations',
+    'Migration20260611T140408CatalogBulkOperationLogs',
+    'Migration20260611T140409MfaInit',
+    'Migration20260611T140410PromptActionsInit',
+    'Migration20260611T140411CoreSettingsSecretValueType',
+    'Migration20260611T140412CatalogProductPackagingUnits',
+    'Migration20260611T140413CartsCartItemPackaging',
+    'Migration20260611T140414OrdersOrderItemPackaging',
+    'Migration20260611T140415QuoteRequestsQrItemPackaging',
+    'Migration20260611T140416DeliveryMethodsFixInPersonPickupAdapter',
+    'Migration20260611T140417QuoteRequestsBusinessId',
+    'Migration20260611T140418ShoppingListsDefault',
+    'Migration20260611T140419CoreSettingsEnumOptions',
+    'Migration20260617T095510QuoteRequestsBackfillAdminCreatedAwaiting',
+    'Migration20260618T100727PromotionsEngine',
+    'Migration20260618T130459OrdersOrderAppliedPromotions',
+    'Migration20260625T144227ReturnsInit',
+    'Migration20260625T144228PwaInit',
+    'Migration20260629T090100CoreSettingsHiddenFlag',
+    'Migration20260629T113442TransactionalEmailsInit',
+    'Migration20260629T125121InvoicesModule',
+    'Migration20260629T200954NewsletterInit',
+    'Migration20260708T101135StripeInit',
+    'Migration20260715T103358StripePaymentRefundedAmount',
+    'Migration20260715T171116GoogleAnalyticsInit',
+    'Migration20260717T134752CoreTenantScopeIndexes',
+    'Migration20260717T151403OrganizationsPersonalOrganizations',
+    'Migration20260718T060659CatalogBulkOperationRevertState',
+    'Migration20260718T200338CustomFieldsInit',
+    'Migration20260718T200339OrdersOrderCustomFieldValues',
+    'Migration20260718T200340OrganizationsOrganizationCustomFieldValues',
+    'Migration20260718T200341CustomerAccountsCustomerAccountCustomFieldValues',
+    'Migration20260718T200342QuoteRequestsQuoteRequestCustomFieldValues',
+    'Migration20260718T200343CatalogCategoryCustomFieldValues',
+    'Migration20260720T044254OrganizationsOrgHierarchy',
+    'Migration20260720T044255CustomerAccountsCustomerSubtreeRollup',
+    'Migration20260721T011509CredentialsInit',
+    'Migration20260721T011510CoreSettingsCredentialRefValueType',
+    'Migration20260722T224358KsefInit',
+    'Migration20260723T230401CatalogAttributesOnCustomFields',
+    'Migration20260724T173916ApiKeysDistributorBinding',
+    'Migration20260724T193611OrdersOrderPlacementIntents',
+    'Migration20260724T203140WebhooksOrgFilter',
+    'Migration20260727T200555WebhooksDropExternalIntegrations',
+    'Migration20260727T233211LinkedinAdsInit',
+    'Migration20260728T002715MetaAdsInit',
+    'Migration20260729T132507TpayInit',
+];
+//# sourceMappingURL=baseline-migrations.generated.js.map

package/dist/migrations/baseline-migrations.generated.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"baseline-migrations.generated.js","sourceRoot":"","sources":["../../src/migrations/baseline-migrations.generated.ts"],"names":[],"mappings":"AAAA,gEAAgE;AAChE,6EAA6E;AAC7E,yEAAyE;AACzE,gEAAgE;AAChE,EAAE;AACF,gFAAgF;AAChF,gFAAgF;AAChF,cAAc;AACd,EAAE;AACF,kFAAkF;AAClF,8EAA8E;AAC9E,8EAA8E;AAC9E,8EAA8E;AAC9E,8EAA8E;AAC9E,iFAAiF;AACjF,gBAAgB;AAChB,EAAE;AACF,+EAA+E;AAC/E,4EAA4E;AAC5E,gFAAgF;AAChF,yCAAyC;AAEzC,MAAM,CAAC,MAAM,mBAAmB,GAAsB;IACpD,4CAA4C;IAC5C,2CAA2C;IAC3C,2CAA2C;IAC3C,0CAA0C;IAC1C,sDAAsD;IACtD,wCAAwC;IACxC,6DAA6D;IAC7D,0CAA0C;IAC1C,yCAAyC;IACzC,uCAAuC;IACvC,iCAAiC;IACjC,iDAAiD;IACjD,sCAAsC;IACtC,+CAA+C;IAC/C,6CAA6C;IAC7C,2CAA2C;IAC3C,kDAAkD;IAClD,2DAA2D;IAC3D,4DAA4D;IAC5D,sDAAsD;IACtD,mDAAmD;IACnD,6CAA6C;IAC7C,iDAAiD;IACjD,0CAA0C;IAC1C,kDAAkD;IAClD,iDAAiD;IACjD,yCAAyC;IACzC,6DAA6D;IAC7D,+CAA+C;IAC/C,2CAA2C;IAC3C,0CAA0C;IAC1C,yDAAyD;IACzD,4CAA4C;IAC5C,2CAA2C;IAC3C,iCAAiC;IACjC,sCAAsC;IACtC,kCAAkC;IAClC,oDAAoD;IACpD,iDAAiD;IACjD,2CAA2C;IAC3C,0CAA0C;IAC1C,iDAAiD;IACjD,sDAAsD;IACtD,sDAAsD;IACtD,0DAA0D;IAC1D,oEAAoE;IACpE,iEAAiE;IACjE,oDAAoD;IACpD,gDAAgD;IAChD,8DAA8D;IAC9D,4CAA4C;IAC5C,+CAA+C;IAC/C,2EAA2E;IAC3E,0CAA0C;IAC1C,2CAA2C;IAC3C,0DAA0D;IAC1D,iEAAiE;IACjE,sDAAsD;IACtD,yDAAyD;IACzD,sDAAsD;IACtD,4DAA4D;IAC5D,mDAAmD;IACnD,wDAAwD;IACxD,gDAAgD;IAChD,qDAAqD;IACrD,+CAA+C;IAC/C,kDAAkD;IAClD,iCAAiC;IACjC,2CAA2C;IAC3C,qDAAqD;IACrD,sDAAsD;IACtD,gDAAgD;IAChD,kDAAkD;IAClD,sDAAsD;IACtD,iEAAiE;IACjE,iDAAiD;IACjD,8CAA8C;IAC9C,iDAAiD;IACjD,mEAAmE;IACnE,0CAA0C;IAC1C,sDAAsD;IACtD,qCAAqC;IACrC,iCAAiC;IACjC,gDAAgD;IAChD,iDAAiD;IACjD,wCAAwC;IACxC,wCAAwC;IACxC,oCAAoC;IACpC,qDAAqD;IACrD,6CAA6C;IAC7C,gDAAgD;IAChD,4DAA4D;IAC5D,yDAAyD;IACzD,0CAA0C;IAC1C,sDAAsD;IACtD,oEAAoE;IACpE,0EAA0E;IAC1E,oEAAoE;IACpE,0DAA0D;IAC1D,mDAAmD;IACnD,+DAA+D;IAC/D,yCAAyC;IACzC,4DAA4D;IAC5D,kCAAkC;IAClC,yDAAyD;IACzD,mDAAmD;IACnD,qDAAqD;IACrD,2CAA2C;IAC3C,0DAA0D;IAC1D,yCAAyC;IACzC,qCAAqC;IACrC,kCAAkC;CACnC,CAAC"}

package/dist/migrations/index.d.ts

@@ -0,0 +1,62 @@
+/**
+ * `./migrations` — the platform's seventh subpath, and the platform's own claim
+ * about its schema history.
+ *
+ * ## What is on it
+ *
+ * {@link BASELINE_MIGRATIONS}: the frozen historical prefix, as an ordered list
+ * of migration class names.
+ * `specs/110-instance-repository/contracts/instance-migration-order.md` is
+ * normative and §1 is where every alternative to it is refused with the reason.
+ *
+ * The short version. The order a migration corpus is applied in is a frozen
+ * historical prefix — the pre-065 block, whose order is history and which the
+ * manifest graph contradicts in 37 places — followed by the modules, module by
+ * module, in a topological order of that graph. Membership of the prefix used
+ * to be `origin === 'core' && timestamp <= BASELINE_THROUGH`: *"came out of
+ * this repository's build"*. That is a different question from *"is one of the
+ * migrations whose order is history"*, and the two coincide exactly while every
+ * module is compiled into the application. Measured over the real registry the
+ * moment they come apart: the prefix falls from **112** entries to **11**, 181
+ * of 182 positions move, and six migrations — three of them `core`'s — land
+ * before the migration that creates a table they touch. An instance installing
+ * the same modules could not migrate a fresh database at all, failing at
+ * `Migration20260505T102206AssetsLibraryInit` with
+ * `relation "cms_pages" does not exist`.
+ *
+ * So membership is by **identity**, and the identities are here.
+ *
+ * ## Why the platform carries it
+ *
+ * R1.5. It is data about *this platform's* history, a client receives it by
+ * installing the platform, and a client receives a correction to it by
+ * `pnpm update`. The alternative — an instance carrying the order — makes a
+ * fact about our history the client's to hold, in a tree we cannot grep.
+ *
+ * ## Why no module may name it
+ *
+ * It is declared by the `exports` map and carried by no published barrel, which
+ * is D-160.14's third state: `node` and `tsc` resolve it, and
+ * `check:platform-surface` gives a module reaching it a finding of its own
+ * (`host-internal-subpath`). The reader is the host's ORM configuration, which
+ * is the one program that composes an execution order. A module's own
+ * `./migrations` subpath is the other side of the same conversation and is
+ * unaffected: it publishes that module's classes, and this publishes the order
+ * the platform applies them in.
+ */
+export { BASELINE_MIGRATIONS } from './baseline-migrations.generated.js';
+export { BASELINE_MIGRATION_INVENTORY, type BaselineMigrationIdentity, } from '../db/baseline-migration-inventory.js';
+export { Migration20260424T165847CoreFoundationInit } from './20260424T165847_core_foundation_init.js';
+export { Migration20260425T050720CoreCommerceInit } from './20260425T050720_core_commerce_init.js';
+export { Migration20260430T101450CoreSettingsInit } from './20260430T101450_core_settings_init.js';
+export { Migration20260430T170044CoreSalesChannelsPromote } from './20260430T170044_core_sales_channels_promote.js';
+export { Migration20260506T200657CoreModuleLifecycleInit } from './20260506T200657_core_module_lifecycle_init.js';
+export { Migration20260514T111329CoreSettingsGlobalValue } from './20260514T111329_core_settings_global_value.js';
+export { Migration20260611T140411CoreSettingsSecretValueType } from './20260611T140411_core_settings_secret_value_type.js';
+export { Migration20260611T140419CoreSettingsEnumOptions } from './20260611T140419_core_settings_enum_options.js';
+export { Migration20260629T090100CoreSettingsHiddenFlag } from './20260629T090100_core_settings_hidden_flag.js';
+export { Migration20260717T134752CoreTenantScopeIndexes } from './20260717T134752_core_tenant_scope_indexes.js';
+export { Migration20260721T011510CoreSettingsCredentialRefValueType } from './20260721T011510_core_settings_credential_ref_value_type.js';
+export { Migration20260816T203339CoreRetireCoreActivationSettings } from './20260816T203339_core_retire_core_activation_settings.js';
+export { Migration20260919T101500CoreModuleRegistrationsBootConverged } from './20260919T101500_core_module_registrations_boot_converged.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/migrations/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/migrations/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6CG;AACH,OAAO,EAAE,mBAAmB,EAAE,MAAM,oCAAoC,CAAC;AACzE,OAAO,EACL,4BAA4B,EAC5B,KAAK,yBAAyB,GAC/B,MAAM,uCAAuC,CAAC;AAe/C,OAAO,EAAE,0CAA0C,EAAE,MAAM,2CAA2C,CAAC;AACvG,OAAO,EAAE,wCAAwC,EAAE,MAAM,yCAAyC,CAAC;AACnG,OAAO,EAAE,wCAAwC,EAAE,MAAM,yCAAyC,CAAC;AACnG,OAAO,EAAE,gDAAgD,EAAE,MAAM,kDAAkD,CAAC;AACpH,OAAO,EAAE,+CAA+C,EAAE,MAAM,iDAAiD,CAAC;AAClH,OAAO,EAAE,+CAA+C,EAAE,MAAM,iDAAiD,CAAC;AAClH,OAAO,EAAE,mDAAmD,EAAE,MAAM,sDAAsD,CAAC;AAC3H,OAAO,EAAE,+CAA+C,EAAE,MAAM,iDAAiD,CAAC;AAClH,OAAO,EAAE,8CAA8C,EAAE,MAAM,gDAAgD,CAAC;AAChH,OAAO,EAAE,8CAA8C,EAAE,MAAM,gDAAgD,CAAC;AAChH,OAAO,EAAE,0DAA0D,EAAE,MAAM,8DAA8D,CAAC;AAC1I,OAAO,EAAE,wDAAwD,EAAE,MAAM,2DAA2D,CAAC;AACrI,OAAO,EAAE,4DAA4D,EAAE,MAAM,+DAA+D,CAAC"}

package/dist/migrations/index.js

@@ -0,0 +1,75 @@
+/**
+ * `./migrations` — the platform's seventh subpath, and the platform's own claim
+ * about its schema history.
+ *
+ * ## What is on it
+ *
+ * {@link BASELINE_MIGRATIONS}: the frozen historical prefix, as an ordered list
+ * of migration class names.
+ * `specs/110-instance-repository/contracts/instance-migration-order.md` is
+ * normative and §1 is where every alternative to it is refused with the reason.
+ *
+ * The short version. The order a migration corpus is applied in is a frozen
+ * historical prefix — the pre-065 block, whose order is history and which the
+ * manifest graph contradicts in 37 places — followed by the modules, module by
+ * module, in a topological order of that graph. Membership of the prefix used
+ * to be `origin === 'core' && timestamp <= BASELINE_THROUGH`: *"came out of
+ * this repository's build"*. That is a different question from *"is one of the
+ * migrations whose order is history"*, and the two coincide exactly while every
+ * module is compiled into the application. Measured over the real registry the
+ * moment they come apart: the prefix falls from **112** entries to **11**, 181
+ * of 182 positions move, and six migrations — three of them `core`'s — land
+ * before the migration that creates a table they touch. An instance installing
+ * the same modules could not migrate a fresh database at all, failing at
+ * `Migration20260505T102206AssetsLibraryInit` with
+ * `relation "cms_pages" does not exist`.
+ *
+ * So membership is by **identity**, and the identities are here.
+ *
+ * ## Why the platform carries it
+ *
+ * R1.5. It is data about *this platform's* history, a client receives it by
+ * installing the platform, and a client receives a correction to it by
+ * `pnpm update`. The alternative — an instance carrying the order — makes a
+ * fact about our history the client's to hold, in a tree we cannot grep.
+ *
+ * ## Why no module may name it
+ *
+ * It is declared by the `exports` map and carried by no published barrel, which
+ * is D-160.14's third state: `node` and `tsc` resolve it, and
+ * `check:platform-surface` gives a module reaching it a finding of its own
+ * (`host-internal-subpath`). The reader is the host's ORM configuration, which
+ * is the one program that composes an execution order. A module's own
+ * `./migrations` subpath is the other side of the same conversation and is
+ * unaffected: it publishes that module's classes, and this publishes the order
+ * the platform applies them in.
+ */
+export { BASELINE_MIGRATIONS } from './baseline-migrations.generated.js';
+export { BASELINE_MIGRATION_INVENTORY, } from '../db/baseline-migration-inventory.js';
+// --- the platform's own thirteen migrations -------------------------------
+//
+// Named exports and no `migrations` array, and the asymmetry with a module
+// package's `./migrations` barrel is deliberate. That array exists because
+// `packages/package-runtime.ts` reads it out of an **installed** package's
+// export and refuses the package when it is absent; the platform is not a
+// module package and is discovered by nothing, so an array here would be a
+// claim nothing reads. What is read is each class **by name**, by
+// `backend/src/db/migrations-registry.generated.ts`, which the generator emits
+// against this specifier — and a migration class name is contract in a way an
+// entity class name is not: `mikro_orm_migrations` persists it, so it is a
+// string every already-migrated database holds. A class that is in neither this
+// barrel nor the registry is a migration that does not run.
+export { Migration20260424T165847CoreFoundationInit } from './20260424T165847_core_foundation_init.js';
+export { Migration20260425T050720CoreCommerceInit } from './20260425T050720_core_commerce_init.js';
+export { Migration20260430T101450CoreSettingsInit } from './20260430T101450_core_settings_init.js';
+export { Migration20260430T170044CoreSalesChannelsPromote } from './20260430T170044_core_sales_channels_promote.js';
+export { Migration20260506T200657CoreModuleLifecycleInit } from './20260506T200657_core_module_lifecycle_init.js';
+export { Migration20260514T111329CoreSettingsGlobalValue } from './20260514T111329_core_settings_global_value.js';
+export { Migration20260611T140411CoreSettingsSecretValueType } from './20260611T140411_core_settings_secret_value_type.js';
+export { Migration20260611T140419CoreSettingsEnumOptions } from './20260611T140419_core_settings_enum_options.js';
+export { Migration20260629T090100CoreSettingsHiddenFlag } from './20260629T090100_core_settings_hidden_flag.js';
+export { Migration20260717T134752CoreTenantScopeIndexes } from './20260717T134752_core_tenant_scope_indexes.js';
+export { Migration20260721T011510CoreSettingsCredentialRefValueType } from './20260721T011510_core_settings_credential_ref_value_type.js';
+export { Migration20260816T203339CoreRetireCoreActivationSettings } from './20260816T203339_core_retire_core_activation_settings.js';
+export { Migration20260919T101500CoreModuleRegistrationsBootConverged } from './20260919T101500_core_module_registrations_boot_converged.js';
+//# sourceMappingURL=index.js.map

package/dist/migrations/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/migrations/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6CG;AACH,OAAO,EAAE,mBAAmB,EAAE,MAAM,oCAAoC,CAAC;AACzE,OAAO,EACL,4BAA4B,GAE7B,MAAM,uCAAuC,CAAC;AAE/C,6EAA6E;AAC7E,EAAE;AACF,2EAA2E;AAC3E,2EAA2E;AAC3E,2EAA2E;AAC3E,0EAA0E;AAC1E,2EAA2E;AAC3E,kEAAkE;AAClE,+EAA+E;AAC/E,8EAA8E;AAC9E,2EAA2E;AAC3E,gFAAgF;AAChF,4DAA4D;AAC5D,OAAO,EAAE,0CAA0C,EAAE,MAAM,2CAA2C,CAAC;AACvG,OAAO,EAAE,wCAAwC,EAAE,MAAM,yCAAyC,CAAC;AACnG,OAAO,EAAE,wCAAwC,EAAE,MAAM,yCAAyC,CAAC;AACnG,OAAO,EAAE,gDAAgD,EAAE,MAAM,kDAAkD,CAAC;AACpH,OAAO,EAAE,+CAA+C,EAAE,MAAM,iDAAiD,CAAC;AAClH,OAAO,EAAE,+CAA+C,EAAE,MAAM,iDAAiD,CAAC;AAClH,OAAO,EAAE,mDAAmD,EAAE,MAAM,sDAAsD,CAAC;AAC3H,OAAO,EAAE,+CAA+C,EAAE,MAAM,iDAAiD,CAAC;AAClH,OAAO,EAAE,8CAA8C,EAAE,MAAM,gDAAgD,CAAC;AAChH,OAAO,EAAE,8CAA8C,EAAE,MAAM,gDAAgD,CAAC;AAChH,OAAO,EAAE,0DAA0D,EAAE,MAAM,8DAA8D,CAAC;AAC1I,OAAO,EAAE,wDAAwD,EAAE,MAAM,2DAA2D,CAAC;AACrI,OAAO,EAAE,4DAA4D,EAAE,MAAM,+DAA+D,CAAC"}

package/dist/overlay/deployment-roots.d.ts

@@ -0,0 +1,37 @@
+/**
+ * The active deployment name, or `null` for a bare-core build.
+ *
+ * Read from `DEPLOYMENT`; blank/whitespace is treated as unset. It names no
+ * path, which is why it moved whole: the environment is the same environment in
+ * every tree.
+ *
+ * `env` is an argument rather than an ambient read because one process resolves
+ * both answers — a suite proves a module present with the deployment selected
+ * and absent without it, in one run.
+ */
+export declare function selectedDeployment(env?: NodeJS.ProcessEnv): string | null;
+/**
+ * Absolute path to a deployment's overlay modules root (whether or not it
+ * exists), under the supplied deployment root.
+ */
+export declare function overlayModulesRootFor(deploymentRoot: string, deployment: string): string;
+/**
+ * Every deployment under the supplied root, sorted — one directory under
+ * `<deploymentRoot>/apps/`.
+ *
+ * `DEPLOYMENT` selects which one a *build* composes; this is the whole set, and
+ * it exists so the determinism gate can verify each deployment's committed
+ * artefacts without being run once per deployment (issue #120). An artefact only
+ * a run nobody makes would check is an artefact nothing checks.
+ *
+ * A root with no `apps/` is the empty list rather than a throw: a tree that
+ * ships no deployment is bare core, which is a supported state and not an error.
+ */
+export declare function deploymentsOnDisk(deploymentRoot: string): readonly string[];
+/**
+ * The active overlay modules root, or `null` when there is no deployment or the
+ * deployment ships no overlay directory. A non-directory path resolves to null
+ * (core-only) rather than raising — a missing overlay is not an error.
+ */
+export declare function activeOverlayModulesRoot(deploymentRoot: string, env?: NodeJS.ProcessEnv): string | null;
+//# sourceMappingURL=deployment-roots.d.ts.map

package/dist/overlay/deployment-roots.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"deployment-roots.d.ts","sourceRoot":"","sources":["../../src/overlay/deployment-roots.ts"],"names":[],"mappings":"AA0BA;;;;;;;;;;GAUG;AACH,wBAAgB,kBAAkB,CAAC,GAAG,GAAE,MAAM,CAAC,UAAwB,GAAG,MAAM,GAAG,IAAI,CAKtF;AAED;;;GAGG;AACH,wBAAgB,qBAAqB,CAAC,cAAc,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,GAAG,MAAM,CAExF;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,iBAAiB,CAAC,cAAc,EAAE,MAAM,GAAG,SAAS,MAAM,EAAE,CAO3E;AAED;;;;GAIG;AACH,wBAAgB,wBAAwB,CACtC,cAAc,EAAE,MAAM,EACtB,GAAG,GAAE,MAAM,CAAC,UAAwB,GACnC,MAAM,GAAG,IAAI,CAUf"}