@gracker/smartperfetto 1.0.13

package/skills/pipelines/webview_surface_control.skill.yaml

@@ -0,0 +1,187 @@
+# SPDX-License-Identifier: AGPL-3.0-or-later
+# Copyright (C) 2024-2026 Gracker (Chris)
+# This file is part of SmartPerfetto. See LICENSE for details.
+
+# =============================================================================
+# WebView Surface Control Pipeline
+# =============================================================================
+# Modern WebView with Viz/OOP-R and SurfaceControl.
+# Independent composition without blocking App RenderThread.
+# =============================================================================
+
+name: pipeline_webview_surface_control
+version: "1.0"
+type: pipeline_definition
+category: rendering
+
+meta:
+  pipeline_id: WEBVIEW_SURFACE_CONTROL
+  display_name: "WebView Surface Control"
+  description: "现代 WebView + Viz/OOP-R，独立合成"
+  icon: "web"
+  family: webview
+  doc_path: "rendering_pipelines/webview_surface_control.md"
+  # ----- Article-grounded signature (S09) -----
+  s_article_ref: "S09"
+  four_features:
+    producer_threads: ["VizCompositorThread", "CrRendererMain", "Compositor", "CompositorTileWorker*"]
+    expected_layer_count: "N (overlay candidates)"   # Chromium 为每个 candidate 创建 SurfaceControl overlay
+    bufferqueue_path: "CHROMIUM_TO_ASURFACECONTROL_TRANSACTION"   # Chromium overlay candidates → ASurfaceControl 直接提交
+    extra_rhythm_sources: ["chromium_compositor_rhythm"]
+  deviation_anchors: "independent_overlay_anchor_6_at_chromium_to_sf"
+  # 锚点偏离：网页内容由 Chromium 直接走 ASurfaceControl/ASurfaceTransaction 提交到 SF，
+  # 不经宿主 RT replay，避免阻塞宿主 RenderThread。
+  subvariants_note: "文章 S09 列 5 种 WebView 路径中的 SurfaceControl 模式（参 webview_gl_functor 注释）。"
+  hwc_constraint: |
+    overlay candidate 数量过多时 HWC plane 不够 → 部分 candidate 回退到 client composition
+    → SF GPU 合成成本上升。这是 SurfaceControl 模式相对 Functor 的额外风险点。
+
+detection:
+  scoring_signals:
+    - signal: has_viz_compositor
+      thread_pattern: "VizCompositorThread*"
+      weight: 55
+    - signal: has_cr_renderer
+      thread_pattern: "CrRendererMain*"
+      weight: 12
+    - signal: has_surface_control
+      slice_pattern: "*SurfaceControl*"
+      weight: 15
+
+  exclude_if:
+    - thread: "1.ui"           # Flutter engine present → use Flutter pipeline
+
+teaching:
+  title: "WebView Surface Control 渲染管线"
+  summary: |
+    现代 WebView 使用 Viz (Visual Compositor) 和 OOP-R (Out-of-Process Rasterization)
+    进行渲染时，可能通过 SurfaceControl 独立提交到 SurfaceFlinger。
+    browser code 与 GPU / network services 通常仍在宿主 app 进程内；
+    是否启用该模式、是否完全不阻塞宿主 RenderThread，要以具体设备和 trace 为准。
+
+  mermaid: |
+    sequenceDiagram
+      participant CR as CrRendererMain
+      participant Viz as VizCompositorThread
+      participant SC as SurfaceControl
+      participant TX as Transaction
+      participant VS as VSync-sf
+      participant SF as SurfaceFlinger
+
+      Note over CR,SF: 📍 WebView Surface Control (条件成立时的独立合成)
+      CR->>CR: Blink 渲染网页
+      CR->>Viz: 提交合成任务
+
+      activate Viz
+      Viz->>Viz: GPU 光栅化 Tiles
+      Viz->>Viz: 合成网页 Layers
+      Viz->>SC: 创建/更新 SurfaceControl
+      Viz->>TX: ASurfaceTransaction
+      TX->>SF: 独立提交 Transaction
+      deactivate Viz
+
+      VS->>SF: 🔔 VSync-sf
+      activate SF
+      SF->>SF: latchBuffer
+      SF->>SF: HWC Composite
+      deactivate SF
+
+      Note over CR,SF: ✨ 独立于 App RenderThread，不阻塞 UI
+  thread_roles:
+    - thread: VizCompositorThread
+      role: "Viz 合成器"
+      description: "Chromium 可视化合成器，线程名可能表现为 VizCompositorThread 或相近名称"
+    - thread: CrRendererMain
+      role: "Chromium 渲染"
+      description: "WebView 内容渲染"
+
+  key_slices:
+    - name: "VizCompositorThread (hint)"
+      thread: VizCompositorThread
+      description: "Viz 合成提示信号，未必稳定可见"
+    - name: "SurfaceControl"
+      thread: any
+      description: "SurfaceControl 事务"
+
+auto_pin:
+  instructions:
+    # Time-ordered pinning (production -> transfer -> consume -> display)
+    - pattern: "^VSYNC-app$"
+      match_by: name
+      priority: 1
+      reason: "VSync (WebView 开始生产帧)"
+
+    - pattern: "^main(\\s+\\d+)?$"
+      match_by: name
+      priority: 2
+      reason: "WebView 宿主 UI (生产)"
+      expand: true  # 展开显示 Running 状态和 callstack
+      smart_filter:
+        enabled: true
+        description: "仅 Pin 活跃渲染进程的宿主主线程"
+
+    - pattern: "CrRendererMain"
+      match_by: name
+      priority: 3
+      reason: "Chromium 渲染 (生产/传输)"
+      smart_filter:
+        enabled: true
+        description: "仅 Pin 属于当前 app 的 Chromium 渲染进程"
+
+    - pattern: "VizCompositorThread|VizCompositor"
+      match_by: name
+      priority: 4
+      reason: "Viz 合成器 (传输)"
+      smart_filter:
+        enabled: true
+        description: "仅 Pin 属于当前 app 的 Viz 合成器线程/进程"
+
+    - pattern: "^VSYNC-sf$"
+      match_by: name
+      priority: 5.5
+      reason: "VSync (SurfaceFlinger 消费/合成)"
+
+    - pattern: "^BufferTX"
+      match_by: name
+      priority: 6
+      reason: "BufferTX (SurfaceFlinger 事务)"
+
+    - pattern: "^[sS]urface[fF]linger"
+      match_by: name
+      priority: 7
+      reason: "SurfaceFlinger (最终合成/显示)"
+      main_thread_only: true
+
+analysis:
+  common_issues:
+    - id: viz_latency
+      name: "Viz 延迟"
+      description: "Viz 合成器处理延迟"
+      detection_skill: sf_frame_consumption
+
+    # ----- Article-grounded issues (S09) -----
+    - id: hwc_overlay_count_overflow_to_client_composition
+      name: "Overlay candidate 数量过多触发 HWC client composition 回退"
+      description: |
+        Chromium 为每个 overlay candidate 创建 SurfaceControl，HWC plane 数量有限。
+        多 overlay 同屏时部分会被打回 client composition，GPU 带宽吃紧。
+      detection_skill: sf_layer_count_in_range
+
+    - id: surfacecontrol_transaction_late_apply
+      name: "ASurfaceTransaction apply 晚到"
+      description: |
+        Chromium 的 overlay transaction 与宿主窗口 transaction 不同帧 apply 时，用户看到 layer 错位。
+        SurfaceSyncGroup（API 34+）可以让多 transaction 同帧生效。
+      detection_skill: sf_composition_in_range
+
+    - id: chromium_renderer_blocking_compositor
+      name: "Chromium Renderer 阻塞 Compositor"
+      description: |
+        CrRendererMain 卡或 commit 慢，VizCompositorThread 收不到 CompositorFrame，
+        ASurfaceTransaction 提交也会延迟。
+      detection_skill: cpu_analysis
+
+  recommended_skills:
+    - sf_frame_consumption
+    - sf_layer_count_in_range
+    - cpu_analysis

package/skills/pipelines/webview_surfaceview_wrapper.skill.yaml

@@ -0,0 +1,196 @@
+# SPDX-License-Identifier: AGPL-3.0-or-later
+# Copyright (C) 2024-2026 Gracker (Chris)
+# This file is part of SmartPerfetto. See LICENSE for details.
+
+# =============================================================================
+# WebView SurfaceView Wrapper Pipeline
+# =============================================================================
+# Full-screen video wrapper mode for WebView.
+# Used for video playback in WebView.
+# =============================================================================
+
+name: pipeline_webview_surfaceview_wrapper
+version: "1.0"
+type: pipeline_definition
+category: rendering
+
+meta:
+  pipeline_id: WEBVIEW_SURFACEVIEW_WRAPPER
+  display_name: "WebView SurfaceView Wrapper"
+  description: "WebView 全屏视频包装模式"
+  icon: "video"
+  family: webview
+  doc_path: "rendering_pipelines/webview_surfaceview_wrapper.md"
+  # ----- Article-grounded signature (S09 + S12) -----
+  s_article_ref: "S09"
+  four_features:
+    producer_threads: ["MediaCodec*", "media.codec", "media.swcodec", "CrRendererMain"]
+    expected_layer_count: 1   # 视频独立 SurfaceView layer
+    bufferqueue_path: "MEDIACODEC_TO_INDEPENDENT_SURFACE"   # 视频解码 → 独立 Surface BufferQueue → SF
+    extra_rhythm_sources: ["video_codec_pacing"]
+  deviation_anchors: "video_independent_surface_anchor_4_5_6_at_codec"
+  # 锚点偏离：网页全屏视频时由 MediaCodec 直接解码到独立 SurfaceView 的 BufferQueue（同 S12 video overlay）。
+  # CrRendererMain 主要管视频外壳 UI（控制条/字幕/手势）。
+  related_pipeline: "全屏视频部分等价于 VIDEO_OVERLAY_HWC（S12），与之配合使用"
+  subvariants_note: "文章 S09 列出的 5 种 WebView 路径之一（参 webview_gl_functor 注释）。"
+
+detection:
+  scoring_signals:
+    - signal: has_webview
+      slice_pattern: "*WebView*"
+      weight: 30
+    - signal: has_webview_core
+      thread_pattern: "WebViewCore*"
+      weight: 10
+    - signal: has_cr_renderer
+      thread_pattern: "CrRendererMain*"
+      weight: 10
+    - signal: has_surfaceview
+      slice_pattern: "*SurfaceView*"
+      weight: 25
+    - signal: has_video
+      slice_pattern: "*Video*"
+      weight: 12
+    - signal: has_mediacodec
+      slice_pattern: "*MediaCodec*"
+      weight: 13
+
+  exclude_if:
+    - thread: "1.ui"           # Flutter engine present → use Flutter pipeline
+
+teaching:
+  title: "WebView SurfaceView Wrapper 渲染管线"
+  summary: |
+    WebView 全屏视频播放模式，使用 SurfaceView 包装视频内容。
+    视频解码通过 MediaCodec，直接输出到 SurfaceView。
+    常见于网页视频全屏播放场景。
+
+  mermaid: |
+    sequenceDiagram
+      participant Main as App (main)
+      participant WV as WebView
+      participant CR as CrRendererMain
+      participant SV as SurfaceView
+      participant BQ as BufferQueue
+      participant VS as VSync-sf
+      participant SF as SurfaceFlinger
+
+      Note over Main,SF: 📍 WebView SurfaceView Wrapper (全屏视频)
+      Main->>WV: 加载视频页面
+      WV->>CR: 请求视频渲染
+
+      activate CR
+      CR->>SV: 创建 SurfaceView 包装
+      CR->>BQ: 视频解码输出
+      deactivate CR
+
+      Note over SV,SF: 视频帧独立路径
+      BQ-->>SF: 视频 Buffer Ready
+      VS->>SF: 🔔 VSync-sf
+      activate SF
+      SF->>SF: latchBuffer (视频 Layer)
+      SF->>SF: HWC Overlay/Composite
+      deactivate SF
+
+      Note over Main,SF: 🎬 全屏视频使用独立 Surface 优化
+  thread_roles:
+    - thread: main
+      role: "App 控制"
+      description: "控制 WebView 和播放状态"
+    - thread: CrRendererMain
+      role: "Chromium 渲染"
+      description: "WebView 内容和视频协调"
+    - thread: MediaCodec
+      role: "视频解码"
+      description: "硬件视频解码"
+    - thread: SurfaceFlinger
+      role: "合成/Overlay"
+      description: "将视频 SurfaceView Layer 以 Overlay 或 GPU 合成方式输出"
+
+  key_slices:
+    - name: "MediaCodec"
+      thread: any
+      description: "视频解码（queue/dequeue/releaseOutputBuffer 等）"
+    - name: "SurfaceView"
+      thread: any
+      description: "全屏视频 SurfaceView 创建/attach/resize"
+    - name: "latchBuffer"
+      thread: SurfaceFlinger
+      description: "SurfaceFlinger 获取视频 Buffer（决定 Overlay/合成）"
+    - name: "HWC"
+      thread: any
+      description: "硬件合成/Overlay 相关调用（不同厂商 trace 名称可能不同）"
+
+auto_pin:
+  instructions:
+    # Time-ordered pinning (production -> transfer -> consume -> display)
+    - pattern: "^VSYNC-app$"
+      match_by: name
+      priority: 1
+      reason: "VSync (WebView/视频开始生产帧)"
+
+    - pattern: "^main(\\s+\\d+)?$"
+      match_by: name
+      priority: 2
+      reason: "App 控制 (生产)"
+      expand: true  # 展开显示 Running 状态和 callstack
+      smart_filter:
+        enabled: true
+        description: "仅 Pin 活跃渲染进程的宿主主线程"
+
+    - pattern: "CrRendererMain"
+      match_by: name
+      priority: 3
+      reason: "Chromium 渲染 (生产/传输)"
+      smart_filter:
+        enabled: true
+        description: "仅 Pin 属于当前 app 的 Chromium 渲染进程"
+
+    - pattern: "MediaCodec"
+      match_by: name
+      priority: 4
+      reason: "视频解码 (生产/传输)"
+
+    - pattern: "^VSYNC-sf$"
+      match_by: name
+      priority: 5.5
+      reason: "VSync (SurfaceFlinger 消费/合成)"
+
+    - pattern: "^BufferTX"
+      match_by: name
+      priority: 6
+      reason: "BufferTX (SurfaceFlinger 事务)"
+
+    - pattern: "^[sS]urface[fF]linger"
+      match_by: name
+      priority: 7
+      reason: "SurfaceFlinger (最终合成/显示)"
+      main_thread_only: true
+
+analysis:
+  common_issues:
+    # ----- Article-grounded issues (S09 + S12) -----
+    - id: codec_underflow
+      name: "MediaCodec output buffer 不足"
+      description: |
+        MediaCodec releaseOutputBuffer 频率与显示节奏不匹配——pool 用完时下一次 dequeueOutputBuffer 阻塞。
+        触发原因：HWC 消费慢 / SurfaceView consumer back-pressure / decoder 解码慢。
+      detection_skill: gpu_render_in_range
+
+    - id: hwc_overlay_decision_for_video
+      name: "HWC overlay 决策对视频敏感"
+      description: |
+        视频 buffer 通常 YUV NV12/P010 格式，HWC 倾向 device composition；但 DRM/HDCP 受保护内容必须走 secure overlay；
+        旋转、缩放比例超 HWC scaler 能力或 HDR 元数据不支持 → 回退 client composition 增加 GPU 负担。
+      detection_skill: sf_layer_count_in_range
+
+    - id: webview_video_chrome_decoupling
+      name: "网页视频与外壳 UI 解耦"
+      description: |
+        视频 layer 走 MediaCodec → 独立 Surface 路径，CrRendererMain 仅管理外壳。
+        若网页外壳 UI（控制条、字幕）渲染卡，但视频流畅，要分别归因。
+      detection_skill: sf_frame_consumption
+
+  recommended_skills:
+    - sf_frame_consumption
+    - cpu_analysis

package/skills/pipelines/webview_textureview_custom.skill.yaml

@@ -0,0 +1,201 @@
+# SPDX-License-Identifier: AGPL-3.0-or-later
+# Copyright (C) 2024-2026 Gracker (Chris)
+# This file is part of SmartPerfetto. See LICENSE for details.
+
+# =============================================================================
+# WebView TextureView Custom Pipeline
+# =============================================================================
+# Custom WebView kernel (X5/UC) using TextureView.
+# Third-party WebView implementations in China.
+# =============================================================================
+
+name: pipeline_webview_textureview_custom
+version: "1.0"
+type: pipeline_definition
+category: rendering
+
+meta:
+  pipeline_id: WEBVIEW_TEXTUREVIEW_CUSTOM
+  display_name: "WebView TextureView (定制内核)"
+  description: "X5/UC 等定制 WebView 内核，使用 TextureView"
+  icon: "web"
+  family: webview
+  doc_path: "rendering_pipelines/webview_textureview_custom.md"
+  # ----- Article-grounded signature (S09 + S04) -----
+  s_article_ref: "S09"
+  four_features:
+    producer_threads: ["WebViewCore", "X5*", "UCCore*", "TBS*"]
+    consumer_threads: ["RenderThread"]
+    expected_layer_count: 1   # 网页内容回宿主，单 layer
+    bufferqueue_path: "CUSTOM_KERNEL_TO_SURFACETEXTURE_TO_HOST_BBQ"   # 定制内核 → SurfaceTexture → 宿主 RT updateTexImage
+    extra_rhythm_sources: ["custom_kernel_rhythm"]
+  deviation_anchors: "custom_kernel_to_host_resample_anchor_5"
+  # 锚点偏离：与 FLUTTER_TEXTUREVIEW 类似，但 Producer 是国内定制内核（X5/UC/TBS）。
+  # 内核可能有自己的渲染优化策略，但整体仍是 SurfaceTexture producer + 宿主侧再次合成 的架构。
+  custom_kernels: |
+    国内常见定制内核：
+    - 腾讯 X5 / TBS（QQ、微信、QQ 浏览器）
+    - 阿里 UCCore（UC 浏览器、夸克、支付宝）
+    - 百度 ZeusCore（百度 App）
+  subvariants_note: "文章 S09 列出的 5 种 WebView 路径之一（参 webview_gl_functor 注释）。"
+
+detection:
+  scoring_signals:
+    - signal: has_tbs
+      slice_pattern: "*TBS*"
+      weight: 30
+    - signal: has_x5
+      slice_pattern: "*X5*"
+      weight: 30
+    - signal: has_uccore
+      slice_pattern: "*UCCore*"
+      weight: 20
+
+  exclude_if:
+    - thread: "1.ui"           # Flutter engine present → use Flutter pipeline
+
+teaching:
+  title: "WebView TextureView (定制内核) 渲染管线"
+  summary: |
+    使用腾讯 X5、UC 等第三方定制 WebView 内核，通常使用 TextureView
+    进行渲染。这些内核可能有自己的渲染优化策略，但整体上仍属于
+    “SurfaceTexture producer + 宿主侧再次合成”的架构；回调线程和消费线程实现差异很大。
+
+  mermaid: |
+    sequenceDiagram
+      participant Main as App (main)
+      participant RT as RenderThread
+      participant X5 as X5/UC Core
+      participant TV as TextureView
+      participant BQ as BufferQueue
+      participant VS as VSync-sf
+      participant SF as SurfaceFlinger
+
+      Note over Main,SF: 📍 自定义 WebView 内核 (X5/UC)
+      Main->>X5: 加载网页
+      activate X5
+      X5->>TV: 渲染到 TextureView
+      X5->>TV: queueBuffer / produce frame
+      deactivate X5
+
+      Main->>RT: syncFrameState
+      activate RT
+      RT->>RT: DrawFrame
+      RT->>RT: 绑定 TextureView 纹理
+      RT->>BQ: queueBuffer
+      deactivate RT
+
+      VS->>SF: 🔔 VSync-sf
+      activate SF
+      SF->>SF: latchBuffer
+      SF->>SF: HWC Composite
+      deactivate SF
+
+      Note over Main,SF: 🇨🇳 国内常见的第三方 WebView 方案
+  thread_roles:
+    - thread: main
+      role: "UI 集成"
+      description: "承载定制 WebView 的 Activity"
+    - thread: RenderThread
+      role: "纹理合成"
+      description: "将定制内核内容作为纹理合成"
+    - thread: WebViewCore
+      role: "定制内核渲染"
+      description: "X5/UC 等内核渲染线程（trace 中可能表现为 WebViewCore/CrRendererMain/其他专用线程）"
+
+  key_slices:
+    - name: "SurfaceTexture"
+      thread: any
+      description: "TextureView/SurfaceTexture 生产-消费链路"
+    - name: "updateTexImage (hint)"
+      thread: RenderThread
+      description: "消费侧更新纹理的常见提示信号"
+    - name: "syncFrameState"
+      thread: RenderThread
+      description: "宿主 UI 与 RenderThread 同步，驱动纹理合成"
+    - name: "DrawFrame"
+      thread: RenderThread
+      description: "宿主 RenderThread 合成 WebView 纹理并提交"
+
+auto_pin:
+  instructions:
+    # Time-ordered pinning (production -> transfer -> consume -> display)
+    - pattern: "^VSYNC-app$"
+      match_by: name
+      priority: 1
+      reason: "VSync (WebView 开始生产帧)"
+
+    - pattern: "^main(\\s+\\d+)?$"
+      match_by: name
+      priority: 2
+      reason: "UI 集成 (生产)"
+      expand: true  # 展开显示 Running 状态和 callstack
+      smart_filter:
+        enabled: true
+        description: "仅 Pin 活跃渲染进程的宿主主线程"
+
+    - pattern: "CrRendererMain|WebViewCore|UCCore|X5"
+      match_by: name
+      priority: 3
+      reason: "定制内核渲染 (生产/传输)"
+      smart_filter:
+        enabled: true
+        description: "仅 Pin 属于当前 app 的内核进程/线程（多 app trace 下减少噪音）"
+
+    - pattern: "SurfaceTexture|updateTexImage|onFrameAvailable"
+      match_by: name
+      priority: 3.5
+      reason: "SurfaceTexture (纹理生产-消费/出图关键)"
+
+    - pattern: "^RenderThread(\\s+\\d+)?$"
+      match_by: name
+      priority: 4
+      reason: "纹理合成 (传输)"
+      expand: true  # 展开显示 Running 状态和 callstack
+      smart_filter:
+        enabled: true
+        description: "仅 Pin 活跃渲染进程的 RenderThread"
+
+    - pattern: "^VSYNC-sf$"
+      match_by: name
+      priority: 5.5
+      reason: "VSync (SurfaceFlinger 消费/合成)"
+
+    - pattern: "^BufferTX"
+      match_by: name
+      priority: 6
+      reason: "BufferTX (SurfaceFlinger 事务)"
+
+    - pattern: "^[sS]urface[fF]linger"
+      match_by: name
+      priority: 7
+      reason: "SurfaceFlinger (最终合成/显示)"
+      main_thread_only: true
+
+analysis:
+  common_issues:
+    # ----- Article-grounded issues (S09 + S04) -----
+    - id: custom_kernel_invisible_to_aosp_optimizations
+      name: "AOSP 优化对定制内核失效"
+      description: |
+        AOSP WebView 优化（OOP-R / Viz / SurfaceControl）仅适用于 stock WebView。
+        X5/UC/TBS 等定制内核不走这些路径，性能特征与 stock 完全不同——分析时不要套用 stock 经验。
+      detection_skill: cpu_analysis
+
+    - id: textureview_resample_overhead
+      name: "宿主 RT updateTexImage + GPU 重采样开销"
+      description: |
+        定制内核走 TextureView 路径，所有 S04 TextureView 的代价都适用：updateTexImage acquire、
+        GPU 重采样、YUV→RGB 色彩转换、acquire/release 双层 fence。
+      detection_skill: gpu_render_in_range
+
+    - id: kernel_thread_naming_unstable
+      name: "定制内核线程名不稳定"
+      description: |
+        X5/UC/TBS 定制内核的线程名随版本变化大（X5_GLBackbufferThread / TbsRenderThread / UCRenderingThread 等）。
+        Trace 中识别需要交叉用 process name + slice 名 pattern。
+      detection_skill: cpu_analysis
+
+  recommended_skills:
+    - render_thread_slices
+    - cpu_analysis

package/skills/vendors/honor/startup.override.yaml

@@ -0,0 +1,117 @@
+# SPDX-License-Identifier: AGPL-3.0-or-later
+# Copyright (C) 2024-2026 Gracker (Chris)
+# This file is part of SmartPerfetto. See LICENSE for details.
+
+# =============================================================================
+# Honor MagicOS 启动分析覆盖配置
+# =============================================================================
+# 版本: 1.0.0
+# 基于: composite/startup_analysis
+# 适用: 荣耀设备 (MagicOS)
+# =============================================================================
+
+extends: composite/startup_analysis
+version: "1.0.0"
+
+meta:
+  display_name: "Honor MagicOS 启动分析"
+  description: "针对荣耀 MagicOS 优化的启动分析，包含 TurboX 检测"
+  vendor: honor
+  os: MagicOS
+
+# -----------------------------------------------------------------------------
+# 厂商检测规则
+# -----------------------------------------------------------------------------
+vendor_detection:
+  signatures:
+    - pattern: "*MagicOS*"
+      confidence: high
+    - pattern: "*Honor*"
+      confidence: high
+    - pattern: "*honor*"
+      confidence: high
+    - pattern: "*TurboX*"
+      confidence: high
+    - pattern: "*Magic*"
+      confidence: medium
+
+# -----------------------------------------------------------------------------
+# 额外分析步骤
+# -----------------------------------------------------------------------------
+additional_steps:
+  # 检测 Honor 优化引擎
+  # NOTE: 使用子查询获取 ts，避免 JavaScript 大整数精度丢失问题
+  - id: honor_turbo_engine
+    name: "Honor TurboX 引擎检测"
+    description: "检查 GPU Turbo、Link Turbo 等优化是否生效"
+    for_each: startups
+    sql: |
+      SELECT
+        s.name as turbo_event,
+        s.dur / 1e6 as dur_ms,
+        (s.ts - (SELECT ts FROM android_startups WHERE startup_id = ${item.startup_id})) / 1e6 as relative_ts_ms
+      FROM slice s
+      WHERE (s.name GLOB '*TurboX*'
+             OR s.name GLOB '*GPUTurbo*'
+             OR s.name GLOB '*LinkTurbo*'
+             OR s.name GLOB '*MagicOS*'
+             OR s.name GLOB '*Honor*Boost*')
+        AND s.ts >= (SELECT ts FROM android_startups WHERE startup_id = ${item.startup_id})
+        AND s.ts <= (SELECT ts + dur FROM android_startups WHERE startup_id = ${item.startup_id})
+      ORDER BY s.ts ASC
+
+  # Honor 系统服务
+  # NOTE: 使用子查询获取 ts，避免 JavaScript 大整数精度丢失问题
+  - id: honor_system_services
+    name: "Honor 系统服务调用"
+    for_each: startups
+    sql: |
+      SELECT
+        server_process,
+        client_dur / 1e6 as dur_ms,
+        COUNT(*) as call_count
+      FROM android_binder_txns
+      WHERE client_process GLOB '${package}*'
+        AND (server_process GLOB '*honor*'
+             OR server_process GLOB '*Honor*'
+             OR server_process GLOB '*magic*')
+        AND client_ts >= (SELECT ts FROM android_startups WHERE startup_id = ${item.startup_id})
+        AND client_ts <= (SELECT ts + dur FROM android_startups WHERE startup_id = ${item.startup_id})
+      GROUP BY server_process
+      ORDER BY SUM(client_dur) DESC
+
+# -----------------------------------------------------------------------------
+# 覆盖判断标准
+# -----------------------------------------------------------------------------
+thresholds_override:
+  cold_start_time:
+    levels:
+      excellent: { max: 420 }
+      good: { min: 420, max: 850 }
+      warning: { min: 850, max: 1400 }
+      critical: { min: 1400 }
+
+# -----------------------------------------------------------------------------
+# 额外诊断规则
+# -----------------------------------------------------------------------------
+additional_diagnostics:
+  - id: turbo_not_active
+    condition: "honor_turbo_engine.count == 0"
+    severity: info
+    message: "未检测到 TurboX 加速"
+    suggestions:
+      - "检查应用是否支持 GPU Turbo"
+      - "联系 Honor 系统工程师确认优化策略"
+
+# -----------------------------------------------------------------------------
+# Honor 特有的 Trace Tag 参考
+# -----------------------------------------------------------------------------
+# MagicOS 系统:
+#   - MagicOS.* : MagicOS 系统相关
+#   - TurboX.* : TurboX 加速引擎
+#   - GPUTurbo : GPU 加速
+#   - LinkTurbo : 网络加速
+#
+# Honor 服务:
+#   - Honor.* : Honor 系统服务
+#   - Magic* : Magic 系列功能