# Feedback Widget

## Objective

Let anyone report a bug or send a comment from the page they are looking at.

An always-available launcher that opens a short feedback form and submits it with page context attached.

## 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. Put a single persistent launcher in one corner of the app and open a compact form in place. Do not route the user to a separate feedback page and lose the context they were about to describe.
2. Attach the current URL, the app version, the viewport size, the signed-in account, and a short trail of recent client errors automatically, so the reporter does not have to describe where they were.
3. Show the captured context to the user before they send it, in a collapsible section, and let them remove it. Silent collection of screen state is a trust problem.
4. Route submissions into the app's existing support, ticketing, or moderation destination rather than creating a second inbox nobody watches.
5. Do not require a category, a severity, or a rating before someone can type. Every required field ahead of the message box loses reports.

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

- Capture the current page and session context automatically at the moment the widget opens, not at submit, or a redirect during typing will file the report against the wrong screen.
- If submission fails, keep the typed draft in place with the error shown above it and let the user retry. Losing a bug report to a network blip is the one failure that guarantees it is never re-filed.
- Strip sensitive values out of the captured context before it leaves the browser: password fields, card numbers, tokens, and any field the app marks as private.
- The launcher must not sit on top of a chat bubble, a cookie banner, or a scroll-to-top control. Detect other fixed corner elements and offset, or place it where nothing else lives.
- Confirm receipt with a visible reference the user can quote, so the same issue is not sent four times while they wait.
- Anonymous feedback from public pages needs rate limiting and spam handling, or the inbox fills with automated submissions.
- The form must be reachable and dismissable by keyboard, with focus trapped while open and returned to the launcher on close.
- Very long pasted logs need a size limit that truncates with a note rather than rejecting the whole submission.

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

- [ ] The widget is reachable from every page of the app without navigating away.
- [ ] Page URL, app version, account, and recent client errors are attached automatically and shown to the user before sending.
- [ ] Sensitive field values are excluded from the captured context.
- [ ] A failed submission preserves the draft and offers a retry.
- [ ] Successful submissions return a visible reference and land in the app's existing support destination.
- [ ] Anonymous submissions are rate limited.
- [ ] The launcher does not overlap other fixed corner elements at any viewport width.
- [ ] 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.