Redirect resolved reports to Archive and hide their Restore action

Adding `resolved` to INBOX_EXCLUDED_STATUSES left two gaps for resolved (merged-PR) reports:

- InboxReportDetailGate's stale-URL redirect only checked `suppressed`, so a resolved report opened at a /pulls, /reports, or /runs URL rendered full triage actions instead of redirecting to Archive. Switch to the isDismissedReport predicate (suppressed OR resolved) so both terminal states redirect symmetrically.
- DismissedReportDetail always rendered Restore; resolved reports are terminal, so gate it with isResolvedReport — matching the list-card behavior.

Per Greptile review.

Generated-By: PostHog Code
Task-Id: 3a7dec81-6f1d-425a-a7cb-f468c36b3ec7

Author: andrewm4894

packages/ui/src/features/inbox/components/DismissedReportDetail.tsx

@@ -4,6 +4,7 @@ import {
   FileTextIcon,
   MagnifyingGlassIcon,
 } from "@phosphor-icons/react";
+import { isResolvedReport } from "@posthog/core/inbox/reportMembership";
 import { Button } from "@posthog/quill";
 import type { SignalReport } from "@posthog/shared/types";
 import { InboxDetailFrame } from "@posthog/ui/features/inbox/components/InboxDetailFrame";
@@ -19,14 +20,15 @@ interface DismissedReportDetailProps {
 }
 
 /**
- * Detail view for an archived (suppressed) report. Read-only re-read of what the
- * report was — summary + evidence — with a single Restore action. No triage
- * affordances (archive, discuss, create PR, reviewers): the report is out of the
- * pipeline until it's restored.
+ * Detail view for an archived report. Read-only re-read of what the report was —
+ * summary + evidence. Suppressed reports get a single Restore action; resolved
+ * reports (their PR merged) are terminal and shown for reference only, with no
+ * Restore. No triage affordances (archive, discuss, create PR, reviewers): the
+ * report is out of the pipeline.
  *
  * The gate keeps reports on the route that matches their status: a no-longer-
- * suppressed report opened here (stale URL or restored elsewhere) is redirected
- * to its current home, so this content only ever renders a suppressed report.
+ * archived report opened here (stale URL or restored elsewhere) is redirected to
+ * its current home, so this content only ever renders an archived report.
  */
 export function DismissedReportDetail({
   reportId,
@@ -55,7 +57,8 @@ function DismissedReportDetailContent({ report }: { report: SignalReport }) {
       showDismiss={false}
       primaryAction={
         <>
-          <RestoreReportButton report={report} />
+          {/* Resolved reports are terminal (PR merged) — no Restore. */}
+          {!isResolvedReport(report) && <RestoreReportButton report={report} />}
           <Button
             type="button"
             variant="outline"

packages/ui/src/features/inbox/components/InboxReportDetailGate.tsx

@@ -1,4 +1,5 @@
 import {
+  isDismissedReport,
   isNotActionableReport,
   isPullRequestReport,
   isReportTabReport,
@@ -75,21 +76,22 @@ export function InboxReportDetailGate({
 
   // Keep the report on the route that matches its status. A status↔route mismatch
   // happens when a URL goes stale — browser history, a bookmark, a copied deep
-  // link, or a status change in another session. A suppressed report reached via a
-  // /pulls, /reports, or /runs URL would otherwise render that tab's full triage
-  // actions (archive, discuss, create PR) on an out-of-pipeline report; a restored
-  // report reached via /dismissed would offer Restore and silently re-queue it
-  // (READY/RESOLVED → POTENTIAL is an allowed server-side transition). Redirect
-  // across that dismissed↔pipeline boundary, gated on a settled fetch so we act on
-  // the confirmed status rather than a pre-change cache snapshot (the detail query
+  // link, or a status change in another session. An archived report (suppressed,
+  // or resolved once its PR merges) reached via a /pulls, /reports, or /runs URL
+  // would otherwise render that tab's full triage actions (archive, discuss,
+  // create PR) on an out-of-pipeline report; a restored report reached via
+  // /dismissed would offer Restore and silently re-queue it (READY/RESOLVED →
+  // POTENTIAL is an allowed server-side transition). Redirect across that
+  // archive↔pipeline boundary, gated on a settled fetch so we act on the
+  // confirmed status rather than a pre-change cache snapshot (the detail query
   // forces a fresh fetch on mount via `initialDataUpdatedAt: 0`).
   const onDismissedRoute = backTo === "/code/inbox/dismissed";
-  const isSuppressed = resolvedReport?.status === "suppressed";
+  const isArchived = resolvedReport ? isDismissedReport(resolvedReport) : false;
   let redirectTo: InboxDetailRoute | null = null;
   if (resolvedReport && !isFetching) {
-    if (isSuppressed && !onDismissedRoute) {
+    if (isArchived && !onDismissedRoute) {
       redirectTo = "/code/inbox/dismissed/$reportId";
-    } else if (!isSuppressed && onDismissedRoute) {
+    } else if (!isArchived && onDismissedRoute) {
       redirectTo = nonSuppressedDetailRoute(resolvedReport);
     }
   }