SchemaViolation

One reason a value did not satisfy its schema.

message never carries a value read from the instance. A renderer turns a validation failure into the error it sends back to the agent, so anything quoted here travels back over the wire — and the values being checked are form fields. not(value: /form/cardNumber) putting a card number in an error message is not a hypothetical; it is a defect that reached review once already. What may be quoted is what the catalog said: an enum's options, a const, a minimum. Those are the renderer's own configuration, not the user's data.