What problem does it solve? Changing an Android Room database schema without a proper migration risks destroying user data or crashing the app on upgrade. This Skill provides the rules, templates, and testing practices to evolve the Solvyx database schema safely across versions. ## Core Features & Use Cases - Migration Templates: Ready-to-use Kotlin patterns for additive changes, table renames, and full data-copy migrations using Migration classes and SupportSQLiteDatabase. - Versioning Rules: A decision table defining when to bump @Database version and how to register migrations in AppDatabase.MIGRATIONS without fallbackToDestructiveMigration. - Migration Testing: AndroidX MigrationTestHelper test patterns plus schema JSON export via KSP to validate that upgrades preserve existing user data. - Use Case: When adding a suenoHoras column to the bitacora_entries table, follow the additive migration template, register MIGRATION_4_5, export the schema, and write a test proving existing rows survive the upgrade. ## Quick Start Ask the assistant to write a Room migration from version 4 to 5 that adds a nullable column to an existing table, including the migration test and schema export setup.