@endora-commerce/platform 0.100.0

package/dist/migrations/20260430T170044_core_sales_channels_promote.d.ts

@@ -0,0 +1,67 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Sales Channels module — feature 005 / data-model.md.
+ *
+ * The `sales_channels` table itself was created back in foundation 001;
+ * this migration promotes it from a thin catalog-owned record into the
+ * full Sales-Channel registry the spec describes:
+ *
+ *   - Adds the missing identity columns (`logo_asset_id`, `theme_code`,
+ *     `languages` jsonb, `currencies` jsonb, `active`, `system_default`,
+ *     `version`) and the partial unique index that enforces the
+ *     "exactly-one system default" invariant (FR-002).
+ *   - Backfills the new jsonb arrays from the existing scalar
+ *     `default_language` / `default_currency` columns and copies
+ *     `status='active'` into the new boolean `active` flag.
+ *
+ * It also added a NULLABLE `sales_channel_id` column to `quote_requests`
+ * (FR-006) until `specs/120-migration-closure-bridge-ownership/` Phase 3. That
+ * column, its `ON DELETE RESTRICT` foreign key and its index are now
+ * `Migration20260912T125614QuoteRequestsQuoteRequestChannelAttribution`'s,
+ * under the same rule as the bridges below: the platform declares no
+ * dependencies, so it can never be ordered after a module's table, and
+ * `quote_requests` is not the platform's. The column is still NULLABLE and
+ * T060 (US3) still owns the backfill and the NOT NULL flip.
+ *
+ * It created eight M:N sales-channel bridge tables (FR-009) until
+ * `specs/120-migration-closure-bridge-ownership/` Phase 2. Each one now belongs
+ * to the module that owns its far side, under D-226's ownership rule: a bridge
+ * between an always-present near side and a switchable far side is the far
+ * side's. The class name and every statement below it are unchanged, so a
+ * database that already applied this migration is offered nothing — the storage
+ * keys on the class name and holds no checksum — and the eight far-side
+ * migrations are `create table if not exists` no-ops on it. On a fresh database
+ * they create the same eight tables from the same statements, later in the
+ * order, which is where they have to be for an instance that omits one of those
+ * modules to migrate at all.
+ *
+ * Deferred (intentionally NOT in this migration):
+ *
+ *   - `sales_channel_inventory_locations` — the inventory module does
+ *     not yet have an `inventory_locations` table. The bridge will be
+ *     added in the same migration that introduces that table; until
+ *     then, FR-009's "Inventory" item is unimplemented and is tracked
+ *     by tasks.md T054 / data-model.md § Entities note.
+ *   - The legacy `is_public` and `status` columns are kept as-is for
+ *     one release cycle (R-12) so this migration is fully reversible.
+ *     A later cleanup migration will drop them once every consumer has
+ *     moved to `active`.
+ *   - Inserting / promoting the `Default` row — the boot-time
+ *     reconciler (`default-channel-reconciler.ts`) is the single source
+ *     of truth (R-4).
+ *
+ * The down() reverses every up() step; the legacy columns are not
+ * touched. It no longer drops the eight bridge tables, nor the
+ * `quote_requests` column, because this migration no longer creates either —
+ * each migration that took a statement drops its own.
+ *
+ * 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 `sales_channels` made `modules:uninstall --hard sales_channels` drop
+ * kernel schema.
+ */
+export declare class Migration20260430T170044CoreSalesChannelsPromote extends Migration {
+    up(): Promise<void>;
+    down(): Promise<void>;
+}
+//# sourceMappingURL=20260430T170044_core_sales_channels_promote.d.ts.map

package/dist/migrations/20260430T170044_core_sales_channels_promote.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260430T170044_core_sales_channels_promote.d.ts","sourceRoot":"","sources":["../../src/migrations/20260430T170044_core_sales_channels_promote.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4DG;AACH,qBAAa,gDAAiD,SAAQ,SAAS;IAC9D,EAAE,IAAI,OAAO,CAAC,IAAI,CAAC;IAkDnB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;CAgBrC"}

package/dist/migrations/20260430T170044_core_sales_channels_promote.js

@@ -0,0 +1,101 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Sales Channels module — feature 005 / data-model.md.
+ *
+ * The `sales_channels` table itself was created back in foundation 001;
+ * this migration promotes it from a thin catalog-owned record into the
+ * full Sales-Channel registry the spec describes:
+ *
+ *   - Adds the missing identity columns (`logo_asset_id`, `theme_code`,
+ *     `languages` jsonb, `currencies` jsonb, `active`, `system_default`,
+ *     `version`) and the partial unique index that enforces the
+ *     "exactly-one system default" invariant (FR-002).
+ *   - Backfills the new jsonb arrays from the existing scalar
+ *     `default_language` / `default_currency` columns and copies
+ *     `status='active'` into the new boolean `active` flag.
+ *
+ * It also added a NULLABLE `sales_channel_id` column to `quote_requests`
+ * (FR-006) until `specs/120-migration-closure-bridge-ownership/` Phase 3. That
+ * column, its `ON DELETE RESTRICT` foreign key and its index are now
+ * `Migration20260912T125614QuoteRequestsQuoteRequestChannelAttribution`'s,
+ * under the same rule as the bridges below: the platform declares no
+ * dependencies, so it can never be ordered after a module's table, and
+ * `quote_requests` is not the platform's. The column is still NULLABLE and
+ * T060 (US3) still owns the backfill and the NOT NULL flip.
+ *
+ * It created eight M:N sales-channel bridge tables (FR-009) until
+ * `specs/120-migration-closure-bridge-ownership/` Phase 2. Each one now belongs
+ * to the module that owns its far side, under D-226's ownership rule: a bridge
+ * between an always-present near side and a switchable far side is the far
+ * side's. The class name and every statement below it are unchanged, so a
+ * database that already applied this migration is offered nothing — the storage
+ * keys on the class name and holds no checksum — and the eight far-side
+ * migrations are `create table if not exists` no-ops on it. On a fresh database
+ * they create the same eight tables from the same statements, later in the
+ * order, which is where they have to be for an instance that omits one of those
+ * modules to migrate at all.
+ *
+ * Deferred (intentionally NOT in this migration):
+ *
+ *   - `sales_channel_inventory_locations` — the inventory module does
+ *     not yet have an `inventory_locations` table. The bridge will be
+ *     added in the same migration that introduces that table; until
+ *     then, FR-009's "Inventory" item is unimplemented and is tracked
+ *     by tasks.md T054 / data-model.md § Entities note.
+ *   - The legacy `is_public` and `status` columns are kept as-is for
+ *     one release cycle (R-12) so this migration is fully reversible.
+ *     A later cleanup migration will drop them once every consumer has
+ *     moved to `active`.
+ *   - Inserting / promoting the `Default` row — the boot-time
+ *     reconciler (`default-channel-reconciler.ts`) is the single source
+ *     of truth (R-4).
+ *
+ * The down() reverses every up() step; the legacy columns are not
+ * touched. It no longer drops the eight bridge tables, nor the
+ * `quote_requests` column, because this migration no longer creates either —
+ * each migration that took a statement drops its own.
+ *
+ * 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 `sales_channels` made `modules:uninstall --hard sales_channels` drop
+ * kernel schema.
+ */
+export class Migration20260430T170044CoreSalesChannelsPromote extends Migration {
+    async up() {
+        // -- 1. Identity columns ------------------------------------------------
+        this.addSql('alter table "sales_channels" add column "logo_asset_id" uuid null;');
+        this.addSql('alter table "sales_channels" add constraint "sales_channels_logo_asset_fk" ' +
+            'foreign key ("logo_asset_id") references "assets" ("id") on delete set null;');
+        this.addSql('alter table "sales_channels" add column "theme_code" varchar(64) null;');
+        this.addSql('alter table "sales_channels" add column "languages" jsonb not null default \'[]\'::jsonb;');
+        this.addSql('alter table "sales_channels" add column "currencies" jsonb not null default \'[]\'::jsonb;');
+        this.addSql('alter table "sales_channels" add column "active" boolean not null default true;');
+        this.addSql('alter table "sales_channels" add column "system_default" boolean not null default false;');
+        this.addSql('alter table "sales_channels" add column "version" int not null default 1;');
+        // -- 2. Backfills (data-only; safe and idempotent) ----------------------
+        // Seed the new jsonb arrays from the existing scalar defaults.
+        this.addSql('update "sales_channels" set "languages" = jsonb_build_array("default_language") ' +
+            "where jsonb_array_length(\"languages\") = 0;");
+        this.addSql('update "sales_channels" set "currencies" = jsonb_build_array("default_currency") ' +
+            "where jsonb_array_length(\"currencies\") = 0;");
+        // Mirror legacy `status='active'` into the new boolean.
+        this.addSql("update \"sales_channels\" set \"active\" = (\"status\" = 'active');");
+        // -- 3. Partial unique index (FR-002) -----------------------------------
+        this.addSql('create unique index "sales_channels_one_system_default" ' +
+            'on "sales_channels" ("system_default") where "system_default" = true;');
+    }
+    async down() {
+        // 3. Partial unique index
+        this.addSql('drop index if exists "sales_channels_one_system_default";');
+        // 1. Identity columns
+        this.addSql('alter table "sales_channels" drop column if exists "version";');
+        this.addSql('alter table "sales_channels" drop column if exists "system_default";');
+        this.addSql('alter table "sales_channels" drop column if exists "active";');
+        this.addSql('alter table "sales_channels" drop column if exists "currencies";');
+        this.addSql('alter table "sales_channels" drop column if exists "languages";');
+        this.addSql('alter table "sales_channels" drop column if exists "theme_code";');
+        this.addSql('alter table "sales_channels" drop constraint if exists "sales_channels_logo_asset_fk";');
+        this.addSql('alter table "sales_channels" drop column if exists "logo_asset_id";');
+    }
+}
+//# sourceMappingURL=20260430T170044_core_sales_channels_promote.js.map

package/dist/migrations/20260430T170044_core_sales_channels_promote.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260430T170044_core_sales_channels_promote.js","sourceRoot":"","sources":["../../src/migrations/20260430T170044_core_sales_channels_promote.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4DG;AACH,MAAM,OAAO,gDAAiD,SAAQ,SAAS;IACpE,KAAK,CAAC,EAAE;QACf,0EAA0E;QAC1E,IAAI,CAAC,MAAM,CACT,oEAAoE,CACrE,CAAC;QACF,IAAI,CAAC,MAAM,CACT,6EAA6E;YAC3E,8EAA8E,CACjF,CAAC;QACF,IAAI,CAAC,MAAM,CACT,wEAAwE,CACzE,CAAC;QACF,IAAI,CAAC,MAAM,CACT,2FAA2F,CAC5F,CAAC;QACF,IAAI,CAAC,MAAM,CACT,4FAA4F,CAC7F,CAAC;QACF,IAAI,CAAC,MAAM,CACT,iFAAiF,CAClF,CAAC;QACF,IAAI,CAAC,MAAM,CACT,0FAA0F,CAC3F,CAAC;QACF,IAAI,CAAC,MAAM,CACT,2EAA2E,CAC5E,CAAC;QAEF,0EAA0E;QAC1E,+DAA+D;QAC/D,IAAI,CAAC,MAAM,CACT,kFAAkF;YAChF,8CAA8C,CACjD,CAAC;QACF,IAAI,CAAC,MAAM,CACT,mFAAmF;YACjF,+CAA+C,CAClD,CAAC;QACF,wDAAwD;QACxD,IAAI,CAAC,MAAM,CACT,qEAAqE,CACtE,CAAC;QAEF,0EAA0E;QAC1E,IAAI,CAAC,MAAM,CACT,0DAA0D;YACxD,uEAAuE,CAC1E,CAAC;IACJ,CAAC;IAEQ,KAAK,CAAC,IAAI;QACjB,0BAA0B;QAC1B,IAAI,CAAC,MAAM,CAAC,2DAA2D,CAAC,CAAC;QAEzE,sBAAsB;QACtB,IAAI,CAAC,MAAM,CAAC,+DAA+D,CAAC,CAAC;QAC7E,IAAI,CAAC,MAAM,CAAC,sEAAsE,CAAC,CAAC;QACpF,IAAI,CAAC,MAAM,CAAC,8DAA8D,CAAC,CAAC;QAC5E,IAAI,CAAC,MAAM,CAAC,kEAAkE,CAAC,CAAC;QAChF,IAAI,CAAC,MAAM,CAAC,iEAAiE,CAAC,CAAC;QAC/E,IAAI,CAAC,MAAM,CAAC,kEAAkE,CAAC,CAAC;QAChF,IAAI,CAAC,MAAM,CACT,wFAAwF,CACzF,CAAC;QACF,IAAI,CAAC,MAAM,CAAC,qEAAqE,CAAC,CAAC;IACrF,CAAC;CACF"}

package/dist/migrations/20260506T200657_core_module_lifecycle_init.d.ts

@@ -0,0 +1,21 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Module Lifecycle subsystem — feature 018 / data-model.md.
+ *
+ * Schema changes (one atomic migration):
+ *   - new table `module_registrations` — persisted runtime state of every
+ *     module the system has ever installed. PK is the module id (matches
+ *     manifest `id`); state CHECK enforces the four-state FSM
+ *     (installing / installed / disabled / uninstalled).
+ *   - btree index `idx_module_registrations_state` to support
+ *     `module:status --filter=<state>` (low cardinality but cheap).
+ *
+ * No seed rows. Existing modules are recorded in this table only after
+ * their first `module:install <id>` run (which is what the retrofit pass
+ * upgrades the existing settings-only manifests into).
+ */
+export declare class Migration20260506T200657CoreModuleLifecycleInit extends Migration {
+    up(): Promise<void>;
+    down(): Promise<void>;
+}
+//# sourceMappingURL=20260506T200657_core_module_lifecycle_init.d.ts.map

package/dist/migrations/20260506T200657_core_module_lifecycle_init.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260506T200657_core_module_lifecycle_init.d.ts","sourceRoot":"","sources":["../../src/migrations/20260506T200657_core_module_lifecycle_init.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;GAcG;AACH,qBAAa,+CAAgD,SAAQ,SAAS;IAC7D,EAAE,IAAI,OAAO,CAAC,IAAI,CAAC;IAsBnB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;CAGrC"}

package/dist/migrations/20260506T200657_core_module_lifecycle_init.js

@@ -0,0 +1,41 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Module Lifecycle subsystem — feature 018 / data-model.md.
+ *
+ * Schema changes (one atomic migration):
+ *   - new table `module_registrations` — persisted runtime state of every
+ *     module the system has ever installed. PK is the module id (matches
+ *     manifest `id`); state CHECK enforces the four-state FSM
+ *     (installing / installed / disabled / uninstalled).
+ *   - btree index `idx_module_registrations_state` to support
+ *     `module:status --filter=<state>` (low cardinality but cheap).
+ *
+ * No seed rows. Existing modules are recorded in this table only after
+ * their first `module:install <id>` run (which is what the retrofit pass
+ * upgrades the existing settings-only manifests into).
+ */
+export class Migration20260506T200657CoreModuleLifecycleInit extends Migration {
+    async up() {
+        this.addSql(`
+      create table "module_registrations" (
+        "module_id" varchar(80) not null,
+        "state" varchar(16) not null,
+        "version" varchar(32) not null,
+        "installed_at" timestamptz not null,
+        "last_state_change_at" timestamptz not null,
+        "last_install_failed_at" timestamptz null,
+        "last_install_error" text null,
+        "created_at" timestamptz not null default now(),
+        "updated_at" timestamptz not null default now(),
+        constraint "module_registrations_pkey" primary key ("module_id"),
+        constraint "module_registrations_state_check" check ("state" in
+          ('installing', 'installed', 'disabled', 'uninstalled'))
+      );
+    `);
+        this.addSql(`create index "idx_module_registrations_state" on "module_registrations" ("state");`);
+    }
+    async down() {
+        this.addSql(`drop table if exists "module_registrations";`);
+    }
+}
+//# sourceMappingURL=20260506T200657_core_module_lifecycle_init.js.map

package/dist/migrations/20260506T200657_core_module_lifecycle_init.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260506T200657_core_module_lifecycle_init.js","sourceRoot":"","sources":["../../src/migrations/20260506T200657_core_module_lifecycle_init.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;GAcG;AACH,MAAM,OAAO,+CAAgD,SAAQ,SAAS;IACnE,KAAK,CAAC,EAAE;QACf,IAAI,CAAC,MAAM,CAAC;;;;;;;;;;;;;;;KAeX,CAAC,CAAC;QACH,IAAI,CAAC,MAAM,CACT,oFAAoF,CACrF,CAAC;IACJ,CAAC;IAEQ,KAAK,CAAC,IAAI;QACjB,IAAI,CAAC,MAAM,CAAC,8CAA8C,CAAC,CAAC;IAC9D,CAAC;CACF"}

package/dist/migrations/20260514T111329_core_settings_global_value.d.ts

@@ -0,0 +1,30 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Add a platform-wide "global override" tier to settings.
+ *
+ * Before: resolver chain was per-channel `setting_values` row → manifest
+ * `settings.default_value`. "All channels" admin writes broadcast a row
+ * to every channel.
+ *
+ * After: chain is per-channel `setting_values` row → `settings.global_value`
+ * (when non-NULL) → manifest `settings.default_value`. "All channels" admin
+ * writes update `global_value` only; per-channel rows are untouched. Channels
+ * without an explicit override inherit `global_value` when present, otherwise
+ * fall back to the manifest default.
+ *
+ * A NULL `global_value` means "no global override set" — the admin has not
+ * customised the platform-wide value, so the manifest default applies. An
+ * admin who legitimately wants a literal JSON null at the global tier still
+ * needs the per-channel route; this is an accepted edge case (see
+ * specs/004-settings-module/data-model.md once it's updated).
+ *
+ * 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 declare class Migration20260514T111329CoreSettingsGlobalValue extends Migration {
+    up(): Promise<void>;
+    down(): Promise<void>;
+}
+//# sourceMappingURL=20260514T111329_core_settings_global_value.d.ts.map

package/dist/migrations/20260514T111329_core_settings_global_value.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260514T111329_core_settings_global_value.d.ts","sourceRoot":"","sources":["../../src/migrations/20260514T111329_core_settings_global_value.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,qBAAa,+CAAgD,SAAQ,SAAS;IAC7D,EAAE,IAAI,OAAO,CAAC,IAAI,CAAC;IAMnB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;CAGrC"}

package/dist/migrations/20260514T111329_core_settings_global_value.js

@@ -0,0 +1,34 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Add a platform-wide "global override" tier to settings.
+ *
+ * Before: resolver chain was per-channel `setting_values` row → manifest
+ * `settings.default_value`. "All channels" admin writes broadcast a row
+ * to every channel.
+ *
+ * After: chain is per-channel `setting_values` row → `settings.global_value`
+ * (when non-NULL) → manifest `settings.default_value`. "All channels" admin
+ * writes update `global_value` only; per-channel rows are untouched. Channels
+ * without an explicit override inherit `global_value` when present, otherwise
+ * fall back to the manifest default.
+ *
+ * A NULL `global_value` means "no global override set" — the admin has not
+ * customised the platform-wide value, so the manifest default applies. An
+ * admin who legitimately wants a literal JSON null at the global tier still
+ * needs the per-channel route; this is an accepted edge case (see
+ * specs/004-settings-module/data-model.md once it's updated).
+ *
+ * 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 Migration20260514T111329CoreSettingsGlobalValue extends Migration {
+    async up() {
+        this.addSql('alter table "settings" add column "global_value" jsonb null;');
+    }
+    async down() {
+        this.addSql('alter table "settings" drop column "global_value";');
+    }
+}
+//# sourceMappingURL=20260514T111329_core_settings_global_value.js.map

package/dist/migrations/20260514T111329_core_settings_global_value.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260514T111329_core_settings_global_value.js","sourceRoot":"","sources":["../../src/migrations/20260514T111329_core_settings_global_value.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,OAAO,+CAAgD,SAAQ,SAAS;IACnE,KAAK,CAAC,EAAE;QACf,IAAI,CAAC,MAAM,CACT,8DAA8D,CAC/D,CAAC;IACJ,CAAC;IAEQ,KAAK,CAAC,IAAI;QACjB,IAAI,CAAC,MAAM,CAAC,oDAAoD,CAAC,CAAC;IACpE,CAAC;CACF"}

package/dist/migrations/20260611T140411_core_settings_secret_value_type.d.ts

@@ -0,0 +1,26 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Settings `secret` value type (feature 043, FR-021 / research §R10).
+ *
+ * 1. Extends the `setting_value_type` Postgres enum with `'secret'`. 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.
+ *    Values present in a CREATE TYPE carry no such restriction.
+ * 2. Retrofits `search.llm.embedder_api_key` (feature 006) to the new type so
+ *    the boot reconciler sees no `valueType` diff against the updated search
+ *    manifest. The stored value itself needs no rewrite: a legacy plaintext
+ *    string keeps resolving via the codec's passthrough and is re-encrypted
+ *    on the next admin write.
+ *
+ * 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 declare class Migration20260611T140411CoreSettingsSecretValueType extends Migration {
+    up(): Promise<void>;
+    down(): Promise<void>;
+}
+//# sourceMappingURL=20260611T140411_core_settings_secret_value_type.d.ts.map

package/dist/migrations/20260611T140411_core_settings_secret_value_type.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260611T140411_core_settings_secret_value_type.d.ts","sourceRoot":"","sources":["../../src/migrations/20260611T140411_core_settings_secret_value_type.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;GAmBG;AACH,qBAAa,mDAAoD,SAAQ,SAAS;IACjE,EAAE,IAAI,OAAO,CAAC,IAAI,CAAC;IAoBnB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;CAqBrC"}

package/dist/migrations/20260611T140411_core_settings_secret_value_type.js

@@ -0,0 +1,63 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Settings `secret` value type (feature 043, FR-021 / research §R10).
+ *
+ * 1. Extends the `setting_value_type` Postgres enum with `'secret'`. 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.
+ *    Values present in a CREATE TYPE carry no such restriction.
+ * 2. Retrofits `search.llm.embedder_api_key` (feature 006) to the new type so
+ *    the boot reconciler sees no `valueType` diff against the updated search
+ *    manifest. The stored value itself needs no rewrite: a legacy plaintext
+ *    string keeps resolving via the codec's passthrough and is re-encrypted
+ *    on the next admin write.
+ *
+ * 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 Migration20260611T140411CoreSettingsSecretValueType 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');
+    `);
+        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(`
+      update "settings"
+        set "value_type" = 'secret'
+        where "code" = 'search.llm.embedder_api_key';
+    `);
+    }
+    async down() {
+        // Every secret row (the retrofitted search key plus any reconciler-created
+        // secrets, e.g. prompt_actions.api_key) must leave the enum value before
+        // the narrowing cast below.
+        this.addSql(`
+      update "settings"
+        set "value_type" = 'string'
+        where "value_type" = 'secret';
+    `);
+        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');
+    `);
+        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=20260611T140411_core_settings_secret_value_type.js.map

package/dist/migrations/20260611T140411_core_settings_secret_value_type.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260611T140411_core_settings_secret_value_type.js","sourceRoot":"","sources":["../../src/migrations/20260611T140411_core_settings_secret_value_type.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,OAAO,mDAAoD,SAAQ,SAAS;IACvE,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;;;;KAIX,CAAC,CAAC;IACL,CAAC;IAEQ,KAAK,CAAC,IAAI;QACjB,2EAA2E;QAC3E,yEAAyE;QACzE,4BAA4B;QAC5B,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/20260611T140419_core_settings_enum_options.d.ts

@@ -0,0 +1,19 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Settings enum options (task: Speculation Rules eagerness dropdown).
+ *
+ * Adds a nullable `enum_options` JSONB column to `settings`. When non-null the
+ * setting is an enum-style `string` setting: the admin renders a dropdown and
+ * the backend constrains writes to the listed values. NULL keeps the legacy
+ * free-text behaviour, so the column is purely additive and needs no backfill.
+ *
+ * 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 declare class Migration20260611T140419CoreSettingsEnumOptions extends Migration {
+    up(): Promise<void>;
+    down(): Promise<void>;
+}
+//# sourceMappingURL=20260611T140419_core_settings_enum_options.d.ts.map

package/dist/migrations/20260611T140419_core_settings_enum_options.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260611T140419_core_settings_enum_options.d.ts","sourceRoot":"","sources":["../../src/migrations/20260611T140419_core_settings_enum_options.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;GAYG;AACH,qBAAa,+CAAgD,SAAQ,SAAS;IAC7D,EAAE,IAAI,OAAO,CAAC,IAAI,CAAC;IAInB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;CAGrC"}

package/dist/migrations/20260611T140419_core_settings_enum_options.js

@@ -0,0 +1,23 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Settings enum options (task: Speculation Rules eagerness dropdown).
+ *
+ * Adds a nullable `enum_options` JSONB column to `settings`. When non-null the
+ * setting is an enum-style `string` setting: the admin renders a dropdown and
+ * the backend constrains writes to the listed values. NULL keeps the legacy
+ * free-text behaviour, so the column is purely additive and needs no backfill.
+ *
+ * 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 Migration20260611T140419CoreSettingsEnumOptions extends Migration {
+    async up() {
+        this.addSql(`alter table "settings" add column "enum_options" jsonb null;`);
+    }
+    async down() {
+        this.addSql(`alter table "settings" drop column "enum_options";`);
+    }
+}
+//# sourceMappingURL=20260611T140419_core_settings_enum_options.js.map

package/dist/migrations/20260611T140419_core_settings_enum_options.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260611T140419_core_settings_enum_options.js","sourceRoot":"","sources":["../../src/migrations/20260611T140419_core_settings_enum_options.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;GAYG;AACH,MAAM,OAAO,+CAAgD,SAAQ,SAAS;IACnE,KAAK,CAAC,EAAE;QACf,IAAI,CAAC,MAAM,CAAC,8DAA8D,CAAC,CAAC;IAC9E,CAAC;IAEQ,KAAK,CAAC,IAAI;QACjB,IAAI,CAAC,MAAM,CAAC,oDAAoD,CAAC,CAAC;IACpE,CAAC;CACF"}

package/dist/migrations/20260629T090100_core_settings_hidden_flag.d.ts

@@ -0,0 +1,20 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Settings hidden flag (single-source-of-truth for module-owned settings).
+ *
+ * Adds a non-null `hidden` boolean column (default false) to `settings`. When
+ * true the setting is excluded from the generic admin Settings screen and
+ * managed only through its owning module's dedicated UI (e.g. the PWA settings
+ * page), while remaining fully readable/writable by code. Purely additive —
+ * existing rows default to visible, so no backfill is required.
+ *
+ * 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 declare class Migration20260629T090100CoreSettingsHiddenFlag extends Migration {
+    up(): Promise<void>;
+    down(): Promise<void>;
+}
+//# sourceMappingURL=20260629T090100_core_settings_hidden_flag.d.ts.map

package/dist/migrations/20260629T090100_core_settings_hidden_flag.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260629T090100_core_settings_hidden_flag.d.ts","sourceRoot":"","sources":["../../src/migrations/20260629T090100_core_settings_hidden_flag.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;GAaG;AACH,qBAAa,8CAA+C,SAAQ,SAAS;IAC5D,EAAE,IAAI,OAAO,CAAC,IAAI,CAAC;IAInB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;CAGrC"}

package/dist/migrations/20260629T090100_core_settings_hidden_flag.js

@@ -0,0 +1,24 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Settings hidden flag (single-source-of-truth for module-owned settings).
+ *
+ * Adds a non-null `hidden` boolean column (default false) to `settings`. When
+ * true the setting is excluded from the generic admin Settings screen and
+ * managed only through its owning module's dedicated UI (e.g. the PWA settings
+ * page), while remaining fully readable/writable by code. Purely additive —
+ * existing rows default to visible, so no backfill is required.
+ *
+ * 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 Migration20260629T090100CoreSettingsHiddenFlag extends Migration {
+    async up() {
+        this.addSql(`alter table "settings" add column "hidden" boolean not null default false;`);
+    }
+    async down() {
+        this.addSql(`alter table "settings" drop column "hidden";`);
+    }
+}
+//# sourceMappingURL=20260629T090100_core_settings_hidden_flag.js.map

package/dist/migrations/20260629T090100_core_settings_hidden_flag.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260629T090100_core_settings_hidden_flag.js","sourceRoot":"","sources":["../../src/migrations/20260629T090100_core_settings_hidden_flag.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;GAaG;AACH,MAAM,OAAO,8CAA+C,SAAQ,SAAS;IAClE,KAAK,CAAC,EAAE;QACf,IAAI,CAAC,MAAM,CAAC,4EAA4E,CAAC,CAAC;IAC5F,CAAC;IAEQ,KAAK,CAAC,IAAI;QACjB,IAAI,CAAC,MAAM,CAAC,8CAA8C,CAAC,CAAC;IAC9D,CAAC;CACF"}

package/dist/migrations/20260717T134752_core_tenant_scope_indexes.d.ts

@@ -0,0 +1,27 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Feature 050 — index the tenant-key columns the guard filters on, where the
+ * index audit (research §R5) found a gap. Most org/customer-scoped tables were
+ * already indexed on their tenant key; these three were not.
+ *
+ * **It is empty since `specs/120-migration-closure-bridge-ownership/` Phase 3,
+ * and the class stays.** All three indexes were on module-owned tables —
+ * `analytics_events` twice and `newsletter_subscribers` once — and under D-226
+ * the platform may name only what it creates itself: it declares no
+ * dependencies, so it can never be ordered after a module's table, and an
+ * instance omitting `analytics` or `newsletter` could not migrate a fresh
+ * database at all. The statements moved to
+ * `Migration20260912T125655AnalyticsEventsTenantScopeIndexes` and
+ * `Migration20260912T125702NewsletterSubscriberTenantScopeIndex`, verbatim.
+ *
+ * The class name is on `BASELINE_MIGRATIONS` and cannot go: `mikro_orm_migrations`
+ * persists the name and no checksum, so every database that has already applied
+ * this migration is offered nothing, and deleting the class would make it
+ * pending nowhere while moving 70-odd frozen positions. An empty `up()` is what
+ * a migration whose whole body moved elsewhere looks like.
+ */
+export declare class Migration20260717T134752CoreTenantScopeIndexes extends Migration {
+    up(): Promise<void>;
+    down(): Promise<void>;
+}
+//# sourceMappingURL=20260717T134752_core_tenant_scope_indexes.d.ts.map

package/dist/migrations/20260717T134752_core_tenant_scope_indexes.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260717T134752_core_tenant_scope_indexes.d.ts","sourceRoot":"","sources":["../../src/migrations/20260717T134752_core_tenant_scope_indexes.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,qBAAa,8CAA+C,SAAQ,SAAS;IAC5D,EAAE,IAAI,OAAO,CAAC,IAAI,CAAC;IAInB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;CAIrC"}

package/dist/migrations/20260717T134752_core_tenant_scope_indexes.js

@@ -0,0 +1,32 @@
+import { Migration } from '@mikro-orm/migrations';
+/**
+ * Feature 050 — index the tenant-key columns the guard filters on, where the
+ * index audit (research §R5) found a gap. Most org/customer-scoped tables were
+ * already indexed on their tenant key; these three were not.
+ *
+ * **It is empty since `specs/120-migration-closure-bridge-ownership/` Phase 3,
+ * and the class stays.** All three indexes were on module-owned tables —
+ * `analytics_events` twice and `newsletter_subscribers` once — and under D-226
+ * the platform may name only what it creates itself: it declares no
+ * dependencies, so it can never be ordered after a module's table, and an
+ * instance omitting `analytics` or `newsletter` could not migrate a fresh
+ * database at all. The statements moved to
+ * `Migration20260912T125655AnalyticsEventsTenantScopeIndexes` and
+ * `Migration20260912T125702NewsletterSubscriberTenantScopeIndex`, verbatim.
+ *
+ * The class name is on `BASELINE_MIGRATIONS` and cannot go: `mikro_orm_migrations`
+ * persists the name and no checksum, so every database that has already applied
+ * this migration is offered nothing, and deleting the class would make it
+ * pending nowhere while moving 70-odd frozen positions. An empty `up()` is what
+ * a migration whose whole body moved elsewhere looks like.
+ */
+export class Migration20260717T134752CoreTenantScopeIndexes extends Migration {
+    async up() {
+        // Moved to the two modules that own the tables — see the class comment.
+    }
+    async down() {
+        // Nothing to reverse: each moved statement is reversed by the migration
+        // that now carries it.
+    }
+}
+//# sourceMappingURL=20260717T134752_core_tenant_scope_indexes.js.map

package/dist/migrations/20260717T134752_core_tenant_scope_indexes.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260717T134752_core_tenant_scope_indexes.js","sourceRoot":"","sources":["../../src/migrations/20260717T134752_core_tenant_scope_indexes.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAElD;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,MAAM,OAAO,8CAA+C,SAAQ,SAAS;IAClE,KAAK,CAAC,EAAE;QACf,wEAAwE;IAC1E,CAAC;IAEQ,KAAK,CAAC,IAAI;QACjB,wEAAwE;QACxE,uBAAuB;IACzB,CAAC;CACF"}

package/dist/migrations/20260721T011510_core_settings_credential_ref_value_type.d.ts

@@ -0,0 +1,24 @@
+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 declare class Migration20260721T011510CoreSettingsCredentialRefValueType extends Migration {
+    up(): Promise<void>;
+    down(): Promise<void>;
+}
+//# sourceMappingURL=20260721T011510_core_settings_credential_ref_value_type.d.ts.map

package/dist/migrations/20260721T011510_core_settings_credential_ref_value_type.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"20260721T011510_core_settings_credential_ref_value_type.d.ts","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,qBAAa,0DAA2D,SAAQ,SAAS;IACxE,EAAE,IAAI,OAAO,CAAC,IAAI,CAAC;IAgBnB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC;CAsBrC"}