# Task: Frontend developer feedback review

## Goal

Add the developer-facing global feedback review area.

## Feature Spec

- `docs/FEATURES/product-feedback.md`

## Scope

- Add routes restricted to the `Developer` role:
  - `/app/feedback`
  - `/app/feedback/:id`
- Add feature-owned views/stores/components under `frontend/src/features/feedback/`.
- Add a discoverable navigation entry for users with the `Developer` role.
- The list page is global and shows all reports by default, including final statuses.
- Support list filters:
  - type
  - status
  - tag
  - reporter
  - workspace context
  - date range
  - text search
- Support sorting by:
  - newest
  - oldest
  - last activity
- Detail page should show:
  - report details and captured metadata
  - reporter name/email
  - current URL/path link
  - screenshot preview
  - developer download/open-original screenshot action
  - comments
  - activity timeline
  - status updates
  - type updates
  - tag management with suggestions from previously used tags
- Allow developers to comment on any feedback report.
- Add English and French locale strings.

## Likely Files

- `frontend/src/router/router.js`
- `frontend/src/layouts/main/**`
- `frontend/src/features/feedback/**`
- `frontend/src/locales/en.json`
- `frontend/src/locales/fr.json`

## Notes

- Do not add assignment, priority, severity, duplicate linking, or private comments.
- Keep the review page operational and dense, not a Jira-style board.

## Validation

```bash
cd frontend
npm run build
```

## Done When

- [ ] Only users with the `Developer` role can access `/app/feedback`.
- [ ] Developers can list all feedback with required filters and sorting.
- [ ] Developers can open details and inspect metadata.
- [ ] Developers can preview and download/open screenshots.
- [ ] Developers can update type, status, and tags.
- [ ] Tag suggestions use previously used tags.
- [ ] Developers can comment.
- [ ] UI strings exist in English and French.
- [ ] Frontend build passes.
