Module-owned migration chain for the shop tables (phoenix_kit_shop_config, phoenix_kit_shop_shipping_methods, phoenix_kit_shop_categories, phoenix_kit_shop_products, phoenix_kit_shop_product_slugs, phoenix_kit_shop_category_slugs, phoenix_kit_shop_carts, phoenix_kit_shop_cart_items, phoenix_kit_shop_import_configs, phoenix_kit_shop_import_logs) plus the two slug-projection functions and their triggers.

Ownership situation — read before touching

All ten tables are core V135(+later) baseline tables; core still creates them today. V1 is purely an ADOPTION step (owner decision 2026-09-05: this chain adopts every shop table, including phoenix_kit_shop_products and phoenix_kit_shop_categories, so upstream phoenix_kit_ecommerce — which still owns products for hosts that have not switched to the catalogue — stays whole through core's next baseline squash):

• on existing installs every table is already there (core's baseline), the CREATE TABLE IF NOT EXISTS finds it, and the only new objects are the CREATE OR REPLACE FUNCTION bodies (already core-owned, unchanged) and the pke_schema:1 marker;
• on a hypothetical future install whose core baseline no longer creates these tables, the same statements create them — shape-identical to core's objects, with core's exact index, constraint, function and trigger names.

This deployment's shop_products/shop_categories/both slug projections are deprecated in favor of phoenix_kit_catalogue later (Block 3, after the storefront switch) via a host-side COMMENT ON TABLE … 'deprecated …' — never a DROP, and not part of this chain.

What down/1 is NOT

down/1 unstamps the version marker; it NEVER drops any of the ten tables, the two functions, or the two triggers. The tables are core-created, and rolling back this module's chain must not destroy data — only core's own baseline rollback does that.

The migrated version is tracked as a pke_schema:<N> COMMENT on phoenix_kit_shop_config (the marker convention phoenix_kit_billing, phoenix_kit_entities and phoenix_kit_catalogue also use). A marker-less or foreign-comment table reads as version 0 — the core-baseline shape before this chain existed.

Protocol: phoenix_kit_hello_world README, "Adopting a table core already creates (extraction)".

Every column name below is double-quoted, unlike the pg_dump source (which only quotes "position", a reserved word). This is a normalization, not drift — the two forms are semantically identical.