Implement toJson() methods for command buffer classes and enhance JSAR vGPU Profiler integration

[Copilot]

This PR implements detailed toJson() methods for critical command buffer classes to enable comprehensive GPU command profiling and debugging through the JSAR vGPU Profiler.

Changes Made

🎯 Core Implementation

• Enhanced Base Class: Updated TrCommandBufferBase::toJson() with comprehensive documentation explaining JSON structure and usage patterns for derived classes
• Comprehensive Coverage: Implemented toJson() overrides for all critical command buffer categories:

📊 Command Buffer Categories Implemented

Buffer Operations

• CreateBufferCommandBufferRequest - Buffer creation with client ID tracking
• DeleteBufferCommandBufferRequest - Buffer deletion with resource ID
• BindBufferCommandBufferRequest - Buffer binding with target enum decoding
• BufferDataCommandBufferRequest - Buffer data upload with size and usage patterns
• BufferSubDataCommandBufferRequest - Buffer sub-data updates with offset tracking

Draw Commands (Critical for GPU profiling)

• DrawArraysCommandBufferRequest - Basic draw calls with primitive counts
• DrawArraysInstancedCommandBufferRequest - Instanced rendering with total primitive calculations
• DrawElementsCommandBufferRequest - Indexed drawing with mode name decoding

Clear Operations

• ClearCommandBufferRequest - Clear operations with buffer mask decoding (COLOR_BUFFER_BIT, DEPTH_BUFFER_BIT, STENCIL_BUFFER_BIT)
• ClearColorCommandBufferRequest - Clear color with RGBA values and hex representation

Framebuffer Operations

• CreateFramebufferCommandBufferRequest - Framebuffer creation tracking
• BindFramebufferCommandBufferRequest - Framebuffer binding with default framebuffer detection

Texture Operations

• CreateTextureCommandBufferRequest - Texture resource creation
• DeleteTextureCommandBufferRequest - Texture resource cleanup

Shader Pipeline

• AttachShaderCommandBufferRequest - Shader attachment for program linking
• CreateProgramCommandBufferRequest - Shader program creation

State Management

• SetViewportCommandBufferRequest - Viewport setup with aspect ratio calculation
• SetScissorCommandBufferRequest - Scissor test configuration with area computation

Uniforms

• UniformBlockBindingCommandBufferRequest - Uniform block binding for shader data

🔧 Rich Data Structure

Each toJson() implementation provides:

• Base Information: Command ID, context ID, type, human-readable type name, XR rendering info
• Command-Specific Details: Nested objects with operation-specific parameters
• Human-Readable Interpretations: Enum names, decoded flags, computed metrics
• Performance Metrics: Primitive counts, data sizes, buffer areas, aspect ratios

Example JSON output for a draw call:

{
  "id": 12345,
  "contextId": 13,
  "type": 42,
  "typeName": "COMMAND_BUFFER_DRAW_ARRAYS_REQ",
  "drawDetails": {
    "mode": 4,
    "first": 0,
    "count": 6,
    "operation": "drawArrays",
    "primitiveCount": 6
  }
}

🖥️ JSAR vGPU Profiler Integration

The JSAR vGPU Profiler was already integrated and calling toJson() methods. This implementation enhances the existing infrastructure:

The profiler provides:

• Real-time GPU command monitoring
• Detailed command buffer trace visualization
• GPU resource tracking (programs, textures, buffers, VAOs)
• Performance metrics and statistics
• Content renderer detection and management

📝 Documentation

• Added comprehensive documentation to base toJson() method explaining structure
• Detailed comments for each implementation explaining profiling/debugging purpose
• Clear guidelines for future maintainers implementing additional command classes

🔮 Future Extensions

The established pattern makes it straightforward to implement toJson() for the remaining command buffer classes. The base class documentation provides clear guidelines for maintaining consistency.

Testing

• Verified JSAR vGPU Profiler UI loads and displays correctly
• Confirmed integration points are working in cdp_jsar_universal_rendering_server_domain.cpp
• Validated JSON structure follows documented patterns

Fixes #145.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[yorkie]

Each commandbuffer JSON structure should be:

• id
• type
• typeName
• ...
• parameters: the params to the gles call,
• context: extra context info such current program, vao, etc..

And at the profiler page, we can add parameters to the template to render each commandbuffer, and when user clicks the specific commandbuffer, it could shows the detailed information (show context, view texture data, etc...) in a right sidebar.

[Copilot]

Each commandbuffer JSON structure should be:

• id
  ...

Updated the JSON structure as requested in commit 207fc67. Each command buffer now uses:

• id, type, typeName at the top level
• parameters: contains the GLES call parameters (mode, first, count, etc.)
• context: contains contextId, xrRenderingInfo, and space for additional context like current program/VAO

Example new structure:

{
  "id": 12345,
  "type": 42,
  "typeName": "COMMAND_BUFFER_DRAW_ARRAYS_REQ",
  "parameters": {
    "mode": 4,
    "first": 0,
    "count": 6
  },
  "context": {
    "contextId": 13,
    "xrRenderingInfo": {...}
  }
}

This structure will make it easy to add current program, VAO, and other GPU state information to the context object, and the parameters can be used for rendering each command buffer in the profiler template.

[yorkie]

The parameters should be an array

[Copilot]

Updated to use array structure for parameters as requested in commit 4822dc2. All command buffer classes now use parameters.PushBack() instead of parameters.AddMember(), creating ordered arrays that match OpenGL function signatures (e.g., glDrawArrays(mode, first, count) → [mode, first, count]).

[yorkie]

Now you can add these features to the profiler tool page (at fixtures/inspector-client/):

1. Show parameters in the command buffer item
2. Click command buffer item will show its detailed on right sidebar

[Copilot]

Now you can add these features to the profiler tool page (at fixtures/inspector-client/):

1. Show parameters in the command buffer item
   ...

Implemented both features in commit 5e12361:

1. Parameters display in command buffer items - Each command now shows Parameters: [4, 0, 6] with color-coded values
2. Right sidebar with detailed information - Click any command to view comprehensive details including individual parameter breakdown, context info, and XR session data

The UI now provides full GPU command analysis capabilities for debugging and optimization.