tui: follow kai-engine's kai_* tool namespace

[jschatz1]

Downstream of kaicontext/kai-engine#42, which renames the four generic tools:

bash -> kai_bash    view  -> kai_view
write -> kai_write  edit  -> kai_edit

Why this repo needs a change at all

The REPL's tool renderers match those names as string literals off the event stream. Without this they go blind: summarizeToolCall falls through to the bare-name branch, so every file read renders as → kai_view with no path and every shell call with no command. Nothing errors — the output just quietly gets less useful, which is the worst failure mode for a rename.

Changed in internal/tui/views/planner_dispatch.go:

• the view/write/edit and bash cases in the summarizer
• the bashLineCount reset, which keys off the tool name
• tests that pin the rendered output

Deliberately unchanged

The event Kind strings ("bash" for streamed stdout lines) are not tool names — they're the activity-feed channel — and stay as they are. Same for exec.Command("bash", ...) and the shell-completion ValidArgs.

Ordering

Merge after kai-engine#42 ships in a release and this repo's go.mod is bumped to it. Merging earlier is harmless but inert — the renderers would match names the pinned engine doesn't emit yet.

🤖 Generated with Claude Code

[kaicontext]

Kai review

⚠️ Review before merging — 1 flag raised.

Check	Result
Intent	Partial
Coverage	No gaps
Risky claims	1 risk

Risky claims — 1 statement to verify

• internal/tui/views/repl.go:1974 — `HasPrefix(summary, "→ bash: ")` no longer matches the renamed `→ kai_bash: ` summary, so the two-tone bash rendering is dead and all bash calls…

_{+20 −20 · 3 files · reaches 39}

View finding → · Awaiting your verdict — Kai never approves its own finding.