The get_console_logs tool was unable to retrieve info logs because MCP's "info"
parameter didn't match Unity's internal "Log" type string. Added mapping logic
to convert "info" to "Log" before filtering log entries.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Move log type mapping logic outside the loop to avoid repeated processing.
Added static Dictionary for MCP-to-Unity log type mappings with case-insensitive
comparison. This improves performance and provides better extensibility for
future log type mappings.

Addresses CodeRabbit review feedback for performance optimization.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Per PR review feedback, expanded the log type mapping to handle multi-value
mappings. The "error" filter now returns all error-related log types.

We found that filtering by "error" was not comprehensive enough for
development purposes - Exception and Assert logs are also error conditions
that developers need to see.

Changes:
- Changed LogTypeMapping from Dictionary<string, string> to
  Dictionary<string, HashSet<string>> to support 1-to-many mappings
- Added "error" → {"Error", "Exception", "Assert"} mapping
- Updated GetAllLogsAsJson filtering logic to use HashSet.Contains()

This ensures developers can see all error-related logs when filtering
by "error" type, making debugging more effective.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

- Add offset and limit parameters to GetConsoleLogsResource and GetConsoleLogsTool
- Implement GetLogsAsJson method with pagination in ConsoleLogsService
- Return logs in newest-first order for better debugging workflow
- Add automatic memory management with configurable cleanup thresholds
- Update resource descriptions with pagination usage recommendations
- Enhance Unity-side and Node.js-side implementations consistently

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

…source

- Add bounds validation for offset (≥0) and limit (1-1000) parameters
- Simplify parameter extraction with helper method
- Add defensive programming for pagination metadata access
- Reduce code duplication and improve maintainability

Addresses CodeRabbit review feedback for better error handling and robustness.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

fix: Map 'info' log type to Unity's 'Log' type for console log retrieval

Resolved conflict by combining pagination functionality with the new log type mapping feature from upstream.

- Remove pagination object and consolidate info into message field
- Delete deprecated GetAllLogsAsJson method
- Optimize log counting with single loop for better performance
- Add default offset/limit values to resource templates
- Simplify response to only include logs, message, and success fields
- Move count information (total, filtered, returned) into message text
- Add parameter validation for offset/limit in TypeScript

This addresses all review comments from PR #42 to make the response
format more concise and easier for AI agents to process.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

feat: Add pagination support to console logs to prevent LLM token limits

…tion

- Add includeStackTrace parameter to get_console_logs tool and resource
- Default to true for backward compatibility (except info logs in resource)
- Reduces token usage by 80-90% when set to false
- Update tool/resource descriptions with clear hints for LLMs to use this option
- Add ⚠️ emoji to highlight token-saving recommendations
- Implement stack trace filtering in Unity-side ConsoleLogsService

This helps prevent LLM context window overflow when retrieving Unity console logs.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

…option

feat: Add includeStackTrace option to reduce LLM token usage by 80-90%

… changes aim to make the MCP Unity Editor more user-friendly, easier to configure, and better documented for developers.

Key changes include:
- **Editor UI Enhancements:** Updated `McpUnityEditorWindow.cs` to include new sections for connected clients, npm executable path configuration, and direct buttons for configuring Windsurf, Claude Desktop, and Cursor IDEs.
- **New Settings:** Added `NpmExecutablePath` to `McpUnitySettings.cs` to allow users to specify a custom npm executable path.
- **Utility Functions:** Implemented new utility methods in `McpUtils.cs` for generating MCP configuration JSON, integrating with various IDEs, and running npm commands for server installation/building.
- **Comprehensive Documentation:** Overhauled `README.md` and its localized versions (`README-ja.md`, `README_zh-CN.md`) with detailed features, installation steps, usage guides, debugging information, and an extensive FAQ section.
- **Documentation Assets:** Added a new `docs/` directory containing images referenced in the updated README files.