Module-owned versioned migrations for phoenix_kit_document_creator — the decentralized-migrations protocol core's mix phoenix_kit.update discovers via migration_module/0 (current_version/0 + migrated_version_runtime/1 + idempotent up/1 + version-aware down/1). Adopted per the workspace direction of moving module tables out of the core chain (phoenix_kit_projects is the reference implementation; the doc TABLES themselves remain core-created — V86 + V94 — this chain only ITERATES on them).

Versions:

• V1 — phoenix_kit_doc_documents.project_uuid (nullable FK → phoenix_kit_projects, ON DELETE SET NULL): real per-project document linkage for the projects hub's Documents tab. The FK target is core-created (V101), present on every current install.
• V2 — phoenix_kit_doc_template_taxonomy join table: a template's membership in one category, with an optional group (type_uuid). Replaces the single category_uuid/type_uuid FKs on phoenix_kit_doc_templates with a many-to-many model (a template may belong to several categories, each with its own group). Existing (category_uuid, type_uuid) bindings are backfilled as one row each. The legacy template columns are kept as a compatibility mirror of the primary membership and stamped with a deprecation COMMENT — they must not be dropped until the ANDI consumer migrates.

The migrated version is tracked as a dcr_schema:<N> COMMENT on phoenix_kit_doc_documents (the marker convention from the projects chain, namespaced). A marker-less table reads as version 0 — the core baseline shape before this chain existed.