Add Not actionable tab and route resolved PRs to Archive in inbox

[andrewm4894]

Problem

In the PostHog Code inbox, once a report's implementation PR is merged it transitioned to a terminal state and fell off every tab — there was no "Done"/archive surface to find shipped work again. The desktop app was also missing the Not actionable tab that PostHog/posthog has for auditing signal quality.

Why: Andy hit this directly — he shipped a couple of PRs and they "just disappeared" from the inbox with no Done tab to track them. Michael asked to replicate the Archived / Runs / Not actionable tab structure from PostHog/posthog here.

Changes

Brings the desktop inbox in line with the PostHog/posthog tab structure:

• Archive now lists resolved reports (merged implementation PR) alongside user-suppressed ones. Resolved reports appear for reference only — no Restore action. Merged PRs finally have a home.
• New Not actionable tab (staff-only) listing reports the agent judged not_actionable; they're pulled out of the Reports tab so they don't double-list.
• Adds resolved to the SignalReportStatus enum, labels, and status badge.
• Runs already matched posthog (Queued / Live / Recently finished) — left unchanged.

How did you test this?

• pnpm --filter @posthog/core --filter @posthog/ui typecheck — clean
• pnpm --filter @posthog/core test — 1667 passed (added cases for the new predicates: isDismissedReport incl. resolved, isResolvedReport, isNotActionableReport, isStaffOnlyInboxTab, not-actionable exclusion from Reports)
• pnpm --filter @posthog/ui test — 804 passed
• Regenerated the TanStack route tree for the new /code/inbox/not-actionable routes

Automatic notifications

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

---

Created with PostHog Code from a Slack thread

[greptile-apps]

Comments Outside Diff (1)

1. packages/ui/src/features/inbox/components/InboxReportDetailGate.tsx, line 87-95 (link)

   Stale-URL redirect misses resolved reports

   isSuppressed only checks status === "suppressed", so the boundary-redirect that guards against triage actions being shown on an out-of-pipeline report never fires for resolved reports. A user with a bookmarked or history URL for /code/inbox/reports/$reportId whose PR is later merged (transition to resolved) will land on the Reports detail view with the full triage affordances still rendered, rather than being redirected to /code/inbox/dismissed/$reportId.

   resolved was added to INBOX_EXCLUDED_STATUSES in this PR but the corresponding redirect guard was left unchanged. The existing comment on line 80-85 explicitly describes this redirect as protecting against "out-of-pipeline" reports — resolved is now squarely in that category.

_{Reviews (1): Last reviewed commit: "Add Not actionable tab and route resolve..." | Re-trigger Greptile}

[greptile-apps]

In-flight not_actionable reports double-list in Runs and Not actionable tabs

isNotActionableReport does not guard against isAgentRunReport(report). partitionRunsTabReports partitions directly on isQueuedRunReport/isLiveRunReport, bypassing this predicate entirely. A report that has actionability === "not_actionable" set while still in potential, candidate, in_progress, or pending_input status will therefore satisfy both predicates and appear in both the Runs tab and the Not actionable tab simultaneously.

isReportTabReport avoids this only because it calls isAgentRunReport before isNotActionableReport. Adding the same guard here would make the Not actionable predicate self-consistent, matching the existing pattern in isReportTabReport.