fix(audit): comprehensive 2026-05-15 audit fix wave + Documenso v2 polish

Bundles the prior session's 50-task fix sweep (Documenso v2 + EOI/signing-
progress redesign + env-to-admin migration + dev-mode banner) with the
2026-05-18 audit fix wave (3 CRITICAL, 14 HIGH, 28 MEDIUM, 6 LOW).

CRITICAL (3):
 - C-01 interest-berths INNER JOIN -> LEFT JOIN so hard-deleted berths
   no longer silently drop interest links
 - C-02 /setup added to PUBLIC_PATHS; fresh-deploy bootstrap loop fixed
 - C-03 generic PATCH /interests/[id] no longer accepts pipelineStage —
   callers must go through /stage with the override-guard chain

HIGH (14/15):
 - H-01 explicit ON DELETE on previously-implicit NO ACTION FKs across
   interests/documents/reservations/reminders/invoices (migration 0070)
 - H-02 login page reads ?redirect= param with same-origin guard
 - H-03 CRM invite token moves to URL fragment so it never lands in
   nginx access logs / Referer headers
 - H-04 Retry-After header on sign-in-by-identifier 429 (RFC 6585 §4)
 - H-05 toggleAccount writes an audit row
 - H-06 upsertSetting masks any value whose key ends with _encrypted
 - H-07 archiveClient cascade fires per-interest audit rows
 - H-08 createSalesTransporter applies SMTP_TIMEOUTS
 - H-09 AppShell stable children — viewport flip across breakpoint no
   longer destroys in-progress form drafts
 - H-10 portal documents page swaps Unicode glyph status icons for
   Lucide CheckCircle2/XCircle/Circle + aria-labels
 - H-12 list components swap alert(...) for toast.warning(...)
 - H-13 5 icon-only buttons gain aria-label
 - H-14 parseBody treats empty bodies as {}
 - H-15 admin layout renders a 403 panel instead of silent bounce
 - H-11 not applicable — mobile-search-overlay IS a mobile bottom-sheet

MEDIUM (28+):
 - M-MT01-05 defense-in-depth port_id/parent-id filters on UPDATE/DELETE
   WHEREs across custom-fields, notes (all 6 entity types x update +
   delete), client-contacts, yacht ownerClient lookup, webhook reads
 - M-D01 documents-hub realtime event-name typo (file:created -> uploaded)
 - M-EM01 portal-auth emails thread through portId
 - M-EM02 sendEmail accepts cc/bcc params
 - M-EM04 notification_digest catalog key
 - M-IN01 portal presigned download URLs use 4h TTL
 - M-IN02 OpenAI client lazy-instantiated
 - M-IN04 stale pdfme refs updated to pdf-lib AcroForm
 - M-IN05 umami.testConnection returns tagged union
 - M-L01 reservations tenure_type unified with berths
 - M-L02 report-generators canonicalize stage values
 - M-AU01 audit log placeholder copy fixed
 - M-AU04 outcome_set / outcome_cleared distinct audit verbs
 - M-NEW-2 activity feed entity name+type separator
 - M-R01 portal allowlist narrowed + portal_session backstop in proxy
 - M-SC02 companies archived partial index
 - M-SC04 audit_logs.searchText documented as DB-managed
 - M-S01 storage_s3_access_key_encrypted admin field
 - M-U01 audit log empty state uses <EmptyState>
 - M-U09 invoice delete dialog -> <AlertDialog>
 - M-U10 toast.success on ClientForm + InterestForm create/edit
 - M-U11 settings-form-card logo preview alt text
 - M-U14 mobile topbar title on clients/yachts/interests/berths
 - M-U15 Invoices in mobile More-sheet

LOW (6/8):
 - L-AU01 severity defaults for security-relevant verbs
 - L-AU02 +13 missing actions in admin audit filter
 - L-AU03 +7 missing entity types in admin audit filter
 - L-AU04 dead listAuditLogs stubbed
 - L-D02 CLAUDE.md Owner-wins chain tightened

Bonus — Document detail polish (#67 partial, 3/6 deliverables):
 - state-aware action button per signer
 - watcher Add UI with display-name resolution
 - cleanSignerName cleanup

Prior session work bundled in:
 - Documenso v2 webhook + envelope-ID normalization + sequential signing
 - SigningProgress UI redesign (avatars, per-signer state, timestamps)
 - env->admin settings registry + RegistryDrivenForm + encrypted creds
 - Embedded-signing card + Test connection + setup help
 - Dev-mode EMAIL_REDIRECT_TO banner
 - Pipeline rules admin page
 - Sales email config card
 - Audit log details Sheet
 - EOI tab: Finalising badge, absolute timestamps, sequential indicator
 - Notes pipeline_stage_at_creation (migration 0069)
 - Documenso numeric ID dual-key webhook (migration 0068)
 - Dimensions criterion copy (migration 0067)

Tests: 1374/1374 vitest pass. tsc clean. lint clean.

See docs/AUDIT-FIX-WAVE-2026-05-18.md for the full progress report and
the user-input items still pending.

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

src/lib/services/qualification.service.ts

@@ -214,6 +214,21 @@ export interface QualificationRow {
   confirmedAt: Date | null;
   confirmedBy: string | null;
   notes: string | null;
+  /**
+   * True when the criterion is automatically satisfied by data already on
+   * the interest (or a linked record). Surfaced to the UI so the checklist
+   * can render the criterion as ticked-by-the-system without needing an
+   * explicit `interest_qualifications` row. When both `autoSatisfied` and
+   * the explicit `confirmed` are true, either signal alone counts.
+   *
+   * Auto-satisfaction rules:
+   *   - `dimensions` → ticked when EITHER (a) the linked yacht has all
+   *     three dims (length/width/draft) OR (b) the interest itself has
+   *     desired-berth dims set. The "no yacht needed" case is the second
+   *     branch — a client buying a berth doesn't have to own a vessel,
+   *     they just have to know the berth size they want.
+   */
+  autoSatisfied: boolean;
 }
 
 /**
@@ -226,12 +241,38 @@ export async function listInterestQualifications(
   interestId: string,
   portId: string,
 ): Promise<QualificationRow[]> {
+  // Pull the interest row with the fields needed to derive auto-satisfaction —
+  // desired-berth dims (length/width/draft) plus a linked yacht if any. Cost
+  // is one extra column-select vs the previous columns:{id:true} probe, so
+  // negligible.
   const interest = await db.query.interests.findFirst({
     where: and(eq(interests.id, interestId), eq(interests.portId, portId)),
-    columns: { id: true },
+    columns: {
+      id: true,
+      yachtId: true,
+      desiredLengthFt: true,
+      desiredWidthFt: true,
+      desiredDraftFt: true,
+    },
   });
   if (!interest) throw new NotFoundError('Interest');
 
+  // Pull the linked yacht's dims when one is attached. Used by the
+  // `dimensions` criterion's auto-satisfaction rule (yacht-side branch).
+  let yachtDims: {
+    lengthFt: string | null;
+    widthFt: string | null;
+    draftFt: string | null;
+  } | null = null;
+  if (interest.yachtId) {
+    const { yachts } = await import('@/lib/db/schema/yachts');
+    const yacht = await db.query.yachts.findFirst({
+      where: eq(yachts.id, interest.yachtId),
+      columns: { lengthFt: true, widthFt: true, draftFt: true },
+    });
+    if (yacht) yachtDims = yacht;
+  }
+
   const criteria = await db
     .select()
     .from(qualificationCriteria)
@@ -246,20 +287,59 @@ export async function listInterestQualifications(
 
   return criteria.map((c) => {
     const s = stateByKey.get(c.key);
+    const autoSatisfied = computeAutoSatisfied(c.key, {
+      yachtDims,
+      desiredDims: {
+        lengthFt: interest.desiredLengthFt ?? null,
+        widthFt: interest.desiredWidthFt ?? null,
+        draftFt: interest.desiredDraftFt ?? null,
+      },
+    });
+    const explicit = s?.confirmed ?? false;
     return {
       key: c.key,
       label: c.label,
       description: c.description,
       enabled: c.enabled,
       displayOrder: c.displayOrder,
-      confirmed: s?.confirmed ?? false,
+      // Surface ticked state when either signal is true. Explicit confirmation
+      // still gets its confirmedAt/By stamps; auto-satisfied state leaves
+      // those null so the rep can see "this was system-derived, not an
+      // explicit sign-off".
+      confirmed: explicit || autoSatisfied,
       confirmedAt: s?.confirmedAt ?? null,
       confirmedBy: s?.confirmedBy ?? null,
       notes: s?.notes ?? null,
+      autoSatisfied,
     };
   });
 }
 
+/**
+ * Per-criterion derivation rules. Each key knows how to read the interest
+ * (and any linked records) and decide whether the criterion is satisfied
+ * without an explicit rep tick. Add new rules by branching on `key`.
+ */
+function computeAutoSatisfied(
+  key: string,
+  ctx: {
+    yachtDims: { lengthFt: string | null; widthFt: string | null; draftFt: string | null } | null;
+    desiredDims: { lengthFt: string | null; widthFt: string | null; draftFt: string | null };
+  },
+): boolean {
+  if (key === 'dimensions') {
+    const hasYachtDims =
+      !!ctx.yachtDims &&
+      !!ctx.yachtDims.lengthFt &&
+      !!ctx.yachtDims.widthFt &&
+      !!ctx.yachtDims.draftFt;
+    const hasDesiredDims =
+      !!ctx.desiredDims.lengthFt && !!ctx.desiredDims.widthFt && !!ctx.desiredDims.draftFt;
+    return hasYachtDims || hasDesiredDims;
+  }
+  return false;
+}
+
 /**
  * Upsert a single criterion's confirmed-state for an interest. Stamping the
  * server-side fields (confirmedBy / confirmedAt) makes the row a proper