Live Activity parity: the prompt

Mark, 2026-11-12, verbatim:

I feel like our live activity viewer could be a more faithful copy of our live activity viewer. Evaluate our current implementation compared to our functional one currently found in the live qcontrol app and pictured here (see image). Create a plan to bring them into alignment and functional parity.

The image: live-parity-reference-main.webp, qdash's Live Activity page in the live qcontrol app (dark theme), on its Audit log tab:

• the header carries a live badge and Open JSONL;
• "Show agents" sits at the right;
• the tabs read Events 26 · Tally 26 · Audit log 16;
• the Audit buffer reads 16 kept · 0.0 MiB, with 5000 events and 25 MiB as its limits;
• the search is activity=Inference;
• the rails read Agents: claude-cli 16 and Activity: http 7 · llm 6 · mcp 2 · file 1;
• the table's columns are Time, Activity, Agent, Summary and Decision;
• there are four Inference rows from claude-cli (58638) to api.anthropic.com. Three are allowed. One is denied, with "Rules: Secret in prompt" under its summary.

Read as: "ours" is qnative's Dev › Live Activity (c138, qnative c3), the copy built on 2026-11-11 to replicate this page. "The functional one" is qdash /live on qcontrol main, the build the live app ships.

The plan: live-parity-plan.md.