fix(inbox): tiebreak priority sort by newest first

[rafaeelaudibert]

Summary

When sorting the inbox by priority, reports are now secondarily sorted by timestamp DESC (newest first) within each priority tier.

Priority is a coarse 5-bucket rank (P0–P4), so without a tiebreak, reports in the same tier came back in an arbitrary order. The ordering string sent to the signal report list API changes from status,priority → status,priority,-created_at.

Why this works

The backend (SignalReportViewSet) parses the ordering query param by splitting on commas and applying each clause in order, with created_at already in its ordering whitelist and id appended as a final tiebreak. So this is a frontend-only change — no API changes needed.

The tiebreak is scoped to the priority sort; the total_weight and created_at sorts are unchanged.

Testing

• Added a unit test asserting buildSignalReportListOrdering("priority", "asc") === "status,priority,-created_at".
• reportFiltering.test.ts passes (22 tests).

🤖 Generated with Claude Code

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit bf8860c.}

[greptile-apps]

Comments Outside Diff (1)

1. packages/core/src/inbox/reportFiltering.test.ts, line 101-113 (link)

   The new standalone it for the priority tiebreak breaks the team's preference for parameterised tests. It can be folded into the existing it.each table — and the "priority", "desc" direction (which produces "status,-priority,-created_at") is left untested entirely.

   Context Used: Do not attempt to comment on incorrect alphabetica... (source)

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: packages/core/src/inbox/reportFiltering.test.ts
   Line: 101-113
   
   Comment:
   The new standalone `it` for the priority tiebreak breaks the team's preference for parameterised tests. It can be folded into the existing `it.each` table — and the `"priority", "desc"` direction (which produces `"status,-priority,-created_at"`) is left untested entirely.
   
   
   
   **Context Used:** Do not attempt to comment on incorrect alphabetica... ([source](https://app.greptile.com/review/custom-context?memory=instruction-0))
   
   How can I resolve this? If you propose a fix, please make it concise.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Prompt To Fix All With AI

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

---

### Issue 1 of 1
packages/core/src/inbox/reportFiltering.test.ts:101-113
The new standalone `it` for the priority tiebreak breaks the team's preference for parameterised tests. It can be folded into the existing `it.each` table — and the `"priority", "desc"` direction (which produces `"status,-priority,-created_at"`) is left untested entirely.

```suggestion
  it.each([
    ["total_weight", "desc", "status,-total_weight"],
    ["created_at", "asc", "status,created_at"],
    ["signal_count", "desc", "status,-signal_count"],
    ["priority", "asc", "status,priority,-created_at"],
    ["priority", "desc", "status,-priority,-created_at"],
  ] as const)("orders by status then %s (%s)", (field, direction, expected) => {
    expect(buildSignalReportListOrdering(field, direction)).toBe(expected);
  });
```

_{Reviews (1): Last reviewed commit: "fix(inbox): tiebreak priority sort by ne..." | Re-trigger Greptile}