How should you properly handle schema migration in Hive when you genuinely need to add, remove, or meaningfully change a specific field on an already existing HiveObject class after your app has genuinely already been released to real actual users?

Since Hive genuinely does not automatically handle schema migrations completely on its own the exact same way certain other more full featured databases genuinely do, properly and safely adding a genuinely new additional field to an already existing HiveObject class generally requires making that specific new field genuinely nullable or properly providing a genuinely reasonable sensible default value, since existing already stored objects genuinely will not actually have that new particular field's own data already present, and more significant genuinely structural changes, such as properly and fully renaming or entirely removing an already existing field, typically require writing a dedicated custom migration function that properly runs once during your app's own startup to correctly read, transform, and then properly rewrite your existing already stored data into its own required new correct format.

// Adding a genuinely new nullable field safely preserves compatibility
@HiveField(2)
String? notes;