A cross-layer workflow passes unit tests but breaks when client, API, and persistence state arrive in a different order. The affected area is account settings.
Repair the account settings input boundary implementation so it normalizes valid records and returns field-level errors for invalid ones.
Evidence
- Affected surface: Balanced full-stack / account settings.
- Observed failure family: validate a record batch.
- Scope policy: tenantId must equal tenant-primary.