feat(inbox): Show signals report data in the detail pane#1552
Merged
sortafreel merged 6 commits intomainfrom Apr 8, 2026
Merged
feat(inbox): Show signals report data in the detail pane#1552sortafreel merged 6 commits intomainfrom
sortafreel merged 6 commits intomainfrom
Conversation
- Add Priority and Actionability detail rows with collapsible "Why?" explanations from priority_judgment and actionability_judgment artefacts - Add 'already addressed' warning banner driven by report or judgment - Pass per-signal SignalFinding (verified flag, code paths, data queried) to SignalCard so the detail pane can surface research evidence - Add VerificationBadge to SignalCardHeader and CodePaths/DataQueried collapsibles inside each source-specific signal card variant - Add SignalReportActionabilityBadge alongside the existing priority/ status chips on the inbox list card - Restructure the evidence section in ReportDetailPane to surface loading and unavailable states (forbidden, not_found, invalid_payload, request_failed) so the user gets feedback when artefacts can't load - Add typed normalizers for priority_judgment, actionability_judgment and signal_finding artefacts in posthogClient - Drop the legacy JudgmentBadges component, which used an outdated Record<string, unknown> shape that no longer matches the typed artefact schema in shared/types Squashed-from: signals/new-report-data-in-inbox-ui-backup Originally PR #1428
# Conflicts: # apps/code/src/renderer/api/posthogClient.ts # apps/code/src/renderer/features/inbox/components/list/ReportCard.tsx
…ta-in-inbox-ui-v2 # Conflicts: # apps/code/src/renderer/api/posthogClient.ts
…ta-in-inbox-ui-v2 # Conflicts: # apps/code/src/renderer/api/posthogClient.ts
adboio
reviewed
Apr 8, 2026
Contributor
adboio
left a comment
adboio
left a comment
There was a problem hiding this comment.
@sortafreel do you mind sharing screenshot(s) of the affected areas so i know specifically which pieces to review?
ty!!! ❤️
sortafreel
changed the title
sortafreel
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
We get plenty of data from the Signals report to:
But we don't show them in the UI
Changes
Surfaces researched signals data — priority, actionability, evidence — directly in the inbox detail pane, replacing the placeholder badges with typed, explainable judgments.
priority_judgment/actionability_judgmentartefactsreport.already_addressedor the actionability judgment's flagSignalCards now receive aSignalFindingand surface aVerified/Unverifiedbadge plus collapsibleRelevant codeandData queriedsectionsSignalReportActionabilityBadgechip alongside the existing status / priority chipspriority_judgment,actionability_judgmentandsignal_findingartefacts inposthogClientNotes
main, squashed to a single commit, and rebuilt against the newinbox/components/{detail,list,utils}layout from feat(sig): break inbox into some components #1505.How did you test this?