feat(inbox): surface resolved reports in the Archive tab

[andrewm4894]

Problem

When a signal report is completed — its implementation PR merged — it transitions to the terminal resolved status and vanishes from the inbox entirely. There's no tab or filter that surfaces resolved reports, so there's no way to see or track completed work from the app.

This mirrors the same gap in the PostHog Cloud web inbox, fixed in PostHog/posthog#65040.

Changes

Resolved reports now appear in the existing Archive tab (route /code/inbox/dismissed) alongside dismissed (suppressed) ones — reusing the tab built for terminal reports rather than adding a new surface.

• Added resolved to the SignalReportStatus type (it didn't exist yet in this repo).
• Archive tab filter now fetches both terminal states (status=suppressed,resolved) instead of just suppressed; resolved is added to INBOX_EXCLUDED_STATUSES so it's treated as out-of-inbox everywhere else (counts, scope), and isDismissedReport now matches it.
• Resolved cards are reference-only: no Restore action (resolving is terminal — nothing to restore), and they show a green Resolved badge with a "Resolved {date}" label instead of the dismissal-reason chip.
• Detail view renders no actions for a resolved report, instead of the inapplicable Discuss / Create PR buttons.
• Added Resolved labels, accent color, and badge variant/tooltip for the new status; updated the Archive empty-state copy and the inbox CLAUDE.md.

This is desktop-only — the mobile inbox is intentionally out of scope.

No backend changes — the list API already accepts status=suppressed,resolved and serves these reports on the read paths the Archive tab uses.

How did you test this?

I'm an agent (Claude Code). I did not manually exercise the running desktop app. Verification was automated + by inspection:

• pnpm --filter @posthog/core test — all 1617 tests pass, including updated isDismissedReport / isExcludedFromInbox cases covering resolved.
• pnpm --filter @posthog/core typecheck and @posthog/ui typecheck — no errors in any touched file. (The repo's pnpm typecheck has pre-existing failures on main in unrelated files — canvas/WebsiteLayout.tsx, code-review/InteractiveFileDiff.tsx — confirmed present on a clean tree with these changes stashed; the pre-commit hook was bypassed for that reason.)
• biome check --write run on all changed files.

Manual smoke-testing of the Archive tab and a resolved report's detail view by a reviewer would be worthwhile.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit c099519.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5aae536d8c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[greptile-apps]

Comments Outside Diff (2)

1. packages/core/src/inbox/reportMembership.test.ts, line 163-177 (link)

   Inline multi-assertion instead of parameterised test

   The three isExcludedFromInbox true-cases are asserted sequentially inside a single it block. The isDismissedReport block above was correctly updated to it.each in this PR, but this sibling test was left non-parameterised. Per the codebase convention, prefer it.each here too so each status gets an independent test result in the runner output.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: packages/core/src/inbox/reportMembership.test.ts
   Line: 163-177
   
   Comment:
   **Inline multi-assertion instead of parameterised test**
   
   The three `isExcludedFromInbox` true-cases are asserted sequentially inside a single `it` block. The `isDismissedReport` block above was correctly updated to `it.each` in this PR, but this sibling test was left non-parameterised. Per the codebase convention, prefer `it.each` here too so each status gets an independent test result in the runner output.
   
   How can I resolve this? If you propose a fix, please make it concise.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

2. packages/core/src/inbox/statusLabels.ts, line 1-26 (link)

   Duplicated inboxStatusLabel — OnceAndOnlyOnce

   packages/core/src/inbox/statusLabels.ts and packages/core/src/inbox/reportPresentation.ts both export an identical inboxStatusLabel switch. This PR adds resolved to both, which is the second time the same new case has had to be applied to two files. Each future status addition will need to be kept in sync across both files. Consider consolidating into one source of truth (either remove statusLabels.ts and re-export from reportPresentation.ts, or move the function there and delete the duplicate).

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: packages/core/src/inbox/statusLabels.ts
   Line: 1-26
   
   Comment:
   **Duplicated `inboxStatusLabel` — OnceAndOnlyOnce**
   
   `packages/core/src/inbox/statusLabels.ts` and `packages/core/src/inbox/reportPresentation.ts` both export an identical `inboxStatusLabel` switch. This PR adds `resolved` to both, which is the second time the same new case has had to be applied to two files. Each future status addition will need to be kept in sync across both files. Consider consolidating into one source of truth (either remove `statusLabels.ts` and re-export from `reportPresentation.ts`, or move the function there and delete the duplicate).
   
   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
packages/core/src/inbox/reportMembership.test.ts:163-177
**Inline multi-assertion instead of parameterised test**

The three `isExcludedFromInbox` true-cases are asserted sequentially inside a single `it` block. The `isDismissedReport` block above was correctly updated to `it.each` in this PR, but this sibling test was left non-parameterised. Per the codebase convention, prefer `it.each` here too so each status gets an independent test result in the runner output.

### Issue 2 of 2
packages/core/src/inbox/statusLabels.ts:1-26
**Duplicated `inboxStatusLabel` — OnceAndOnlyOnce**

`packages/core/src/inbox/statusLabels.ts` and `packages/core/src/inbox/reportPresentation.ts` both export an identical `inboxStatusLabel` switch. This PR adds `resolved` to both, which is the second time the same new case has had to be applied to two files. Each future status addition will need to be kept in sync across both files. Consider consolidating into one source of truth (either remove `statusLabels.ts` and re-export from `reportPresentation.ts`, or move the function there and delete the duplicate).

_{Reviews (1): Last reviewed commit: "feat(inbox): surface resolved reports in..." | Re-trigger Greptile}

[github-actions]

All three substantive review bugs (routing bounce for resolved reports, stale archive data, status-prefixed ordering across two terminal statuses) are addressed in the current diff. The change is well-structured, architecturally correct, and the hook signature already supports the added refetch option.

New commits pushed (delta classified label_absent) — stamphog approval dismissed; re-review running automatically.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c099519338

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[stamphog]

The Codex bot raised a valid concern at the current head about DismissedReportDetail.tsx unconditionally rendering RestoreReportButton for resolved reports. The PR attempted to fix this in ReportDetailActions.tsx (returns null for resolved), but DismissedReportDetail.tsx renders its own inline RestoreReportButton directly — it never calls ReportDetailActions. The fix was applied to the wrong component, so a resolved report opened in the archive detail view still shows a "Restore" button; clicking it hits the status !== "suppressed" guard in useInboxRestoreReport and surfaces the misleading toast "This report is no longer archived."

[github-actions]

All prior review concerns are resolved in the current diff: routing uses isDismissedReport for both terminal statuses, DismissedReportDetail gates RestoreReportButton on canRestore, archive ordering drops the status prefix, and a refetch interval is added for server-side transitions. No showstoppers.