CLOSED

[MattPua]

Problem

Users need embeddable product surfaces on dashboards — starting with error tracking issues. This PR adds the shared WidgetCard shell, catalog/registry UX, and dashboard scene glue for the error tracking widget.

This PR is 7/10 in the dashboard widgets Graphite stack.

Depends on: PR 6 (backend widget API + error tracking runner)

Changes

• WidgetCard compound components, DashboardWidgetItem, add-widget modal, catalog/registry
• Error tracking widget UI (component, edit modal, preview, stories, tests)
• Dashboard scene integration: dashboardLogic, DashboardItems, widgetFetchUtils
• Shared card chrome: CardTopHeadingRow, refresh button
• ErrorTrackingIssueList tweaks for dashboard embedding
• Session replay widget not included (PR 8)

How did you test this code?

• Agent: ran Jest tests for widget registry, WidgetCard, error tracking widget during development
• Feature remains behind dashboard widgets feature flag

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Publish to changelog?

no — still feature flagged

Docs update

skip-inkeep-docs

🤖 Agent context

• Frontend slice scoped to error tracking only so QA can validate one widget type end-to-end before session replay
• Uses generated API types from PR 6

[MattPua]

• CLOSED #60495 👈 (View in Graphite)
• feat(dashboards): add widget registry, run_widgets, and dashboard widget API (6/11) #60494 : 1 other dependent PR (#60523 )
• feat(dashboards): add concurrent indexes for dashboard widget tiles (5/11) #60493
• feat(dashboards): validate dashboard tile widget constraints (4/11) #60492
• feat(dashboards): extend dashboard tile exclusivity check for widgets (3/11) #60491
• feat(dashboards): add dashboard tile widget_id column (2/11) #60490
• feat(dashboards): add DashboardWidget model and table migration (1/11) #60489
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Prompt To Fix All With AI

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

---

### Issue 1 of 3
products/dashboards/frontend/widgets/registry.tsx:89-99
**Broken registry object — compilation failure**

Lines 95–98 are a leftover stub for the session-replay widget that was never completed. The entry is missing its key name and opening `{`, so the object literal has a mismatched closing `},` on line 98 that causes a JS/TS parse error. Additionally, `SessionReplayWidget` and `EditSessionReplayWidgetModal` are referenced but never imported, so this would also fail with "cannot find name" errors. The PR description says session replay is deferred to PR 8 — these lines need to be removed entirely before merging.

### Issue 2 of 3
products/dashboards/frontend/widget_types/catalog.ts:58-61
**Stray comma causes a syntax error**

Line 60 is a bare `,` with no property, producing an invalid object literal (`{a:1,,}` is not legal JS/TS). This appears to be a leftover placeholder for the session-replay catalog entry that should be removed.

```suggestion
        titleHref: urls.errorTracking(),
    },
} as const satisfies Record<string, DashboardWidgetCatalogEntry>
```

### Issue 3 of 3
frontend/src/scenes/dashboard/dashboardLogic.tsx:1834-1843
**`Public` placement now silently skips insight refresh**

Previously `handleDashboardLoadComplete` called `refreshDashboardItems` for every placement except `Export`; public-shared dashboards would therefore fetch fresh ClickHouse results. After this change, `DashboardPlacement.Public` is also excluded, so insight tiles on public/shared dashboards will stop showing live query results and fall back to whatever was embedded in the initial `loadDashboard` response. If the intent is to intentionally serve only cached data on public dashboards, this should be documented; otherwise it is a regression that will be invisible to the author but visible to all external viewers.

_{Reviews (1): Last reviewed commit: "feat(dashboards): add WidgetCard shell a..." | Re-trigger Greptile}

[greptile-apps]

Public placement now silently skips insight refresh

Previously handleDashboardLoadComplete called refreshDashboardItems for every placement except Export; public-shared dashboards would therefore fetch fresh ClickHouse results. After this change, DashboardPlacement.Public is also excluded, so insight tiles on public/shared dashboards will stop showing live query results and fall back to whatever was embedded in the initial loadDashboard response. If the intent is to intentionally serve only cached data on public dashboards, this should be documented; otherwise it is a regression that will be invisible to the author but visible to all external viewers.

Prompt To Fix With AI

This is a comment left during a code review.
Path: frontend/src/scenes/dashboard/dashboardLogic.tsx
Line: 1834-1843

Comment:
**`Public` placement now silently skips insight refresh**

Previously `handleDashboardLoadComplete` called `refreshDashboardItems` for every placement except `Export`; public-shared dashboards would therefore fetch fresh ClickHouse results. After this change, `DashboardPlacement.Public` is also excluded, so insight tiles on public/shared dashboards will stop showing live query results and fall back to whatever was embedded in the initial `loadDashboard` response. If the intent is to intentionally serve only cached data on public dashboards, this should be documented; otherwise it is a regression that will be invisible to the author but visible to all external viewers.

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

[MattPua]

Split into #60523 (WidgetCard shell) and #60524 (error tracking widget).