feat(inbox): Dismiss reports with feedback

[Twixes]

Problem

"Snooze", "Suppress" and "Delete" don't provide us with info on why the user got rid of the report – and it's hard to understand how to use them.

Changes

Replacing those three buttons with one clear "Dismiss", and a hidden dropdown for "Delete" - as well as "Reingest".

Basically replaces the old suppress-confirmation dialog and adds a "Dismiss" button (with thumbs-down icon) to both the inbox toolbar and the report detail pane header. Notes:

• When a single report is selected, the Dismiss button opens a dialog that captures why the report is being dismissed — single choice plus an optional note.
  - Multi-select (2+) keeps the previous bulk Snooze / Suppress buttons without the dialog. For mass management.
• Toolbar actions reorganized: Delete and dev-only Reingest moved into a ⋯ overflow menu, keeping the primary toolbar clean.

Implementation PR link now shown in the report detail header next to "Dismiss" (so they function as "here's the PR to review, accept or dismiss").

Backend prerequisite PR: PostHog/posthog#57768

---

Created with PostHog Code

[greptile-apps]

Comments Outside Diff (1)

1. apps/code/src/renderer/features/inbox/components/DismissReportDialog.tsx, line 165-168 (link)

   Misleading feedback copy for the snooze path

   The dialog body tells the user "Your feedback is saved on the report and helps the agents do better", but when "Already fixed" is selected the handler calls snoozeSelected() with no payload — and the API comment explicitly says dismissal_reason/dismissal_note are "Only honored when state == 'suppressed'". So the chosen reason and any note the user typed are silently discarded on this path. The copy should either be conditioned on the selected reason, or the "already fixed" path should be excluded from the blanket feedback promise.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: apps/code/src/renderer/features/inbox/components/DismissReportDialog.tsx
   Line: 165-168
   
   Comment:
   **Misleading feedback copy for the snooze path**
   
   The dialog body tells the user "Your feedback is saved on the report and helps the agents do better", but when "Already fixed" is selected the handler calls `snoozeSelected()` with no payload — and the API comment explicitly says `dismissal_reason`/`dismissal_note` are "Only honored when state == 'suppressed'". So the chosen reason and any note the user typed are silently discarded on this path. The copy should either be conditioned on the selected reason, or the "already fixed" path should be excluded from the blanket feedback promise.
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
apps/code/src/renderer/features/inbox/components/DismissReportDialog.tsx:165-168
**Misleading feedback copy for the snooze path**

The dialog body tells the user "Your feedback is saved on the report and helps the agents do better", but when "Already fixed" is selected the handler calls `snoozeSelected()` with no payload — and the API comment explicitly says `dismissal_reason`/`dismissal_note` are "Only honored when state == 'suppressed'". So the chosen reason and any note the user typed are silently discarded on this path. The copy should either be conditioned on the selected reason, or the "already fixed" path should be excluded from the blanket feedback promise.

### Issue 2 of 2
apps/code/src/renderer/features/inbox/hooks/useInboxBulkActions.ts:21-29
**Active-state reports can no longer be dismissed**

`"potential"`, `"candidate"`, and `"in_progress"` were removed from `suppressibleStatuses`, so the Dismiss button in `ReportDetailPane` will be permanently disabled for reports that are actively being processed. Previously a user could suppress a report at any active stage; now they must wait until the report reaches `failed`, `pending_input`, or `ready`. If that narrowing is intentional it should be documented (a comment on the set or a note in the tooltip), otherwise it will silently block early rejections.

_{Reviews (1): Last reviewed commit: "Simplify" | Re-trigger Greptile}

[greptile-apps]

Active-state reports can no longer be dismissed

"potential", "candidate", and "in_progress" were removed from suppressibleStatuses, so the Dismiss button in ReportDetailPane will be permanently disabled for reports that are actively being processed. Previously a user could suppress a report at any active stage; now they must wait until the report reaches failed, pending_input, or ready. If that narrowing is intentional it should be documented (a comment on the set or a note in the tooltip), otherwise it will silently block early rejections.

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/renderer/features/inbox/hooks/useInboxBulkActions.ts
Line: 21-29

Comment:
**Active-state reports can no longer be dismissed**

`"potential"`, `"candidate"`, and `"in_progress"` were removed from `suppressibleStatuses`, so the Dismiss button in `ReportDetailPane` will be permanently disabled for reports that are actively being processed. Previously a user could suppress a report at any active stage; now they must wait until the report reaches `failed`, `pending_input`, or `ready`. If that narrowing is intentional it should be documented (a comment on the set or a note in the tooltip), otherwise it will silently block early rejections.

How can I resolve this? If you propose a fix, please make it concise.