fix(kb): drop 'use client' from event-summary-react + tighten detail spec selectors

Two test failures from the previous CI run:

1. Dashboard + journey TypesTab tests blew up with:
     Error: Attempted to call renderEventSummary() from the server
     but renderEventSummary is on the client.

   event-summary-react.tsx was marked 'use client' but the dashboard
   and TypesTab are server components that *call* renderEventSummary
   directly. Next 15 rejects that — a client function can only be
   rendered as JSX, not invoked from server code. The function is
   pure (no hooks, no state — just a switch returning JSX), so the
   directive was wrong from the start. Removed it. Server components
   can still return JSX containing <EntityLink> (which IS 'use
   client') — that's the normal server/client composition pattern.

2. kb_detail_renders_summary_and_full_metadata hit strict-mode
   collision: `getByText('Manufacturer')` matched three elements
   because the at-a-glance <dt>Manufacturer</dt> and the full
   metadata table's <dt>manufacturer.name</dt> + <dt>manufacturer.code</dt>
   all match (Playwright getByText normalises case for substring).
   Pinned the at-a-glance assertions to `exact: true` so only the
   capitalised label matches, not the dotted metadata-table keys.

Author: Nigel Tatschner

apps/web/e2e/kb.spec.ts

@@ -200,11 +200,13 @@ test('kb_detail_renders_summary_and_full_metadata', async ({
   await expect(
     page.getByRole('heading', { name: 'Aegis Avenger Stalker', level: 1 }),
   ).toBeVisible();
-  // At-a-glance section.
+  // At-a-glance section. `exact: true` to avoid the strict-mode
+  // collision with the metadata table's `manufacturer.name` /
+  // `manufacturer.code` dotted-path keys.
   await expect(page.getByText('At a glance')).toBeVisible();
-  await expect(page.getByText('Manufacturer')).toBeVisible();
+  await expect(page.getByText('Manufacturer', { exact: true })).toBeVisible();
   await expect(page.getByText('Aegis Dynamics').first()).toBeVisible();
-  await expect(page.getByText('Hull size')).toBeVisible();
+  await expect(page.getByText('Hull size', { exact: true })).toBeVisible();
   // Full metadata section.
   await expect(page.getByText('All metadata')).toBeVisible();
   await expect(page.getByText('manufacturer.name')).toBeVisible();

apps/web/src/lib/event-summary-react.tsx

@@ -1,8 +1,13 @@
-'use client';
-
 /**
  * ReactNode-returning mirror of `formatEventSummary` in
- * `event-summary.ts`. The two functions must produce the same
+ * `event-summary.ts`.
+ *
+ * Universal (no `'use client'`): the function is a pure switch
+ * returning JSX with no React state, so it can be invoked directly
+ * from server components (dashboard / journey TypesTab). It DOES
+ * return `<EntityLink>` instances — those are client components,
+ * and server components composing client components is the
+ * standard pattern (the boundary is handled by Next's bundler). The two functions must produce the same
  * visible text for every variant — but this one inserts
  * `<EntityLink>` wrappers around resolved entity identifiers so
  * the dashboard / journey UI can navigate into `/kb/{category}/{slug}`