# Restore Defaults

## Objective

Give people a way back when their settings have made a screen unusable.

A reset control on configurable screens that returns settings to the app's current defaults.

## 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 every screen users can configure: preferences, column layouts, dashboards, filters, notification settings.
2. Add a reset control and state its scope in the label. 'Reset this panel' and 'Reset all settings' are different promises.
3. Reapply the app's current defaults, computed at reset time. Do not restore whatever was saved when the account was created.
4. Confirm before any reset that discards work the user cannot easily rebuild, and name what is about to be lost.
5. Do NOT reset the whole settings object to wipe one section. Unrelated preferences stored alongside it must survive untouched.

## 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

- A reset must not clear authentication, connected integrations, or billing configuration, regardless of where they are stored.
- If defaults have changed since the user last saved, reset means today's defaults, not their historical value.
- Reset must be reflected immediately in the UI, not only after a reload.
- Where the reset is expensive to undo, offer undo for a short window instead of relying on the confirmation dialog alone.
- Per-workspace and per-account settings must reset independently. Resetting one workspace must not touch another.
- A reset while a save is in flight must not race the save and reinstate the old values.

## 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

- [ ] Every configurable screen has a reset control with an explicit scope in its label.
- [ ] Reset applies current defaults, not values captured at account creation.
- [ ] Settings outside the stated scope are unchanged after a reset.
- [ ] Destructive resets are confirmed and name what will be lost.
- [ ] The UI reflects the reset without a page reload.
- [ ] Credentials, integrations, and billing are never cleared by a reset.
- [ ] 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.