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/interests.service.ts

@@ -10,6 +10,7 @@ import { companyMemberships } from '@/lib/db/schema/companies';
 import { tags } from '@/lib/db/schema/system';
 import { userProfiles } from '@/lib/db/schema/users';
 import { createAuditLog, type AuditMeta } from '@/lib/audit';
+import { activeInterestsWhere } from '@/lib/services/active-interest';
 import { getPortReminderConfig } from '@/lib/services/port-config';
 import { getSetting } from '@/lib/services/settings.service';
 import { NotFoundError, ConflictError, ValidationError } from '@/lib/errors';
@@ -193,7 +194,17 @@ export async function listInterestsForBoard(
   portId: string,
   filters: BoardFilters = {},
 ): Promise<{ data: BoardInterestRow[]; truncated: boolean; total: number }> {
-  const conditions = [eq(interests.portId, portId), isNull(interests.archivedAt)];
+  // Kanban shows only active deals — terminal (outcome-set) rows have
+  // their own /closed views. Pre-2026-05-14 this filter was just
+  // `archivedAt IS NULL`, which worked because setOutcome moved the
+  // stage to the 'completed' sentinel and the kanban only renders the
+  // 7-stage canon. With the sentinel-stage cleanup, terminal rows now
+  // keep their actual stage value, so we filter outcome explicitly.
+  const conditions = [
+    eq(interests.portId, portId),
+    isNull(interests.archivedAt),
+    isNull(interests.outcome),
+  ];
 
   if (filters.leadCategory) {
     conditions.push(eq(interests.leadCategory, filters.leadCategory));
@@ -1165,11 +1176,9 @@ export async function archiveInterest(id: string, portId: string, meta: AuditMet
           .leftJoin(clients, eq(interests.clientId, clients.id))
           .where(
             and(
+              activeInterestsWhere(portId),
               eq(interestBerths.berthId, primaryBerth.berthId),
-              eq(interests.portId, portId),
               ne(interests.id, id),
-              isNull(interests.archivedAt),
-              isNull(interests.outcome),
             ),
           )
           .orderBy(desc(interests.updatedAt))
@@ -1351,10 +1360,12 @@ export async function unlinkBerth(id: string, portId: string, meta: AuditMeta) {
 // ─── Stage Counts (for board) ────────────────────────────────────────────────
 
 export async function getInterestStageCounts(portId: string) {
+  // Kanban / board counts surface active deals only (no terminal
+  // outcomes) — terminal rows belong on a separate /closed surface.
   const rows = await db
     .select({ stage: interests.pipelineStage, count: sql<number>`count(*)::int` })
     .from(interests)
-    .where(and(eq(interests.portId, portId), isNull(interests.archivedAt)))
+    .where(activeInterestsWhere(portId))
     .groupBy(interests.pipelineStage);
   return Object.fromEntries(rows.map((r) => [r.stage, r.count]));
 }