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/components/dashboard/active-deals-tile.tsx

@@ -13,7 +13,8 @@ import { Skeleton } from '@/components/ui/skeleton';
 interface KpiResponse {
   totalClients: number;
   activeInterests: number;
-  pipelineValueUsd: number;
+  pipelineValue: number;
+  pipelineValueCurrency: string;
   occupancyRate: number;
 }
 

src/components/dashboard/kpi-cards.tsx

@@ -12,12 +12,11 @@ import { WidgetErrorBoundary } from './widget-error-boundary';
 interface KpiData {
   totalClients: number;
   activeInterests: number;
-  pipelineValueUsd: number;
+  pipelineValue: number;
+  pipelineValueCurrency: string;
   occupancyRate: number;
 }
 
-const formatUsd = (value: number) => formatCurrency(value, 'USD', { maxFractionDigits: 0 });
-
 function formatPercent(value: number): string {
   return `${value.toFixed(1)}%`;
 }
@@ -76,7 +75,11 @@ export function KpiCards() {
     },
     {
       label: 'Pipeline Value',
-      value: isError ? '-' : formatUsd(data?.pipelineValueUsd ?? 0),
+      value: isError
+        ? '-'
+        : formatCurrency(data?.pipelineValue ?? 0, data?.pipelineValueCurrency ?? 'USD', {
+            maxFractionDigits: 0,
+          }),
       accent: 'success',
     },
     {

src/components/dashboard/pipeline-value-tile.tsx

@@ -9,13 +9,15 @@ import { Skeleton } from '@/components/ui/skeleton';
 import { formatCurrency } from '@/lib/utils/currency';
 
 interface KpiResponse {
-  pipelineValueUsd: number;
+  pipelineValue: number;
+  pipelineValueCurrency: string;
 }
 
 /**
- * Total pipeline value for active interests, USD-denominated. Sourced
- * from the same KPIs endpoint as the active-deals tile so the two
- * share a cache entry and render in lockstep.
+ * Total pipeline value for active interests, converted to the port's
+ * default currency at display time. Sourced from the same KPIs endpoint
+ * as the active-deals tile so the two share a cache entry and render in
+ * lockstep.
  */
 export function PipelineValueTile() {
   const { data, isLoading } = useQuery<KpiResponse>({
@@ -42,9 +44,11 @@ export function PipelineValueTile() {
           ) : (
             <p
               className="truncate text-2xl font-bold leading-tight text-foreground"
-              title={formatCurrency(data?.pipelineValueUsd ?? 0, 'USD')}
+              title={formatCurrency(data?.pipelineValue ?? 0, data?.pipelineValueCurrency ?? 'USD')}
             >
-              {formatCurrency(data?.pipelineValueUsd ?? 0, 'USD', { maxFractionDigits: 0 })}
+              {formatCurrency(data?.pipelineValue ?? 0, data?.pipelineValueCurrency ?? 'USD', {
+                maxFractionDigits: 0,
+              })}
             </p>
           )}
         </div>