chore(style): codebase em-dash sweep + minor layout polish

Replaces every em-dash and en-dash with regular ASCII hyphens
across comments, JSX strings, and dev-facing logs. Mostly cosmetic
but stops the inconsistent mix that crept in over the last few
months (some files used em-dashes in comments, others didn't,
some used both).

Bundles two small dashboard-layout tweaks that touch a couple of
already-modified files:
- (dashboard)/layout.tsx main padding goes from p-6 to pt-3 px-6
  pb-6 so page content sits closer to the topbar.
- Sidebar now receives the ports list it needs for the footer
  port switcher.

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

src/components/interests/interest-detail-header.tsx

@@ -30,9 +30,9 @@ import { cn } from '@/lib/utils';
 
 const OUTCOME_BADGE: Record<string, { label: string; className: string }> = {
   won: { label: 'Won', className: 'bg-emerald-100 text-emerald-700' },
-  lost_other_marina: { label: 'Lost — other marina', className: 'bg-rose-100 text-rose-700' },
-  lost_unqualified: { label: 'Lost — unqualified', className: 'bg-rose-100 text-rose-700' },
-  lost_no_response: { label: 'Lost — no response', className: 'bg-rose-100 text-rose-700' },
+  lost_other_marina: { label: 'Lost - other marina', className: 'bg-rose-100 text-rose-700' },
+  lost_unqualified: { label: 'Lost - unqualified', className: 'bg-rose-100 text-rose-700' },
+  lost_no_response: { label: 'Lost - no response', className: 'bg-rose-100 text-rose-700' },
   cancelled: { label: 'Cancelled', className: 'bg-slate-200 text-slate-700' },
 };
 
@@ -69,7 +69,7 @@ interface InterestDetailHeaderProps {
     clientPrimaryPhone?: string | null;
     clientPrimaryPhoneE164?: string | null;
     /** Pending/snoozed reminders attached to this interest. Drives the
-     *  alarm-bell badge on the header — surfaces follow-ups so the rep
+     *  alarm-bell badge on the header - surfaces follow-ups so the rep
      *  doesn't have to remember to check /reminders. */
     activeReminderCount?: number;
     berthId: string | null;
@@ -107,7 +107,7 @@ export function InterestDetailHeader({ portSlug, interest }: InterestDetailHeade
   const outcomeBadge = resolveOutcomeBadge(interest.outcome);
   const isClosed = !!interest.outcome;
 
-  // Contact deep-links — resolved from the linked client's primary channels.
+  // Contact deep-links - resolved from the linked client's primary channels.
   // wa.me requires the digits-only E.164 number (no leading "+"); fall back to
   // stripping non-digits from the display value when the canonical form is
   // missing.
@@ -258,7 +258,7 @@ export function InterestDetailHeader({ portSlug, interest }: InterestDetailHeade
               </div>
             )}
 
-            {/* Contact deep-links — let the rep email / call / WhatsApp the
+            {/* Contact deep-links - let the rep email / call / WhatsApp the
                 client without leaving the interest workspace. Resolved from
                 the linked client's primary contact channels (server-side
                 fetch in getInterestById). */}
@@ -343,7 +343,7 @@ export function InterestDetailHeader({ portSlug, interest }: InterestDetailHeade
                       the won/lost meaning (green vs rose). Adding a "Won" /
                       "Lost" text label inline blew out the cluster width and
                       forced the Email/Call/WhatsApp action-chip row above to
-                      stack vertically — bad trade. From sm up, the full
+                      stack vertically - bad trade. From sm up, the full
                       "Mark won" / "Close as lost" labels read clearly. */}
                   <button
                     type="button"