By design, the EMF Validation framework runs checks from a read-only environment. The model cannot be modified from a check.
If you want a fix, you should add it to the "fix" entry in your constraint. I'm not sure what your constraint is trying to do though: wouldn't it keep adding fields whenever you had zero, two or more fields?
Please explain what you are trying to check for. Do you want to make sure that the model object has an ownedField with a text different from "Text"?
It may be the case that a more natural solution would be to auto-create a text field every time you create a WebList. To do this, you'd need to modify the generated code as discussed in [1].