feat(errors): one triage hub, and an issue page that says where the error is

[Makisuo]

Why

/errors grouped error events by fingerprint and knew nothing about triage. /errors/issues listed the same fingerprints out of Postgres and knew nothing about volume. The investigation lived on a third route.

They were always the same objects — the warehouse groups by FingerprintHash, and error_issues is keyed on that same hash — so no single view could answer a triage question on its own, and the detail page you landed on read like a different product from the list you came from.

The list

One list, joined on the fingerprint. A row is an ErrorSignal: the issue row as the spine (it covers every fingerprint and carries the triage facts), warehouse volume and trend joined on, and one status slot resolved by precedence — open incident › live investigation › workflow state — replacing the four badge systems a row used to carry.

• Volume-ranked lists run warehouse-first; the other sorts run issue-first, because Postgres already orders them and the warehouse only knows about the window.
• The four KPI cards became one inline stat line. They took the top third of the page to say what fits on one line and pushed the list below the fold.
• Row sparklines are one static <svg> each, not a chart runtime — fifty rows would otherwise mean fifty of them.
• /errors/issues redirects, carrying its old workflowState tab across to the equivalent view.

The detail page

• Header. Five badges, a primary button and an overflow menu sat flat in one actions row, so nothing had precedence. Identity chips move into the title stack; the status collapses to the same chip the list uses; the actions slot keeps one labelled action and one menu.
• It never said where the error was. topFrame and fingerprintHash were on the wire and drawn nowhere — the only thing that ever read them was the investigation snapshot, so the page that exists to answer what broke and where briefed the agent with a stack frame it never showed you. Both are now the block under the title, and the exception message is promoted out of muted caption into the page's primary text.
• It had no time range. The endpoint takes start_time / end_time / bucket_seconds / sample_limit; the page called it with {} and then labelled a number "Events (window)" for a window nobody chose — reached from a list that does have a picker. Wired now: the chart, the samples and the count move together.
• Seven equal-weight sections in one stack become Overview / Occurrences / Activity, tabbed through ?tab=.
• Fix history was thrown away. regressionCount, lastRegressedAt, lastResolvedAt, resolvedVersions and snoozeUntil were decoded on every load and shown nowhere, so the page could not answer the question the workflow exists for: did the fix hold.

Also in here

• errorsSpark — bucketed counts for many fingerprints at once, pivoted server-side, plus an errorLabels sidebar facet.
• The occurrence chart is bars, tinted by severity. The series is a count per discrete bucket, and the old filled area interpolated straight through buckets with no errors, so silence read as steady traffic.
• One panel vocabulary across the page, the rail stops re-declaring the width and border PageLayout.RightSidebar already applies, and the activity timeline's ml-16/-left-16 magic-number pair is a real grid gutter.
• /errors/$errorType is deleted — unreachable since the list rewrite — along with the two atoms and the one query it was the last consumer of. getErrorDetailTraces stays; the dashboard builder still exposes it as a widget data source.

Verification

• bun typecheck clean; oxlint --quiet clean.
• @maple/web 195 files / 1727 tests green; @maple/query-engine and @maple/api green.
• Browser-verified against the local stack: the header chip, the time picker driving chart + samples + count together, the culprit block above the fold, ?tab= surviving reload, an alert-kind issue correctly losing its Occurrences tab, the rail, the breadcrumb, <lg layout and light mode.

Pre-existing failure, not from this branch: packages/domain openapi.test.ts and openapi-ios.test.ts fail on the two mobile_devices/{token}/live_activities/{incident_id} paths. mobile-devices.ts is untouched here and those endpoints landed in 27b62bc067 without the committed-paths assertion being updated.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[github-actions]

🍁 Maple PR preview

Note

Preview resources were removed when this pull request closed.

Final commit 2224e23 · View workflow run