feat: round 2 — stage prompts, berth header, EOI inline edit, measurement units

Berth surfaces
- New compact mooring-chip header (colored plate + status pill, dock-label
  in tooltip) replaces the redundant "Berth B1 / Sold / B DOCK" stack
- Berth list gains a "Latest deal stage" column showing the most-advanced
  pipeline stage of any active linked interest (server-aggregated, ranks by
  PIPELINE_STAGES index)
- "Linked prospect" Select on the status-change dialog rebuilt as a Command
  combobox: search, recent-first sort, stage-coloured pills

Pipeline UX
- Reverting an interest to Open with linked berths now prompts: keep the
  links, unlink and reset, or cancel. Silent when no berths are linked
- Activity feed + entity-activity feed normalise enum field values via
  STAGE_LABELS / formatSource: "deposit_10pct → contract_sent" reads as
  "10% Deposit → Contract Sent"

EOI generate dialog
- Inline-editable rows for client name, nationality (country combobox), and
  yacht name — pencil affordance saves directly via clients/yachts PATCH
- Replaces the single "Edit on client's page" link with two contextual links
  framed by short copy explaining what's inline vs what needs the canonical
  page
- Backend EoiContext now includes client.id + yacht.id so the dialog can
  PATCH without an extra round-trip

Company form
- New "Connections" section lets the rep attach members (clients) and yachts
  during create. Yacht attach uses the existing transfer endpoint so audit
  log + ownership history capture the change
- Inline "+ New client" / "+ New yacht" buttons open the canonical forms
  stacked over the company sheet
- After save, the form chains to a yacht pull-in prompt (if any attached
  client owns yachts not yet linked) and an optional "Create interest" step
  pre-filled with the first attached client

Admin
- /admin landing gains a searchable index — typed query flattens groups into
  a result list matching label + description + group title
- "Documenso & EOI" card relabelled to "EOI signing service" (consistent
  with the user-facing language rename from round 1)

Measurement units (migration 0053)
- interests gains desired_*_m columns + desired_*_unit discriminators so
  the rep's literal entry (ft OR m) is preserved verbatim instead of being
  reconstructed from a single canonical column on every render
- yachts + berths gain matching *_unit columns alongside their existing
  ft + m pairs; defaults to 'ft' so legacy rows still render normally
- Interest form POST/PATCH now sends both ft + m + unit; computed m is
  derived from the ft canonical to keep the recommender SQL unchanged

Misc
- Active-deals tile + topbar type their Link href as `Route` instead of `any`
- Unused REPORT_TYPE_LABELS const dropped from generate-report-form
- Test fixtures (fill-eoi-form, documenso-payload, public-berths) updated
  to include the new id + unit fields on the EoiContext / Berth shapes

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

src/lib/db/migrations/0053_measurement_units.sql

@@ -0,0 +1,64 @@
+-- 0053 — Measurement units (entry-unit tracking + interest dual-store)
+--
+-- Problem: dimensions on interests/yachts/berths are stored in ft OR m, but
+-- the CRM blindly converts between them on display. When a rep edits the
+-- converted side, the original entered value drifts by floating-point error
+-- (e.g. 18.29m → 60.039ft → back to 18.297m).
+--
+-- Fix: every dimension gets two pieces of info — a value column per unit
+-- (so we can render the user's literal entry verbatim) AND a small
+-- discriminator column (`*_unit`) saying which side the user originally
+-- typed in. The form prefers the entered unit when displaying; the other
+-- unit is computed only for export pathways (EOI PDF, recommender).
+--
+-- Interests previously only stored ft; this migration adds *_m columns
+-- alongside. Yachts + berths already store both; only the discriminator
+-- needs to be added.
+--
+-- Backfill: existing rows are flagged as `ft`-entered since that was the
+-- only way to enter them before this change. m-side values get computed
+-- (only for interests where they were null) via `* 0.3048`.
+
+-- ── interests: dual-store + discriminator ─────────────────────────────────
+ALTER TABLE interests
+  ADD COLUMN IF NOT EXISTS desired_length_m numeric,
+  ADD COLUMN IF NOT EXISTS desired_width_m  numeric,
+  ADD COLUMN IF NOT EXISTS desired_draft_m  numeric,
+  ADD COLUMN IF NOT EXISTS desired_length_unit text NOT NULL DEFAULT 'ft',
+  ADD COLUMN IF NOT EXISTS desired_width_unit  text NOT NULL DEFAULT 'ft',
+  ADD COLUMN IF NOT EXISTS desired_draft_unit  text NOT NULL DEFAULT 'ft';
+
+UPDATE interests SET desired_length_m = ROUND(desired_length_ft * 0.3048::numeric, 2) WHERE desired_length_m IS NULL AND desired_length_ft IS NOT NULL;
+UPDATE interests SET desired_width_m  = ROUND(desired_width_ft  * 0.3048::numeric, 2) WHERE desired_width_m  IS NULL AND desired_width_ft  IS NOT NULL;
+UPDATE interests SET desired_draft_m  = ROUND(desired_draft_ft  * 0.3048::numeric, 2) WHERE desired_draft_m  IS NULL AND desired_draft_ft  IS NOT NULL;
+
+-- ── yachts: discriminator only ────────────────────────────────────────────
+ALTER TABLE yachts
+  ADD COLUMN IF NOT EXISTS length_unit text NOT NULL DEFAULT 'ft',
+  ADD COLUMN IF NOT EXISTS width_unit  text NOT NULL DEFAULT 'ft',
+  ADD COLUMN IF NOT EXISTS draft_unit  text NOT NULL DEFAULT 'ft';
+
+-- ── berths: discriminator only (multi-axis) ───────────────────────────────
+ALTER TABLE berths
+  ADD COLUMN IF NOT EXISTS length_unit         text NOT NULL DEFAULT 'ft',
+  ADD COLUMN IF NOT EXISTS width_unit          text NOT NULL DEFAULT 'ft',
+  ADD COLUMN IF NOT EXISTS draft_unit          text NOT NULL DEFAULT 'ft',
+  ADD COLUMN IF NOT EXISTS nominal_boat_size_unit text NOT NULL DEFAULT 'ft',
+  ADD COLUMN IF NOT EXISTS water_depth_unit    text NOT NULL DEFAULT 'ft';
+
+-- Constrain to known values. (Cheaper than a separate enum type for two
+-- string values, and easier to drop if we ever add a third unit.)
+ALTER TABLE interests
+  ADD CONSTRAINT chk_interest_desired_length_unit CHECK (desired_length_unit IN ('ft','m')),
+  ADD CONSTRAINT chk_interest_desired_width_unit  CHECK (desired_width_unit  IN ('ft','m')),
+  ADD CONSTRAINT chk_interest_desired_draft_unit  CHECK (desired_draft_unit  IN ('ft','m'));
+ALTER TABLE yachts
+  ADD CONSTRAINT chk_yacht_length_unit CHECK (length_unit IN ('ft','m')),
+  ADD CONSTRAINT chk_yacht_width_unit  CHECK (width_unit  IN ('ft','m')),
+  ADD CONSTRAINT chk_yacht_draft_unit  CHECK (draft_unit  IN ('ft','m'));
+ALTER TABLE berths
+  ADD CONSTRAINT chk_berth_length_unit            CHECK (length_unit            IN ('ft','m')),
+  ADD CONSTRAINT chk_berth_width_unit             CHECK (width_unit             IN ('ft','m')),
+  ADD CONSTRAINT chk_berth_draft_unit             CHECK (draft_unit             IN ('ft','m')),
+  ADD CONSTRAINT chk_berth_nominal_boat_size_unit CHECK (nominal_boat_size_unit IN ('ft','m')),
+  ADD CONSTRAINT chk_berth_water_depth_unit       CHECK (water_depth_unit       IN ('ft','m'));