feat(berths): split Documents tab into Spec + Deal Documents

Berth detail page now has two tabs:
  - Spec: the existing versioned berth-spec PDF surface (current panel,
    version history, parser badge).
  - Deal Documents: NEW. Lists EOIs / contracts / etc. attached to
    interests currently linked to this berth via interest_berths.

New service helper listDealDocumentsForBerth joins documents →
interests → interest_berths with a port_id guard on both sides.
GET /api/v1/berths/[id]/deal-documents wraps it, gated on berths.view.

Read-only — title, type, status badge, and an Open link to the source
interest page. Edits / sends still happen on the interest's own page.
The Spec tab paragraph now points reps to the new Deal Documents tab
instead of telling them to navigate via Interests.

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

src/lib/services/documents.service.ts

@@ -8,7 +8,7 @@ import {
   documentWatchers,
   files,
 } from '@/lib/db/schema/documents';
-import { interests } from '@/lib/db/schema/interests';
+import { interests, interestBerths } from '@/lib/db/schema/interests';
 import { clients } from '@/lib/db/schema/clients';
 import { companies } from '@/lib/db/schema/companies';
 import { yachts } from '@/lib/db/schema/yachts';
@@ -213,6 +213,65 @@ export async function listDocuments(
   });
 }
 
+// ─── Deal docs for a berth ────────────────────────────────────────────────────
+
+export interface BerthDealDoc {
+  id: string;
+  title: string;
+  documentType: string;
+  status: string;
+  createdAt: Date;
+  interestId: string;
+}
+
+/**
+ * Documents attached to any interest currently linked to this berth via
+ * `interest_berths`. Used by the Deal Documents tab on the berth detail
+ * page so reps can see EOIs / contracts / etc. associated with active
+ * prospects on this slip without leaving the page.
+ *
+ * Read-only; visibility piggybacks on the interest tenancy (the
+ * permission-gate on the berth page guards entry, and we only return
+ * documents for interests in the same port). Edits / sends still happen
+ * from the interest's own page.
+ */
+export async function listDealDocumentsForBerth(
+  portId: string,
+  berthId: string,
+): Promise<BerthDealDoc[]> {
+  const rows = await db
+    .select({
+      id: documents.id,
+      title: documents.title,
+      documentType: documents.documentType,
+      status: documents.status,
+      createdAt: documents.createdAt,
+      interestId: documents.interestId,
+    })
+    .from(documents)
+    .innerJoin(interestBerths, eq(interestBerths.interestId, documents.interestId))
+    .innerJoin(interests, eq(interests.id, documents.interestId))
+    .where(
+      and(
+        eq(interestBerths.berthId, berthId),
+        eq(documents.portId, portId),
+        eq(interests.portId, portId),
+      ),
+    )
+    .orderBy(sql`${documents.createdAt} DESC`);
+
+  return rows
+    .filter((r): r is typeof r & { interestId: string } => Boolean(r.interestId))
+    .map((r) => ({
+      id: r.id,
+      title: r.title,
+      documentType: r.documentType,
+      status: r.status,
+      createdAt: r.createdAt,
+      interestId: r.interestId,
+    }));
+}
+
 // ─── Hub tab counts ───────────────────────────────────────────────────────────
 
 export interface HubTabCounts {