Problem: When keepDirtyOnReinitialize is true and array fields are used (e.g., with final-form-arrays), pristine child fields don't update to new initial values. The parent array field's dirty value overwrites them.

Root Cause: When saving dirty values, the code saves ALL dirty fields including parent array fields (e.g., customers) AND their children (e.g., customers[0].firstName). When setting values back, the parent array value overwrites pristine children.

Example Bug:

// Register both array field and children
form.registerField('customers', ...) // Array field
form.registerField('customers[0].firstName', ...) // Child
form.registerField('customers[1].lastName', ...) // Child

// Modify one child
form.change('customers[0].firstName', 'Modified')

// Reinitialize with new data
form.initialize({ customers: [
  { firstName: 'New1', lastName: 'NewLast1' },
  { firstName: 'New2', lastName: 'NewLast2' }
]})

// BUG: customers[1].lastName keeps old value instead of updating to 'NewLast2'
// because 'customers' array was saved as dirty and overwrote it

Solution: When saving dirty values, skip parent fields if child fields are registered. For example, if both customers and customers[0].firstName are registered, only save dirty values for the child fields.

This allows:

• ✅ Dirty children keep their modified values
• ✅ Pristine children update to new initial values
• ✅ Parent array doesn't override children

Testing:

• Added test with array field + child fields
• Verifies modified child keeps value, pristine child updates
• All existing tests pass

Fixes #366

Summary by CodeRabbit

• Bug Fixes

  • Refined dirty-state persistence during form reinitialization so edits inside nested array fields are preserved while untouched values adopt new initial data.

• Tests

  • Added test coverage validating dirty-state behavior for nested array fields during reinitialization.

• Chores

  • Updated build metadata size limit for the distributed bundle.