AF12

resetField tried to restore a whole subtree from the form's originals and the write was rejected.

In development this reads:

attaform resetField: subtree write rejected at path 'address' — originals contain values that don't satisfy the slim primitive shape. This is a bug in the construction pipeline.

The production message appends the path after the code.

What happened

Same invariant as AF11, at container scope: the subtree assembled from originals should always fit the schema, so a rejected write means the construction-time guarantee broke upstream. The reset for that subtree is skipped; the rest of the form is unaffected.

What to do

Open an issue with the schema for the reported path and the steps that led to the reset. The distinct code (leaf vs subtree) is part of the report's value.