# Undo Actions

## Objective

Let people take it back, instead of asking them if they're sure.

An undo affordance for destructive actions — usually a better answer than a confirmation dialog.

## Before You Begin

This feature is being added to an application that already exists and already
works. Do not scaffold a new project, and do not assume a blank slate.

Inspect the codebase first and establish:

- The existing application structure and where code of this kind already lives.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this feature needs to persist anything.
- The existing authentication and authorization system, if this feature is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this feature, extend it rather than replacing it.

## Implementation Instructions

1. Find destructive actions currently gated behind a confirmation dialog. Where the action can be made reversible, replace the dialog with undo.
2. Implement undo as a REAL reversal: soft-delete with a restore path, or a deferred commit. Do not fake it by hiding the row while the delete has already committed server-side.
3. Surface undo in a toast that lasts long enough to use — roughly 8–10 seconds, longer for bulk actions.
4. Support Cmd/Ctrl+Z for the most recent undoable action.

## UI and UX Requirements

Match the application's existing design system exactly. Reuse its components,
spacing, and typography. This feature should look like it was always there.

## Responsive Requirements

Works on mobile, tablet, and desktop. Touch targets are large enough to hit on a
phone, and nothing overflows horizontally at 320px.

## Accessibility Requirements

- Fully keyboard navigable.
- Correct semantic elements and ARIA roles.
- Visible focus states.
- Meets WCAG AA contrast.
- Dynamic changes are announced to screen readers.
- Respects prefers-reduced-motion.

## Edge Cases

- The user navigates away before undoing — the action must still commit correctly.
- Several undoable actions in quick succession — each needs its own undo, or a stack.
- The undo window expires while the toast is still visible — disable the button rather than failing silently.
- Undo fails server-side — say so; never pretend it worked.
- Cascading deletes are often irreversible. Do not offer undo where you cannot deliver it.

## Testing

Exercise the feature end to end in the running application. Cover every edge case
above, then run the existing test suite and confirm nothing regressed.

## Acceptance Criteria

- [ ] Undo genuinely restores state — verified server-side and after a refresh.
- [ ] The undo window is long enough to actually use.
- [ ] Cmd/Ctrl+Z triggers the last undo.
- [ ] Actions that cannot be reversed still use a confirmation dialog.
- [ ] A failed undo is reported, not swallowed.
- [ ] The feature matches the existing design system.
- [ ] No existing functionality is broken.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  feature fit. Adapt the feature to the app, not the app to the feature.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the feature end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the feature on mobile, tablet, and desktop widths.
5. Check keyboard navigation and focus handling.
6. Summarize what changed: files added, files modified, and anything you
   deliberately did differently because of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.