# Search History

## Objective

Let users rerun a recent search instead of retyping it.

A short list of the queries a user has run before, shown when the search field is focused and empty.

## 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. Store submitted query text per user, scoped to the workspace it was run in, with the time it was last used.
2. Normalize before storing — trim, collapse whitespace, fold case — and update the timestamp on a repeat rather than adding a second row.
3. Show the most recent handful when the search input is focused and empty, and rerun the query on selection.
4. Let the user remove a single entry and clear the whole history, and put clearing somewhere they can actually find it.
5. Do NOT store history for queries the user never submitted. This is a record of past searches, not of keystrokes.

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

- Query text is user data and can contain names, medical terms, or account numbers. Decide whether you are allowed to store it at all, and set a retention window.
- History must not leak across workspaces — a query run in one tenant must not appear while the user is in another.
- Cap the list. Unbounded history becomes a slow, useless scroll.
- Deleting the user's account must delete their history with it.
- A query that returned nothing is still worth keeping — the data may have changed since.
- Restoring a past query should restore the query text only, not silently reapply filters the user has since changed.

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

- [ ] Submitted queries are stored per user and per workspace.
- [ ] Repeated queries deduplicate on their normalized form and move to the top.
- [ ] Recent queries appear on focus and rerun on selection.
- [ ] Individual entries can be removed and the whole history cleared.
- [ ] The list is capped and old entries age out on a defined schedule.
- [ ] History is deleted when the account is deleted.
- [ ] 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.