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/supplemental-info-request-button.tsx

@@ -0,0 +1,102 @@
+'use client';
+
+import { useState } from 'react';
+import { useMutation } from '@tanstack/react-query';
+import { ClipboardCopy, Mail } from 'lucide-react';
+import { toast } from 'sonner';
+
+import { Button } from '@/components/ui/button';
+import { Card, CardContent } from '@/components/ui/card';
+import { Input } from '@/components/ui/input';
+import { apiFetch } from '@/lib/api/client';
+
+interface Props {
+  interestId: string;
+  /** Hide the button when EOI has already been sent / signed — at that
+   *  point the supplemental step is past its window. Caller passes the
+   *  current eoiStatus so we can render contextually. */
+  eoiStatus?: string | null;
+}
+
+interface IssueResponse {
+  data: {
+    link: string;
+    expiresAt: string;
+    emailSent: boolean;
+  };
+}
+
+/**
+ * One-click "Request more info" action. Fires the supplemental-info-
+ * request endpoint, which emails the client a public form pre-filled
+ * with what's on file. On success we display the generated link + a
+ * copy-to-clipboard button in case the rep needs to share it through
+ * another channel.
+ *
+ * Hidden once the EOI is `signed` — the supplemental step only makes
+ * sense before the signed EOI freezes the data into the contract path.
+ */
+export function SupplementalInfoRequestButton({ interestId, eoiStatus }: Props) {
+  const [link, setLink] = useState<string | null>(null);
+
+  const mutation = useMutation({
+    mutationFn: () =>
+      apiFetch<IssueResponse>(`/api/v1/interests/${interestId}/supplemental-info-request`, {
+        method: 'POST',
+      }),
+    onSuccess: (res) => {
+      setLink(res.data.link);
+      if (res.data.emailSent) {
+        toast.success('Email sent — link also shown below for sharing manually.');
+      } else {
+        toast.message('Link generated — no client email on file, share manually.');
+      }
+    },
+    onError: (err) =>
+      toast.error(err instanceof Error ? err.message : 'Failed to generate the form link.'),
+  });
+
+  if (eoiStatus === 'signed') return null;
+
+  return (
+    <Card>
+      <CardContent className="space-y-3 p-4">
+        <div className="space-y-1">
+          <h3 className="text-sm font-semibold">Need more info before drafting the EOI?</h3>
+          <p className="text-xs text-muted-foreground">
+            Email the client a one-time link to a public form pre-filled with what we have on file.
+            Submissions auto-update this client + interest record.
+          </p>
+        </div>
+        <div className="flex flex-wrap items-center gap-2">
+          <Button
+            type="button"
+            size="sm"
+            onClick={() => mutation.mutate()}
+            disabled={mutation.isPending}
+          >
+            <Mail className="mr-1.5 size-3.5" aria-hidden />
+            {mutation.isPending ? 'Generating…' : link ? 'Resend' : 'Request more info'}
+          </Button>
+          {link ? (
+            <>
+              <Input value={link} readOnly className="h-8 text-xs font-mono flex-1 min-w-[260px]" />
+              <Button
+                type="button"
+                size="sm"
+                variant="outline"
+                onClick={() => {
+                  void navigator.clipboard.writeText(link);
+                  toast.success('Link copied');
+                }}
+              >
+                <ClipboardCopy className="mr-1.5 size-3.5" aria-hidden />
+                Copy
+              </Button>
+            </>
+          ) : null}
+        </div>
+      </CardContent>
+    </Card>
+  );
+}