cesnimda
1.3 KiB
Settings privacy read and save recovery
Reused runtime e8e7d83958587e8b5a4b93d03d3e736896df5a48. No application source changed. The existing privacy form shows a loading state and no switches while its first read is held. A fixture 503 shows an unavailable message. Keyboard retry restores the named control group and its saved value.
The user switches off AI and presses Save. The intercepted preference update carries only the two current preference fields and receives a fixture 409. The form shows the error and preserves the unsaved draft. Keyboard discard restores the loaded setting and clears the warning, without another request.
Passed 36 configurations at nine widths across EN/NB and both themes. The 180 captured states had zero axe violations, page exceptions, unexpected writes or proposals. Each configuration made exactly one intercepted rejected write. There were 36 unavailable company reads and one intentional initial privacy 503 per configuration. The pilot overlaps the full matrix and is not added to its totals.
This fixture qualifies presentation of a rejected save. It does not establish a server-side optimistic concurrency contract. No setting was saved, no entitlement changed and no model ran. Other Settings transient, backup/export and native checks remain separate.