fix: capture editor launch output and expose view_log tool (issue #106)

[twinlunarstarz-dev]

Summary

Fixes issue #106 — Godot editor launch errors (e.g., parse errors) were invisible to the AI consumer because launch_editor only returned "launched successfully" without capturing console output.

Changes Made (src/index.ts)

1. Added in-memory log buffer

• New field editorLogLines: string[] on GodotServer class stores stdout/stderr lines from editor launches (non-persistent, cleared on new launch).

2. Modified handleLaunchEditor

• Pipes child process stdout and stderr into the editorLogLines buffer line-by-line with [stdout]/[stderr] prefixes.
• Returns immediately after spawning instead of waiting for first output or timing out (prevents timeout on slow startups).

3. New view_log tool

• Accepts optional lineCount parameter (default: 50, max: 1000).
• Returns trailing lines from the log buffer so the AI can inspect what Godot printed during startup.

Direct Modifications

Location	Change
~Line 238+	Added editorLogLines field to class
~Line 1046-1057 (handleLaunchEditor)	Replaced wait/timeout logic with immediate return + stdout/stderr piping into buffer
~Line 90 (tool definitions)	Added new view_log tool schema with lineCount parameter and description
~Line 234-261 (switch handler)	Added case for "view_log" routing to handleViewLog, removed unused "get_debug_output"/"stop_project" cases, updated default error message
New method (~line 1059+)	Implemented handleViewLog() — validates lineCount param and returns trailing lines as [stdout].../[stderr]... prefixed text

Testing

• Tested on a local Godot project: editor launched without issues, no apparent functionality was lost.
• The new view_log tool successfully captures startup output (engine version, GPU info) immediately after launch_editor.
• No duplicate instances were spawned during testing.

Note: I do not have extensive TypeScript knowledge — please inspect the code changes carefully to verify correctness and ensure no edge cases are missed.