mariadb-agents-migration-validator

A deterministic procedure for validating a MySQL SQL dump, schema, or codebase BEFORE importing into MariaDB. This is an ORCHESTRATION skill : it does not teach migration, it applies a fixed 10-dimension scan and produces a graded validation report. Every finding cites the canonical skill that explains the fix and the exact MySQL-vs-MariaDB divergence.

Quick Reference

• Scan ALL 10 divergence dimensions in order. NEVER skip a dimension because the dump "looks standard".
• Grade every finding with one of three severities : BLOCKER, WARNING, SUGGESTION.
• BLOCKER : the dump will not import correctly or apps will break. Examples : caching_sha2_password users, INVISIBLE INDEX keyword, GTID-continuity expectation, GROUPS window frame, MySQL 8 functional-index syntax.
• WARNING : the dump imports but carries a known footgun. Examples : JSON columns (no enforcement after import), sql_mode default differences, non-InnoDB storage engines.
• SUGGESTION : a non-blocking improvement. Examples : utf8 (utf8mb3) charset, AUTO_INCREMENT that could become a sequence.
• MariaDB JSON is a LONGTEXT alias, NOT native binary. Use CHECK (JSON_VALID(col)) for structure ; use functional indexes on virtual columns for index access. A migrated JSON column has NO write-time validation until the CHECK is added. (D-010, L-005)
• Every finding cites the canonical skill that explains the fix. NEVER report a divergence without a skill-ref.
• Output a single findings table : finding, severity, location, MySQL-vs-MariaDB divergence, remediation step, skill-ref. Close with a verdict line.
• ALWAYS recommend running mariadb-upgrade exactly once AFTER the import, regardless of the verdict.
• A clean dump still gets a report : the table has zero rows and the verdict is PASS.

The 10 Divergence Dimensions