feat(reporting): money-math sweep — Step 1 PRE-DEPLOY-PLAN

Single coherent commit completing § 1.1 (hot-path correctness) plus
§ 1.1.4.5 (multi-berth EOI mooring fix). Numbers users see are now
self-consistent across dashboard / kanban / hot deals / PDF reports.

## Active-interest sweep (canonical predicate everywhere)

Routed every "active interest" filter through `activeInterestsWhere`
(commit b966d81 helper). The helper enforces port-scoping + archivedAt
IS NULL + outcome IS NULL — strict definition, won is closed.

Touched sites:
- src/lib/services/reminders.service.ts:digestPort — no longer fires
  reminders for won/lost/cancelled deals
- src/lib/services/berths.service.ts:getLatestInterestStageByBerth
- src/lib/services/client-archive-dossier.service.ts (next-in-line
  others lookup)
- src/lib/services/client-archive.service.ts (remaining-under-offer
  recount before flipping berth back to available)
- src/lib/services/client-restore.service.ts (yacht-usage check)
- src/lib/services/interests.service.ts:listInterestsForBoard +
  getInterestStageCounts + the "others on same berth" lookup —
  kanban / board now exclude terminal deals
- src/lib/services/report-generators.ts: fetchPipelineData,
  fetchRevenueData stage breakdowns, top-N interests

## Pipeline-value currency conversion

`getKpis()` now fetches the port's defaultCurrency from `ports` and
converts each berth's `priceCurrency`→port-default via
`currency.service`. Returns `pipelineValue` + `pipelineValueCurrency`
instead of the lying `pipelineValueUsd`. Missing rates fall through to
raw amount summing (so the tile still shows an approximate number) —
behind a follow-up to surface a "rates incomplete" indicator.

3 consumers updated: KpiCards, PipelineValueTile, ActiveDealsTile.

## Occupancy = sold only

Both the dashboard KPI tile and the revenue-report PDF occupancy data
now count only `berth.status='sold'`. `under_offer` is a hold, not
occupation. The analytics timeline switches from
`berth_reservations`-derived to a cumulative-won-deals derivation via
`interests.outcome='won' AND outcome_at::date <= day` — same source of
truth, historical shape preserved.

## Revenue PDF two-card layout

Added `totalForecast` + `pipelineWeights` to `RevenueData`. Summary
section now renders both:
- "Completed revenue (won)"  — money in the bank
- "Forecast revenue (pipeline-weighted)" — expected pipeline value

Pipeline weights resolve from `system_settings.pipeline_weights`
(per-port admin override) and fall back to STAGE_WEIGHTS defaults. PDF
and dashboard forecast tiles reconcile.

## Multi-berth EOI mooring (4.5)

Documenso `Berth Number` form field now carries the formatBerthRange
output for BOTH single- and multi-berth EOIs. Single-berth output is
byte-identical to the legacy primary-only path
(`formatBerthRange(['A1']) === 'A1'`). Multi-berth EOIs now render
the full range ("A1-A3, B5") in the existing field instead of being
silently dropped against a nonexistent `Berth Range` field.

Dropped:
- `'Berth Range'` from the Documenso formValues payload + TS type
- `setBerthRange()` helper from fill-eoi-form.ts (now redundant)
- The "missing Berth Range AcroForm field" warning log

Updated CLAUDE.md to reflect — no Documenso admin template change
needed.

## Tests

- Updated `documenso-payload.test.ts` — new fixture asserts
  formatBerthRange output flows into Berth Number; multi-berth case
  added.
- Updated `analytics-service.test.ts:computeOccupancyTimeline` —
  fixture creates a won interest instead of a reservation.
- Updated `alerts-engine.test.ts:interest.stale` — fixture stage
  switched from dead `'in_communication'` to canonical `'qualified'`.
- Updated `report-templates.test.tsx:revenue` — fixture carries
  `totalForecast` + `pipelineWeights` to match new RevenueData.

1373/1373 vitest pass. tsc + eslint clean.

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

src/lib/services/documenso-payload.ts

@@ -28,13 +28,16 @@ export interface DocumensoTemplatePayload {
     Length: string;
     Width: string;
     Draft: string;
-    'Berth Number': string;
     /**
-     * Compact range string of every berth in the interest's EOI bundle
-     * (e.g. "A1-A3, B5"). Empty when the bundle is empty. Multi-berth
-     * EOIs surface here; single-berth EOIs duplicate the primary mooring.
+     * Berth mooring as the human sees it. Single-berth EOI → the
+     * primary mooring (e.g. "A1"). Multi-berth EOI → the compact range
+     * (e.g. "A1-A3, B5") produced by `formatBerthRange()`. Single-
+     * berth output is byte-identical to the legacy primary-only path.
+     * 2026-05-14: collapsed the prior separate `Berth Range` form field
+     * into this one — the Documenso template has only `Berth Number`,
+     * and Documenso silently dropped unknown formValues.
      */
-    'Berth Range': string;
+    'Berth Number': string;
     Lease_10: boolean;
     Purchase: boolean;
   };
@@ -153,8 +156,11 @@ export function buildDocumensoPayload(
       Length: context.yacht?.lengthFt ?? '',
       Width: context.yacht?.widthFt ?? '',
       Draft: context.yacht?.draftFt ?? '',
-      'Berth Number': context.berth?.mooringNumber ?? '',
-      'Berth Range': context.eoiBerthRange,
+      // formatBerthRange(['A1']) === 'A1' — so single-berth EOIs render
+      // identically to the legacy primary-only flow; multi-berth EOIs
+      // now actually show the full range instead of just the primary
+      // mooring.
+      'Berth Number': context.eoiBerthRange || (context.berth?.mooringNumber ?? ''),
       Lease_10: false,
       Purchase: true,
     },