Fix debug module documentation discrepancies

- Fix XE_LOG macro parameter order in debug.md (category, level) was reversed
- Add 'Implementation Status' section to profiler.md listing stub methods
  (MarkEvent, SetMarker, ExportChromeTracing) that are not yet implemented

docs/api/debug/debug.md

@@ -70,11 +70,11 @@ Logger::Get().AddSink(std::make_unique<FileLogSink>("app.log"));
 Logger::Get().SetMinimumLevel(LogLevel::Debug);
 
 // 记录日志
-XE_LOG(LogLevel::Info, LogCategory::Rendering, "Render started");
+XE_LOG(LogCategory::Rendering, LogLevel::Info, "Render started");
 
 // 使用宏记录日志
 if (condition) {
-    XE_LOG(LogLevel::Error, LogCategory::General, "Something went wrong");
+    XE_LOG(LogCategory::General, LogLevel::Error, "Something went wrong");
 }
 ```
 

docs/api/debug/profiler/profiler.md

@@ -78,6 +78,16 @@
 
 自动使用当前函数名进行分析。
 
+## 实现状态
+
+以下方法目前为存根（stub）实现，尚未完成功能：
+
+| 方法 | 状态 |
+|------|------|
+| `void MarkEvent(const char* name, uint64_t timestamp, uint32_t threadId)` | 存根 |
+| `void SetMarker(const char* name, uint32_t color)` | 存根 |
+| `void ExportChromeTracing(const Containers::String& filePath)` | 存根 |
+
 ## 使用示例
 
 ```cpp