fix(conversations): Render markdown tables with a horizontal scrollbar

[priscilawebdev]

Markdown tables in conversation details overflowed their container instead of scrolling — columns were cut off mid-word at the pane edge.

Cause

The shared MarkdownContainer styled tables with:

table { width: auto; width: max-content; }

width: max-content sizes a table to its widest unwrapped content and ignores the container. Nothing downstream clipped or scrolled it, so wide tables spilled past the pane. Measured in a 320px pane: the table rendered at 563px, forcing 251px of overflow.

This affected both the Input and Output tabs, since both render through that container.

A second, quieter bug: the transcript's MessageText override tried to contain this with table { display: block; max-width: 100%; overflow-x: auto }. That stopped the spill but produced no usable scrollbar (scrollWidth == clientWidth) — a table cannot be both the scroll box and the overflowing content, so display: block made it shrink-wrap and silently squish columns instead.

Change

Swap AI span content onto the design system Markdown renderer, which Seer Explorer already uses. Its DefaultTable wraps each table in a Container overflowX="auto" and sizes the table with min-width: 100% rather than width — narrow tables fill the container, wide ones scroll inside a bordered box while surrounding prose stays anchored.

This deletes the offending CSS rather than patching it (net −72 lines) and drops dangerouslySetInnerHTML from the markdown path in favor of React elements.

• aiContentRenderer.tsx — both markdown paths → scraps Markdown
• styles.tsx — MultilineText's "Pretty" view → scraps Markdown; delete MarkdownContainer and its namespace export
• messagesPanel.tsx — drop the now-obsolete MessageText table/pre override (scraps CodeBlock sets its own overflow-x)

Behavior changes to review

• Code blocks now render via the scraps CodeBlock component — different styling, and they gain a copy button.
• Markdown output is React elements rather than sanitized HTML, so anything depending on the old raw-HTML structure changes shape.

AIContentRenderer is also consumed by the trace drawer's AI span sections, so this affects those surfaces too, not just conversation details.

Out of scope

MARKDOWN_INDICATORS in aiContentDetection.ts has no pattern for tables, so a bare markdown table (no heading, bold, or list nearby) is classified plain-text and rendered as raw pipe characters — it never becomes a table at all. That's a pre-existing detection bug on master, untouched here, and worth its own fix.