Polish debug tool activity styling in cloud chat

Problem

Keep tool activity visible in debug mode, but replace the current raw/emojified presentation with a cleaner system status style. Remove emojis, improve spacing/typography/hierarchy, distinguish tool start/success/error states, and make long SQL/query evidence collapsible or secondary so debugging remains possible without overwhelming the main answer.

Context

The current org-home chat intentionally exposes tool activity while debugging, but the presentation reads like internal scaffolding rather than a designed UI. During QA the activity stream showed emoji-prefixed rows such as 📦, 📋, 🔍, ✓, plus raw status labels like list sources complete, catalog complete, render dashboard complete, and inline query output tables. That level of visibility is useful for debugging and should remain available, but the styling makes the surface feel unfinished.

This task is explicitly not about hiding tool activity. It is about making debug-visible execution states legible and intentional:

• no emojis
• clear visual distinction between in-progress, success, and error states
• better typography and spacing so the answer remains primary
• long SQL / raw result evidence presented as secondary detail rather than dominating the message

Likely touchpoints include the shared chat rendering layer used by the org-home chat and any status/event formatting that currently emits ad hoc badge rows or plain stacked tool output.

Possible Solutions

1. Recommended: keep the current event model, but redesign the renderer into a compact debug activity rail. Trade-off: lowest product risk because it preserves existing semantics and only changes presentation. It also keeps debug usefulness high.
2. Replace the step-by-step rows with one rolling Working... summary plus expandable details. Trade-off: cleaner visually, but it hides live per-tool progress unless expanded and is less useful for active debugging.
3. Add a separate debug mode toggle and leave the default current presentation alone. Trade-off: flexible long term, but does not solve the poor styling in the mode people are actually using today.

The recommended direction is to keep debug visibility first-class, but present it with system-style rows, subdued chrome, monospace only where helpful, and collapsible evidence blocks for long query payloads.

Plan

1. Inventory the chat event/status render path for tool start, tool success, tool error, and evidence payloads.
2. Define a visual treatment for debug-visible activity: - neutral system labels instead of emojis - compact rows for status - clear error styling - secondary containers for SQL and raw table evidence
3. Update the shared chat UI so org-home and related surfaces inherit the same treatment.
4. Run QA on the suite home page chat with multi-step prompts to confirm the answer remains primary while tool activity stays inspectable.

Implementation Progress

QA Exploration

• [ ] QA exploration completed (or N/A for non-UI tasks)

Review Feedback

• [ ] Review cleared