# Post-schema migrations applied AFTER directus schema apply runs.
#
# Pre-schema migrations live in ../db-init/ — they create tables that
# Directus does NOT manage (positions hypertable, faulty column, future
# PostGIS extension). Post-schema migrations live here — they constrain
# tables that Directus DOES manage (organization_*, events, entries,
# entry_*, classes), which are created by `directus schema apply` from
# the snapshot YAML during entrypoint step 2/5.
#
# Order at boot:
#   1. apply-db-init.sh    DB_INIT_DIR=/directus/db-init       (pre-schema)
#   2. schema-apply.sh                                          (Directus tables created)
#   3. apply-db-init.sh    DB_INIT_DIR=/directus/db-init-post   (post-schema)
#   4. directus bootstrap
#   5. directus start
#
# Both pre- and post- runs share the same `migrations_applied` guard
# table. Filenames must be unique across both directories (which they
# are by convention — pre-schema files start with descriptive names
# from the table they create; post-schema files start with descriptive
# names from the constraint they add).