feat(expenses+interests): trip/event grouping (lightweight)

Per the trips/events design discussion: instead of building a full
events domain (table + CRUD UI + calendar) for the 6–12 yacht shows
a year, ship the cheap version that covers the actual asks.

Expenses — `tripLabel` free-text:
- New `expenses.trip_label` text column (migration 0039) + index for
  filter / autocomplete lookup.
- Validator: createExpenseShape + listExpensesSchema +
  exportExpensePdfSchema.filter all accept tripLabel.
- Service: createExpense + updateExpense persist; listExpenses filters;
  new `listTripLabels(portId, search?)` returns distinct values
  ordered by most-recent expenseDate so the autocomplete surfaces
  recently-used labels first.
- New `GET /api/v1/expenses/trip-labels` endpoint (gated by
  expenses.view) backs the autocomplete.
- Form dialog: native `<datalist>` powered by the autocomplete query
  so reps don't end up with "Palm Beach 2026" / "palm-beach 2026"
  fragmented across two PDF sections.
- Expense list: new "Trip" column (badge) + free-text filter.
- Detail page: trip label rendered alongside Category / Payer.
- PDF export: GroupBy gains 'trip'; filter.tripLabel narrows the
  export. Untagged rows fall under "(no trip)".
- Trim/normalize on write so " Palm Beach 2026 " === "Palm Beach 2026".

Interests — event tagging via existing tag system:
- Reps can tag interests with an event tag (e.g. "Palm Beach 2026")
  via the existing InlineTagEditor on the detail page; tags are
  port-scoped and reusable.
- Interest list now has a TagPicker filter rendered next to the
  FilterBar so reps can sort prospects by event attended ("show me
  every lead from Palm Beach"). Hidden 'relation'-typed
  FilterDefinition for tagIds wires URL round-trip + saved-views
  capture without rendering inside the FilterBar.
- FilterBar deserializer now handles `relation` types as comma-joined
  arrays on URL load.

Why a free-text trip label and not a trips table:
- 6–12 events/year doesn't justify a domain. The CRUD UI cost would
  be most of the engineering, and reps already have the events on
  their personal calendars.
- If usage proves demand for per-event ROI dashboards or richer
  attribution, promote to a real `trips` table later. Migration
  path: trip_label → tripId is a backfill+swap.

Test status: 1168/1168 vitest. tsc clean. Migration 0039 applied
in dev (also caught + fixed an unrelated audit-v3 follow-up: 0037
had `idx_br_interest` colliding with the existing
`berth_recommendations.idx_br_interest`; renamed to
`idx_brr_interest` / `idx_brr_contract_file`).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

src/lib/services/expense-pdf.service.ts

@@ -47,7 +47,7 @@ import { logger } from '@/lib/logger';
 
 // ─── Public options + result types ──────────────────────────────────────────
 
-export type GroupBy = 'none' | 'payer' | 'category' | 'date';
+export type GroupBy = 'none' | 'payer' | 'category' | 'date' | 'trip';
 export type PageFormat = 'A4' | 'Letter' | 'Legal';
 export type TargetCurrency = 'USD' | 'EUR';
 
@@ -84,6 +84,7 @@ export interface ExpensePdfArgs {
     category?: string | null;
     paymentStatus?: string | null;
     payer?: string | null;
+    tripLabel?: string | null;
     includeArchived?: boolean;
   };
   options: ExpensePdfOptions;
@@ -171,6 +172,8 @@ interface ExpenseRow {
    *  the table + a footnote at the bottom of the summary box. */
   noReceiptAcknowledged: boolean;
   paymentStatus: string | null;
+  /** Free-text trip / event label — drives `groupBy=trip` sectioning. */
+  tripLabel: string | null;
 }
 
 interface ProcessedExpense extends ExpenseRow {
@@ -328,6 +331,10 @@ function groupKey(row: ProcessedExpense, by: GroupBy): string {
       return row.payer ?? 'Unknown payer';
     case 'category':
       return row.category ?? 'Uncategorized';
+    case 'trip':
+      // Untagged rows go under "(no trip)" so they're still in the
+      // export, just collected at the bottom.
+      return row.tripLabel ?? '(no trip)';
     case 'date':
       return row.expenseDate.toISOString().slice(0, 10);
     default:
@@ -388,6 +395,7 @@ async function fetchExpenseRows(args: ExpensePdfArgs): Promise<ExpenseRow[]> {
     if (args.filter?.payer) conditions.push(eq(expenses.payer, args.filter.payer));
     if (args.filter?.paymentStatus)
       conditions.push(eq(expenses.paymentStatus, args.filter.paymentStatus));
+    if (args.filter?.tripLabel) conditions.push(eq(expenses.tripLabel, args.filter.tripLabel));
   }
 
   const rows = await db
@@ -404,6 +412,7 @@ async function fetchExpenseRows(args: ExpensePdfArgs): Promise<ExpenseRow[]> {
       description: expenses.description,
       receiptFileIds: expenses.receiptFileIds,
       noReceiptAcknowledged: expenses.noReceiptAcknowledged,
+      tripLabel: expenses.tripLabel,
       paymentStatus: expenses.paymentStatus,
     })
     .from(expenses)