migrations

var LegacyPostgres fs.FS = mustSubFS(legacyFS, "legacy")

LegacyPostgres is the pre-ContentKit combined lineage (searchkit app id). Installations created from it keep applying it: its final migration converges on the keyword profile schema and drops the embedding tables. Export those tables before applying it (docs/migration.md). Never use it for a new installation.

var Postgres fs.FS = mustSubFS(keywordFS, "keyword")

Postgres is the keyword profile: the only Postgres search lineage for new installations. It requires pg_trgm and PGroonga and no vector extension. Apply it under its own migratekit app id, scoped to the keyword schema.

var SignalClickHouse fs.FS = mustSubFS(signalClickHouseFS, "clickhouse/signal")

SignalClickHouse is the signal-plane ClickHouse lineage. Apply it with migratekit chmigrate to the dedicated signal database (see signal.CreateDatabase) under its own app identity; check compatibility at startup with signal.CheckSchema.

var Social fs.FS = mustSubFS(socialFS, "social")

Social is the interaction lineage (social_* tables) applied into the host schema under content.MigratekitApp; every file carries a parent link.

var Taxonomy fs.FS = mustSubFS(taxonomyFS, "taxonomy")

Taxonomy is the catalog lineage (content_nodes, content_node_names, content_edges, content_assignments, content_node_counts). Apply it under its own migratekit app id (contentkit_taxonomy) into the same host schema after the keyword profile, which it depends on.