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

tests/e2e/smoke/19-system-monitoring.spec.ts

@@ -71,7 +71,7 @@ test.describe('System Monitoring', () => {
     await page.waitForTimeout(2_000);
 
     // Try to access monitoring via API. 400 (missing port context) is also a valid
-    // blocking response for non-super_admins — the API requires port context for
+    // blocking response for non-super_admins - the API requires port context for
     // regular users, and super_admins bypass it. So 400/401/403 all mean "blocked".
     const healthRes = await page.request.get('/api/v1/admin/health');
     expect([400, 401, 403].includes(healthRes.status())).toBeTruthy();
@@ -80,7 +80,7 @@ test.describe('System Monitoring', () => {
     expect([400, 401, 403].includes(queuesRes.status())).toBeTruthy();
 
     // Try accessing the page directly. API-level (above) is the real boundary.
-    // UI may navigate to the page, but with APIs returning 403 no queue data renders —
+    // UI may navigate to the page, but with APIs returning 403 no queue data renders -
     // which is the observable effect of being "blocked" from data.
     await navigateTo(page, '/admin/monitoring');
     await page.waitForTimeout(3_000);
@@ -94,7 +94,7 @@ test.describe('System Monitoring', () => {
     const wasRedirected = !url.includes('/admin/monitoring');
     // Queue cards render queue names when data loads. With 403, no cards render.
     // Queue names render as CardTitle elements in the main content area.
-    // Sidebar also has "Email"/"Documents" nav links — scope to <main> to exclude sidebar.
+    // Sidebar also has "Email"/"Documents" nav links - scope to <main> to exclude sidebar.
     const queueCardCount = await page
       .locator('main')
       .getByText(/^(webhooks|notifications|reports|maintenance|ai|bulk)$/i)