Add the read-only analysis catalog panel

REVIEW.md

@@ -62,7 +62,7 @@ The merge control's **tooltip** runs its localized strings through `resolvedOrEm
 
 ## A `title` in a test assertion does not mean the code renders a `title` attribute
 
-Every tooltip in this extension goes through the platform `Tooltip`/`TooltipContent`; none sets an HTML `title` attribute. Tests nevertheless assert `toHaveAttribute('title', …)` because the `Tooltip` stub in [\_\_mocks\_\_/platform-bible-react.tsx](__mocks__/platform-bible-react.tsx) reads its `TooltipContent` child's text and clones the trigger with that text as a `title`, which keeps the tooltip assertable without simulating hover in jsdom. The `title` **prop** some components take (the boundary button's, for one) is likewise just a prop name; it is rendered as `TooltipContent` children.
+Every tooltip in this extension goes through the platform `Tooltip`/`TooltipContent`, with one documented exception: the usage counts in [src/components/CatalogRowView.tsx](src/components/CatalogRowView.tsx) sit inside the row's own button, where a tooltip trigger would nest one interactive element in another, so they carry a native `title` and repeat their label in screen-reader-only text. Outside that exception, no component sets an HTML `title` attribute. Tests nevertheless assert `toHaveAttribute('title', …)` because the `Tooltip` stub in [\_\_mocks\_\_/platform-bible-react.tsx](__mocks__/platform-bible-react.tsx) reads its `TooltipContent` child's text and clones the trigger with that text as a `title`, which keeps the tooltip assertable without simulating hover in jsdom. The `title` **prop** some components take (the boundary button's, for one) is likewise just a prop name; it is rendered as `TooltipContent` children.
 
 So do not conclude from either signal that a control is limited to plain text — for instance, that it cannot hold a `Kbd` or any other element. Read the component's own JSX before claiming a render path is text-only.
 

__mocks__/lucide-react.tsx

@@ -84,3 +84,17 @@ export function Merge(props: Readonly<{ className?: string }>): ReactElement {
 export function Split(props: Readonly<{ size?: number; className?: string }>): ReactElement {
   return <svg data-testid="split-icon" {...props} />;
 }
+
+/**
+ * Stub for the ChevronRight icon, marking a collapsed catalog row.
+ */
+export function ChevronRight(props: Readonly<{ className?: string }>): ReactElement {
+  return <svg data-testid="chevron-right-icon" {...props} />;
+}
+
+/**
+ * Stub for the ChevronDown icon, marking an expanded catalog row.
+ */
+export function ChevronDown(props: Readonly<{ className?: string }>): ReactElement {
+  return <svg data-testid="chevron-down-icon" {...props} />;
+}

__mocks__/platform-bible-react-experimental.ts

@@ -0,0 +1,16 @@
+/**
+ * @file Jest mock for platform-bible-react/experimental. The real package ships ESM which Jest
+ * cannot parse without extra transform configuration. This stub provides the subset used by the
+ * extension.
+ */
+
+/** Text and layout direction. */
+export type Direction = 'rtl' | 'ltr';
+
+/**
+ * Layout direction the interface runs in, read from the document rather than from localStorage as
+ * the real function does, so a test sets it the way it would for any other RTL assertion.
+ */
+export function readDirection(): Direction {
+  return document.documentElement.dir === 'rtl' ? 'rtl' : 'ltr';
+}