feat(pipeline): 9→7 stage refactor + v1.1 hardening wave

Replaces the legacy 9-stage pipeline with 7 canonical stages
(enquiry → qualified → eoi → reservation → deposit_paid → contract →
nurturing) plus three doc sub-status columns (eoi_doc_status,
reservation_doc_status, contract_doc_status) that track sent/signed
within a single stage instead of branching it.

Schema (migration 0062):
- interests gains assigned_to, deposit_expected_amount/currency,
  three doc-status columns, two documenso-id columns, and
  date_reservation_signed.
- New tables: qualification_criteria (per-port admin-configurable),
  interest_qualifications (per-interest state), payments (deposit /
  balance / refund records keyed to interest + client).
- Default qualification criteria seeded for every existing port.
- Dummy-data UPDATEs collapse Sent/Signed pairs and 'completed' into
  the new stage + doc-status + outcome shape.

Migration 0063 adds interest_contact_log.voice_transcript and
template_used columns for v1.1-A/B (quick-template buttons + voice
transcription via Web Speech API).

v1.1 phase work bundled here:
- A/B: Quick-template buttons (Call / Visit / Email) + mic toggle on
       the contact-log compose dialog (useVoiceTranscription hook).
- C:   berth-rules-engine wraps state writes in pg_advisory_xact_lock
       with an idempotent re-read; emits rule_evaluated audit traces.
- D:   Documenso webhook: reservation/contract sub-status stamping
       moved out of the PDF-download try-block so a download failure
       no longer swallows the stamp. New integration test coverage.
- E:   /admin/qualification-criteria CRUD page + admin component.
- F:   default_new_interest_owner exposed in System Settings.
- G:   recentActivityCount + active_engagement deal-pulse signal
       surfaced as a chip on interests + hot-deals card.
- H:   interest_assigned notification on assignedTo change (skips
       self-assign, uses a dedupe key).

Plus the supporting components: AssignedToChip, DealPulseChip,
PaymentsSection, QualificationChecklist, MultiEoiChip,
SkipAheadBanner, WonStatusPanel, InterestBerthStatusBanner,
SupplementalInfoRequestButton, UserPicker.

Tests: 1370/1370 vitest pass (added deal-health unit suite +
expanded constants/validators/pipeline-transitions coverage). tsc
clean, eslint clean.

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

src/components/interests/deal-pulse-chip.tsx

@@ -0,0 +1,78 @@
+'use client';
+
+import { Activity } from 'lucide-react';
+
+import { Tooltip, TooltipContent, TooltipProvider, TooltipTrigger } from '@/components/ui/tooltip';
+import { computeDealHealth, type DealHealthInput } from '@/lib/services/deal-health';
+import { cn } from '@/lib/utils';
+
+const PULSE_TINT: Record<'cold' | 'warm' | 'hot', string> = {
+  hot: 'border-emerald-200 bg-emerald-50 text-emerald-800',
+  warm: 'border-amber-200 bg-amber-50 text-amber-800',
+  cold: 'border-rose-200 bg-rose-50 text-rose-800',
+};
+
+const PULSE_LABEL: Record<'cold' | 'warm' | 'hot', string> = {
+  hot: 'Hot',
+  warm: 'Warm',
+  cold: 'Cold',
+};
+
+/**
+ * Header chip surfacing the rule-based deal-health score. The tooltip
+ * exposes every signal that contributed to the score so the calculation is
+ * transparent — stakeholders averse to AI black boxes can read exactly
+ * which dates / stages drove the verdict.
+ */
+export function DealPulseChip({ interest }: { interest: DealHealthInput }) {
+  // Closed / archived deals don't get a pulse — UX would be confusing.
+  if (interest.archivedAt || interest.outcome) return null;
+
+  const health = computeDealHealth(interest);
+  const tint = PULSE_TINT[health.pulse];
+  const label = PULSE_LABEL[health.pulse];
+
+  return (
+    <TooltipProvider>
+      <Tooltip>
+        <TooltipTrigger asChild>
+          <span
+            className={cn(
+              'inline-flex items-center gap-1 rounded-full border px-2 py-0.5 text-[11px] font-medium cursor-help',
+              tint,
+            )}
+            aria-label={`Deal pulse: ${label}, score ${health.score}/100`}
+          >
+            <Activity className="size-3" aria-hidden />
+            {label} · {health.score}
+          </span>
+        </TooltipTrigger>
+        <TooltipContent side="bottom" className="max-w-xs">
+          <p className="font-semibold mb-1.5">
+            Deal pulse — {label} ({health.score}/100)
+          </p>
+          {health.signals.length === 0 ? (
+            <p className="text-xs">
+              Baseline score (50) — nothing notable yet. Log contact or progress the stage to move
+              the dial.
+            </p>
+          ) : (
+            <ul className="space-y-1 text-xs">
+              {health.signals.map((s) => (
+                <li key={s.id} className="flex gap-2">
+                  <span className={s.delta > 0 ? 'text-emerald-300' : 'text-rose-300'}>
+                    {s.delta > 0 ? `+${s.delta}` : s.delta}
+                  </span>
+                  <span>{s.detail}</span>
+                </li>
+              ))}
+            </ul>
+          )}
+          <p className="mt-2 text-[10px] opacity-70">
+            Rule-based. Every signal traces to a date or stage you can see — no AI.
+          </p>
+        </TooltipContent>
+      </Tooltip>
+    </TooltipProvider>
+  );
+}