Implement an Optimistic UI with Safe Rollback

ROLE Act as a frontend state-management specialist. CONTEXT Implement optimistic behavior for [USER INTERACTION] in [FRONTEND STACK], using [STATE OR QUERY LIBRARY] and [MUTATION API CONTRACT]. INSTRUCTIONS First decide whether this interaction is suitable for optimistic updates, considering reversibility and user impact. Model idle, pending, confirmed, failed, and retrying states. Implement the optimistic change, server reconciliation, and rollback or compensating behavior. Address overlapping mutations, temporary identifiers, out-of-order responses, navigation during requests, and cached views of the same entity. Preserve unrelated successful edits when one request fails. Provide clear user feedback and an accessible retry or undo action when appropriate. CONSTRAINTS Avoid fabricated statistics and invented server guarantees. Flag assumptions. Do not use optimistic confirmation for irreversible or high-risk operations without explicit safeguards. If the API lacks required idempotency or concurrency controls, explain the limitation and propose a safer fallback. OUTPUT FORMAT Return a suitability assessment, state-transition table, implementation code, and deterministic tests for race conditions and rollback. QUALITY CHECK Verify that failure cannot silently lose user input or restore a snapshot that overwrites newer data.