Tools: Unity Profiler

[IvanMurzak]

Fix Profiler Tools Implementation (PR #338)

Overview

This task focuses on reviewing and fixing the implementation introduced in the following pull request:

• feat: Add Profiler Tool for Unity performance analysis via MCP #338

The current implementation of the profiler tools is broken and requires stabilization, validation, and proper architectural separation.

---

Goals

1. Ensure Core Compatibility

All functionality used in the new profiler tools must:

• Be fully supported by the built-in Unity Editor
• NOT depend on external or optional Unity packages

---

2. Handle Package Dependencies Properly

If any tool requires functionality from a Unity package:

• That tool must NOT remain in the core implementation
• It must be:
  • Extracted into a separate module
  • Delivered as an Extension
  • Packaged in a dedicated Unity package
  • Explicitly declare its dependencies

---

3. Testing Requirements

• All existing tests must pass
• Each new profiler tool must include:
  • Unit tests
  • Coverage for core functionality
  • Validation of expected behavior

---

Acceptance Criteria

• ✅ No tool in the core depends on non-built-in Unity packages
• ✅ Tools requiring packages are moved to Extension packages
• ✅ All tests pass successfully
• ✅ Each new tool is covered by tests
• ✅ No broken or incomplete implementations remain

---

Notes

• Favor clean separation of concerns between core and extensions
• Keep the core lightweight and dependency-free
• Ensure tools are stable and production-ready