UX bug: after adding an array item, a new one is created and its required fields are immediately required

https://www.dropbox.com/s/aqla5ocfwjt8703/ypzcck10.png?raw=1

This is an array with a single, required string field.

I added one, which started a form for a second one. I was unable to save the array until I removed the second one. This is not a smooth experience.

Reproduce the issue described in the body with an array containing one required string field, using the linked screenshot as the visual reference. Trace the array form behavior and define done as allowing the array to be saved after adding an item without an unintended second item making its required field block submission.

Written by the indexing model from the issue text.