chore(autonomous-session): consolidate uncommitted work from prior session

Bundles the prior autonomous-session output that was sitting unstaged:

- Em-dash sweep across src/ + tests/ (en-dash/em-dash to hyphen, ~2280 instances)
- country-flag-icons rollout (CountryFlag component, replaces emoji glyphs that
  never rendered on Windows; lazy-loads the 3x2 SVG index as a single chunk
  after the per-subpath dynamic-import approach silently failed in webpack)
- Admin IA Phase 1+2: 7-domain regroup, 41 to 38 pages, /admin/berths index,
  redirects (ocr to ai, reports to dashboard, invitations to users),
  docs/admin-ia-proposal.md
- Per-template email tester (registry + endpoint + UI on Email admin page)
- Cancel-document mode picker (delete-from-Documenso vs keep-for-audit)
- Dashboard PDF report: 25 widgets, SVG charts, date-range picker, 11 resolvers
- Customize-widgets per-region sortables at xl+ (charts/rails/feed); single
  flat sortable below xl when the layout stacks; per-viewport saved orders
- Audit doc updates capturing each shipped item
- Lint fixes: react-compiler immutability in DonutChart (reduce instead of
  let-reassign), set-state-in-effect disables in CountryFlag and
  UploadForSigning preview-bytes effect, unused 'confirm' destructures in
  interest contract + reservation tabs, unescaped apostrophe in test-template
  card copy

src/hooks/use-dashboard-integrations.ts

@@ -6,12 +6,12 @@ import type { WidgetIntegration } from '@/components/dashboard/widget-registry';
 /**
  * Returns availability for each external integration a dashboard widget
  * might depend on. Lets the widget picker hide options whose underlying
- * service isn't wired up — so reps don't enable widgets that'd render
+ * service isn't wired up - so reps don't enable widgets that'd render
  * nothing.
  *
  * Add a new integration by:
  *   1. Extending `WidgetIntegration` in the registry.
- *   2. Probing the service here (cheap query is fine — the hook already
+ *   2. Probing the service here (cheap query is fine - the hook already
  *      ships its own network call so adding another doesn't change the
  *      cost model).
  *   3. Returning the boolean in the map.
@@ -24,13 +24,13 @@ export function useDashboardIntegrations(): {
   available: Record<WidgetIntegration, boolean>;
 } {
   const umami = useUmamiActive('today');
-  // Same probe the sidebar uses — `notConfigured: true` is the explicit
+  // Same probe the sidebar uses - `notConfigured: true` is the explicit
   // signal the server returns when the integration isn't wired up.
   const umamiAvailable = umami.isLoading
     ? true
     : (umami.data as { notConfigured?: boolean } | undefined)?.notConfigured !== true;
 
-  // Documenso has no dashboard widgets yet — wire a real probe when the
+  // Documenso has no dashboard widgets yet - wire a real probe when the
   // first one lands. Assuming available for now keeps the map honest if
   // a Documenso widget is added before this hook is updated.
   const documensoAvailable = true;