A card edit form that has two save endpoints — one saves only part of the data, leaving the record in a partially-updated state. Find which field is silently dropped.
Data inconsistency occurs when a save operation partially succeeds — updating some fields while silently ignoring others. The API returns 200 OK, but the persisted record doesn't reflect all the changes the user made. This is a common source of subtle bugs that only appear after editing.
| Bug | Save with buggy endpoint: name is updated but status field is ignored — record is inconsistent |
| Correct | Save with correct endpoint: both name and status are saved atomically |
| Read | Read current state at any time to verify what is actually persisted |