feat(tui): add per-tool output visibility via show_tool_output config

[graelo]

Issue for this PR

Closes #17250

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

Adds a show_tool_output string array to tui.json that lists tool names whose output should always be shown (and expanded), even when the global generic tool output toggle is off.

This addresses the use case where users want to hide noisy tool outputs (file reads, shell commands) but still see rich, formatted output from specific tools like plugins (e.g., project_status, todo_read, todo_edit or any custom tool which output is meant to be read).

Changes:

• Added show_tool_output field to TuiOptions in tui-schema.ts
• Modified GenericTool component to check if a tool is in the list and:
  • Show output block even when global toggle is off
  • Default to expanded state for tools in the list

Usage: in tui.json

{
  "show_tool_output": ["project_status", "todo_edit", "todo_write"]
}

How did you verify your code works?

I've been using it locally for 3 weeks, to allow my subagents use my todo_edit, todo_write and todo_read tools, and occasionally a work-only variant of the generic project_status tool that I mentioned in the issue.

Screenshots / recordings

Here's an example of using show_tool_output inside a subagent

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[graelo]

Somewhat related: In case you're wondering why these custom todo_(read|edit|write) tools: it's because they can be easily used within subagents, they offer one level of subitems, and todo_edit is much more efficient than asking the LLM to regenerate the whole todo list.

[graelo]

The two e2e failures are in session-review.spec.ts and seem unrelated to my PR — the changes here only touch tui-schema.ts and the GenericTool rendering logic. Happy to rerun CI if that would help, or let me know if you'd like me to dig into those tests.