v0.55.1

Fixed

• A Console error caused by the agent's own tool call no longer raises
  the "ask the agent to fix these" chip. Measured with Codex: it passed
  uap_editor_execute_menu a menu path that does not exist
  (GameObject/Duplicate); the tool answered found:false and the agent
  worked around it, but Unity also logs an Error for that call, so the red
  chip appeared, stayed for the rest of the session and was then offered
  to the next agent as well ("Ask Grok to fix") although nothing was wrong
  with the project. Errors logged on the main thread while a UapOps tool is
  running are now attributed to that call: they are appended to the tool
  result (Unity Console errors logged during this call:, at most 5
  lines) so the agent still sees them, and they stay off the chip. Errors
  from other threads, and anything the project logs again after the call,
  reach the chip as before. uap_editor_execute_menu additionally checks
  that the menu item exists before running it, so that particular Error is
  no longer logged at all. Design note:
  docs/design-notes/2026-09-17-tool-caused-console-errors.md.