Navi Code TUI: sub-agent spawn card + nested styling for subagent thinking/planning ...

Sub-agent activity was either rendered as a generic tool card (spawn_agent) or
dropped to raw debug output (turn_thinking was unhandled in the TUI chat model
and the raw CLI). The webclient nests subagent events inside the spawn_agent
card; the TUI is flat, so nesting is conveyed with a distinct spawn card plus
left-indented, dimmed subagent cards.

New renderers/subagent.py:
- SpawnAgentStartedRenderer: "↘ subagent · <profile_id>" card showing the task
  (+ briefing dimmed), secondary border. Registered before ToolStartedRenderer.
- SpawnAgentResultRenderer: "↙ subagent · <profile_id> ✓/✗" card with the
  result, success/error border. Registered before ToolResultRenderer.

Nested subagent styling (left indent via Padding + dim):
- ThinkingRenderer: is_subagent → "subagent thinking" title, dim border, indented.
- PlanningStatusRenderer / PlanReadyRenderer: is_subagent → indented (label/title
  already mark it as subagent).
- ToolStartedRenderer / ToolResultRenderer: is_subagent → indented so inner
  tool calls read as nested inside the spawn card.

chat_model handles turn_thinking → thinking_block item with is_subagent meta;
chat_panel._refresh forwards is_subagent to the thinking renderer. Raw CLI
render.py prints turn_thinking as a [thinking] block (with "(subagent)" prefix).

Tests: spawn card shows profile/task and status; subagent thinking/planning/tool
cards are indented and labeled; non-subagent tool card is not indented;
turn_thinking creates a subagent thinking_block. 593 passed, 1 skipped.

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code: render planning as a progress line + plan card, not raw events ...

planning_status and plan_ready events were unhandled in the TUI chat model and
the raw CLI renderer, so they fell through to raw debug output (TUI:
"plan_ready: {...}" status lines; raw CLI: "[event: plan_ready] {msg}").

TUI:
- New renderers/planning.py: PlanningStatusRenderer renders a "⚙ Planning ·
  <label>" line (info color; dim + "(subagent)" prefix for subagent planning);
  PlanReadyRenderer renders the plan as a Panel wrapping themed Markdown, titled
  "Plan" with an accent border ("subagent plan" + dim border for subagents).
- Registered both in default_registry().
- chat_model handles the events: non-subagent planning_status rolls in place
  (Analysis → Execution plan → Plan review share one line instead of stacking);
  plan_ready consumes the pending planning line and appends the plan card;
  subagent planning is appended as its own dim line/card so it does not bleed
  into the parent turn's indicator (matching the webclient).
- chat_panel._refresh maps the new kinds to the registry.

Raw CLI (render.py): planning_status prints "[planning] <label>"; plan_ready
prints a "[plan] … [/plan]" block with the plan text.

Tests: renderer accepts/render (label, subagent prefix, plan title/content);
chat_model rolling-in-place, plan_ready consumes indicator, subagent separation.
584 passed, 1 skipped.

Co-Authored-By: Claude <noreply@anthropic.com>