[Bug]: Desktop TODOS panel ignores todo_write calls made inside codemode #159

GUI version

0.1.60

Operating system

Windows

Reproduction steps

1. Enable the todos mod and set codemode to tools (/config or config.json).
2. Start a multi-step task so the agent creates a todo list (todo_write).
3. Let the agent finish the work; it will complete the list using await tools.todo_write(...) inside a codemode script, because todo_write is read-only and therefore script-first in this mode.
4. Watch the TODOS tray above the composer, and reopen the thread afterwards.

Expected behavior

The TODOS tray and the transcript TODO card reflect the latest statuses from the nested update (all items checked off, tray hides once everything is completed).

Actual behavior

• The tray and TODO card keep showing the original list indefinitely (e.g. 0/8, first item in_progress, rest pending), even though the agent's codemode call marked every item completed and the harness session state is correct.
• The nested update is visible only as a generic codemode output line (✓ todo_write …); no new TODO tool row or status change is rendered.

Screenshots, recordings, or sanitized logs

Root cause: createCodemodeTool executes nested tools with runner.execute({ ..., nested: true }) and emits no tool_queued/tool_completed events. The desktop computes activeTodos only from top-level thread items whose tool name starts with todo (IJ/Bx/LJ in workspace-screen-C6Kunc9Q.js), so nested todo_write updates are invisible. The ACP sessionUpdate: "plan" translator has the same top-level-only gap.

Safety check

• I removed credentials and private project information from this report.