Library form fields
Design References
Contract
Field wraps a visible label, optional help text,
optional validation error, and one control body. Form controls should always be
labeled. Field-level errors are public-safe strings projected by the product
view model: they may name the field and required user action, but must not
include raw provider payloads, stack traces, SQL, tokens, credential values, or
private customer data. Provider/API modules return structured errors; the
product controller maps those errors into field text before rendering.
Fields do not own input type, form submission, provider validation, or resource payloads. They provide accessible structure around controls supplied through their body slot.
Consequence
Product modules can use consistent labels and errors without duplicating control-specific markup.