tui: playbook empty-state templates are mouse-only and omit the descriptions the web UI shows #1099

The empty-Playbook onboarding (spec 0049) offers the built-in templates as clickable buttons. In the TUI, clicking is the only way to apply one — apply_playbook_template has exactly one non-test call site, in the mouse handler:

self.apply_playbook_template(hit.template_id, hit.markdown);

(crates/cli/src/app/editor.rs ~line 383 @ ad47152, reached from a MouseEventKind::Down hit test against layout.playbook_template_buttons)

No key binding reaches it. Over SSH in a terminal without mouse reporting, or for anyone working keyboard-only, the onboarding is a dead end: the buttons are painted but cannot be activated.

The TUI also shows less than the web UI. Same daemon, same templates:

TUI

Templates

  * Goal
  * Investigation
  * Tasks

web UI

Templates

  * Goal
      Goal, context, requirements, and verification — run to execute
  * Investigation
      Question, context, plan, findings, and done — run to investigate
  * Tasks
      Todo / Progress / Done board the agent runs and delegates

The descriptions are what make the choice meaningful, and they are already carried in the template list the TUI renders from.

Expected

• A keyboard path to apply a template from the empty state (arrow keys + Enter over the buttons, or numbered picks, or routing it through the existing session-picker-style list).
• The TUI empty state shows each template's description, matching the web UI.

Acceptance criteria

• A template can be applied with the keyboard alone, with the affordance visible in the empty state.
• TUI template rows show the same descriptions the web UI shows.
• Mouse activation keeps working.

Found during a hands-on UX audit of the Playbook in the TUI and web UI.