Surface editor error context in log reads (#520)

* Surface editor error context in log reads

Editor and game logs now preserve structured error details, read visible Debugger Errors rows through logs_read, and clear those rows from clear_logs. Compact responses remain the default; callers opt into rich metadata with include_details.

* Address review: gate Errors-tab clear, full stack frames, cheaper polling

- clear_logs no longer wipes the Debugger Errors panel by default; the
  Errors-tab clear sits behind a new clear_debugger_errors opt-in and
  routes through the panel's own Clear button so the engine resets
  error_count/warning_count, the "Errors (N)" badge, the errors_cleared
  signal, and toolbar button states (a raw Tree.clear() left them stale).
- details.frames now captures every stack row. The real tree (verified
  against script_editor_debugger.cpp on 4.3 and 4.6) lays frames out as
  flat children with only frame 0 labeled "<Stack Trace>", so the old
  per-child label match collapsed multi-frame stacks to one entry.
  Detection is run-based, survives translated labels, and the test
  fixture now mirrors the real layout.
- _entries_for_response shallow-copies on the default compact path and
  reserves the deep copy for include_details=true.
- Debugger tree discovery scans only the cached EditorDebuggerNode
  subtree instead of recursing the whole editor UI on every poll.

Live-smoked against a real editor (Godot 4.6.3): a real push_error row
returned all 5 stack frames; the opt-in clear reset the "Errors (1)"
badge and button states via the engine's own clear path.

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

---------

Co-authored-by: David Sarno <david@lighthaus.us>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: 3 people

docs/TOOLS.md

@@ -29,11 +29,22 @@ not the MCP tool names.
 | `script_create` / `script_attach` / `script_patch` | Create, attach, anchor-edit GDScript files |
 | `project_run` | Play the project (autosave persists in-memory MCP edits unless `autosave=False`) |
 | `test_run` | Run GDScript test suites in the editor |
-| `logs_read` | Read plugin / game / editor / combined log buffers. `source="editor"` surfaces parse errors + @tool/EditorPlugin runtime errors + push_error/push_warning (Godot 4.5+, filtered to user .gd/.cs) — use this when the editor's Output panel shows red lines but `logs_read` returned nothing |
+| `logs_read` | Read plugin / game / editor / combined log buffers. `source="editor"` surfaces parse errors, GDScript reload warnings, @tool/EditorPlugin runtime errors, push_error/push_warning, and visible Debugger dock Errors-tab rows — use this when the editor's Output or Debugger Errors panel shows red/yellow rows |
 | `editor_screenshot` | Capture editor viewport, cinematic camera, or running game framebuffer |
 | `editor_reload_plugin` | Reload the plugin and wait for reconnect (server must be external) |
 | `animation_create` | Create an Animation clip (auto-creates AnimationPlayer + library if missing) |
 
+`logs_read` also accepts `include_details=true` for `source="editor"`,
+`source="game"`, and `source="all"`. Detailed entries include the original
+Godot `_log_error` code/rationale when available, error type, resolved source
+location, and stack/error-tree context corresponding to the Debugger dock's
+Errors tab.
+
+`editor_manage(op="logs_clear")` accepts `clear_debugger_errors=true` to also
+clear the Debugger dock's visible Errors-tab rows (routed through the panel's
+own Clear path so the tab badge and counters reset). The Errors panel is
+user-facing UI, so the default leaves it untouched.
+
 ## Domain rollups (`<domain>_manage`)
 
 Each rollup is a single MCP tool dispatched by `op` name + `params` dict.

plugin/addons/godot_ai/debugger/mcp_debugger_plugin.gd

@@ -192,14 +192,24 @@ func _capture(message: String, data: Array, session_id: int) -> bool:
 func _on_log_batch(data: Array) -> void:
 	if _game_log_buffer == null:
 		return
-	## data layout: [[[level, text], [level, text], ...]]
+	## data layout: [[[level, text, details?], ...]]
 	if data.is_empty() or not (data[0] is Array):
 		return
 	var entries: Array = data[0]
 	for entry in entries:
+		if entry is Dictionary:
+			var dict_details: Dictionary = {}
+			var raw_dict_details = entry.get("details", {})
+			if raw_dict_details is Dictionary:
+				dict_details = raw_dict_details
+			_game_log_buffer.append(str(entry.get("level", "info")), str(entry.get("text", "")), dict_details)
+			continue
 		if not (entry is Array) or entry.size() < 2:
 			continue
-		_game_log_buffer.append(str(entry[0]), str(entry[1]))
+		var details: Dictionary = {}
+		if entry.size() > 2 and entry[2] is Dictionary:
+			details = entry[2]
+		_game_log_buffer.append(str(entry[0]), str(entry[1]), details)
 
 
 ## Request a game-process framebuffer capture over the debugger channel.