refactor(code): use status token for signal report list ordering

Author: Twixes

apps/code/src/renderer/features/inbox/utils/filterReports.test.ts

@@ -97,21 +97,21 @@ describe("filterReportsBySearch", () => {
 });
 
 describe("buildSignalReportListOrdering", () => {
-  it("puts pipeline first then descending field", () => {
+  it("puts status rank first then descending field", () => {
     expect(buildSignalReportListOrdering("total_weight", "desc")).toBe(
-      "pipeline,-total_weight",
+      "status,-total_weight",
     );
   });
 
-  it("puts pipeline first then ascending field", () => {
+  it("puts status rank first then ascending field", () => {
     expect(buildSignalReportListOrdering("created_at", "asc")).toBe(
-      "pipeline,created_at",
+      "status,created_at",
     );
   });
 
   it("works for signal_count", () => {
     expect(buildSignalReportListOrdering("signal_count", "desc")).toBe(
-      "pipeline,-signal_count",
+      "status,-signal_count",
     );
   });
 });

apps/code/src/renderer/features/inbox/utils/filterReports.ts

@@ -16,13 +16,13 @@ export function filterReportsBySearch(
 }
 
 /**
- * Comma-separated `ordering` for the signal report list API: stage (`pipeline`) then
- * the toolbar field (matches default inbox UX).
+ * Comma-separated `ordering` for the signal report list API: semantic `status` rank
+ * then the toolbar field (matches default inbox UX).
  */
 export function buildSignalReportListOrdering(
   field: SignalReportOrderingField,
   direction: "asc" | "desc",
 ): string {
   const secondary = direction === "desc" ? `-${field}` : field;
-  return `pipeline,${secondary}`;
+  return `status,${secondary}`;
 }

apps/code/src/shared/types.ts

@@ -236,9 +236,9 @@ export interface SignalReportsQueryParams {
   offset?: number;
   status?: CommaSeparatedSignalReportStatuses;
   /**
-   * Comma-separated sort keys (prefix `-` for descending). Use `pipeline` (or `stage`)
-   * for report stage rank; `signal_count`, `total_weight`, `created_at`, `updated_at`, `id`.
-   * Example: `pipeline,-total_weight`. Omit `pipeline` if you want a global sort only.
+   * Comma-separated sort keys (prefix `-` for descending). `status` is semantic stage
+   * rank (not lexicographic `status` column order). Also: `signal_count`, `total_weight`,
+   * `created_at`, `updated_at`, `id`. Example: `status,-total_weight`.
    */
   ordering?: string;
 }