@gracker/smartperfetto 1.0.13

package/skills/pipelines/hardware_buffer_renderer.skill.yaml

@@ -0,0 +1,205 @@
+# SPDX-License-Identifier: AGPL-3.0-or-later
+# Copyright (C) 2024-2026 Gracker (Chris)
+# This file is part of SmartPerfetto. See LICENSE for details.
+
+# =============================================================================
+# Hardware Buffer Renderer Pipeline
+# =============================================================================
+# Android 14+ HardwareBufferRenderer API.
+# Direct buffer rendering without SurfaceView overhead.
+# =============================================================================
+
+name: pipeline_hardware_buffer_renderer
+version: "1.0"
+type: pipeline_definition
+category: rendering
+
+meta:
+  pipeline_id: HARDWARE_BUFFER_RENDERER
+  display_name: "HardwareBufferRenderer"
+  description: "Android 14+ HBR API，直接 Buffer 渲染"
+  icon: "memory"
+  family: specialized
+  doc_path: "rendering_pipelines/hardware_buffer_renderer.md"
+  # ----- Article-grounded signature (S07 OFFSCREEN_HARDWAREBUFFER 子变种) -----
+  s_article_ref: "S07"
+  four_features:
+    producer_threads: ["main", "RenderThread"]
+    expected_layer_count: 0   # 离屏生产，可见时通过 SurfaceControl Transaction 直推
+    bufferqueue_path: "OFFSCREEN_HARDWAREBUFFER + SURFACECONTROL_TRANSACTION_DIRECT"
+    # ↑ 离屏 GPU 生产 HardwareBuffer → 直接通过 SurfaceControl.Transaction.setBuffer 提交（跳过 BBQ）
+    extra_rhythm_sources: []
+  deviation_anchors: "offscreen_hardwarebuffer_anchor_5_no_bbq_anchor_6"
+  # 锚点偏离：⑤ GPU 渲染到离屏 HardwareBuffer（不是宿主 buffer）；
+  # ⑥ 跳过标准 BBQ，直接通过 SurfaceControl.Transaction.setBuffer 进入 SF。
+  android_version: |
+    Android 14 AOSP 已存在但 @hide / @SystemApi；Android 15 / API 35 才正式公开。
+    Android 10-13 的离屏硬件渲染通常通过 HardwareRenderer + setSurface() 或 EGL 离屏 context + HardwareBuffer 组合实现。
+  subvariants_note: |
+    文章 S07 把 software/离屏拆为 4 子变种，HBR 对应：
+    OFFSCREEN_HARDWAREBUFFER（HardwareBufferRenderer 离屏 GPU，Android 14+/API 35）。
+    Phase E 拆 OFFSCREEN_BITMAP（离屏 Bitmap + 纹理上传）独立 ID。
+  no_bbq_implication: |
+    离屏结果直接通过 SurfaceControl.Transaction.setBuffer() 提交时跳过 BLASTBufferQueue。
+    Trace 上看不到这条 layer 的 BufferTX counter——要从 SF 进程 transaction 接收点和 layer latch 看，
+    不能按窗口提交习惯找 BBQ。S07 §"BufferQueue/queueBuffer/BufferTX 在这一类里怎么理解"。
+
+detection:
+  scoring_signals:
+    - signal: has_hardware_buffer_renderer
+      slice_pattern: "*HardwareBufferRenderer*"
+      weight: 55
+    - signal: has_ahardware_buffer_renderer
+      slice_pattern: "*AHardwareBufferRenderer*"
+      weight: 20
+    - signal: has_render_node
+      slice_pattern: "*RenderNode*"
+      weight: 15
+    - signal: has_recording_canvas
+      slice_pattern: "*RecordingCanvas*"
+      weight: 10
+
+teaching:
+  title: "HardwareBufferRenderer 渲染管线"
+  summary: |
+    Android 14+ 新增的 HardwareBufferRenderer API，提供 GPU 硬件加速的离屏渲染，
+    替代传统的 lockCanvas() CPU 软件渲染。
+
+    核心优势:
+    - GPU 光栅化代替 CPU Skia 软件渲染
+    - 直接渲染到 HardwareBuffer（是否零拷贝取决于后续合成/采样/拷贝链路）
+    - 可选择 wide-gamut/HDR 相关 buffer format（取决于设备与格式支持，如 RGBA_FP16 等）
+    - 显式 Fence 控制
+
+    典型使用场景:
+    - 自定义绘图引擎 (PDF 渲染器、矢量编辑器)
+    - HDR 图像处理
+    - 高帧率软件渲染
+
+  mermaid: |
+    sequenceDiagram
+      participant App as App
+      participant HBR as HardwareBufferRenderer
+      participant GPU as GPU
+      participant TX as Transaction
+      participant VS as VSync-sf
+      participant SF as SurfaceFlinger
+
+      Note over App,SF: 📍 HardwareBufferRenderer (Android 14+)
+      App->>HBR: create (HardwareBuffer)
+      activate HBR
+      HBR->>GPU: GPU 渲染到 HardwareBuffer
+      HBR->>HBR: 完成渲染
+      deactivate HBR
+
+      App->>TX: ASurfaceTransaction
+      App->>TX: setBuffer (HardwareBuffer)
+      TX->>SF: Transaction 提交
+
+      VS->>SF: 🔔 VSync-sf
+      activate SF
+      SF->>SF: setTransactionState
+      SF->>SF: latchBuffer
+      SF->>SF: HWC Composite
+      deactivate SF
+
+      Note over App,SF: 🆕 Android 14+ 新 API，无 SurfaceView 开销
+  thread_roles:
+    - thread: main
+      role: "HBR 控制"
+      description: "创建 HardwareBuffer，记录绘制命令"
+      trace_tags: "HardwareBufferRenderer, RenderNode, RecordingCanvas"
+    - thread: RenderThread
+      role: "GPU 光栅化"
+      description: "执行 RenderNode 的 GPU 渲染"
+      trace_tags: "DrawRenderNode, GpuRasterize"
+    - thread: SurfaceFlinger
+      role: "合成显示"
+      description: "等待 Fence，合成 HardwareBuffer"
+
+  key_slices:
+    - name: "HardwareBufferRenderer"
+      thread: main
+      description: "HBR 生命周期操作 (create/draw/close)"
+    - name: "obtainRenderRequest"
+      thread: main
+      description: "获取渲染请求"
+    - name: "RenderNode"
+      thread: main
+      description: "绘制命令容器"
+    - name: "RecordingCanvas"
+      thread: main
+      description: "记录绘制命令"
+    - name: "SyncFence"
+      thread: any
+      description: "GPU 完成同步 Fence"
+
+auto_pin:
+  instructions:
+    # Time-ordered pinning (production -> transfer -> consume -> display)
+    - pattern: "^VSYNC-app$"
+      match_by: name
+      priority: 1
+      reason: "VSync (开始生产帧)"
+
+    - pattern: "^main(\\s+\\d+)?$"
+      match_by: name
+      priority: 2
+      reason: "HBR 控制 (生产/传输)"
+      expand: true  # 展开显示 Running 状态和 callstack
+      smart_filter:
+        enabled: true
+        description: "仅 Pin 活跃渲染进程的主线程（避免 pin 到系统/其他 app 的 main）"
+
+    - 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: "最终合成/显示"
+      main_thread_only: true
+
+analysis:
+  common_issues:
+    - id: hbr_fence_not_awaited
+      name: "Fence 未正确等待"
+      description: "HBR submit 返回的 Fence 未等待即提交 Transaction"
+      detection_skill: present_fence_timing
+
+    - id: hbr_buffer_reuse
+      name: "Buffer 重用冲突"
+      description: "在 GPU 渲染完成前复用 HardwareBuffer"
+      detection_skill: gpu_analysis
+
+    - id: hbr_transaction_timing
+      name: "Transaction 提交时机不当"
+      description: "HBR 内容未同步到 VSync"
+      detection_skill: vsync_alignment_in_range
+
+    # ----- Article-grounded issues (S07) -----
+    - id: no_bufftx_counter_visible
+      name: "Trace 看不到该 layer 的 BufferTX"
+      description: |
+        HBR 直推 SurfaceControl.Transaction.setBuffer 时跳过 BBQ，trace 上看不到该 layer 的 BufferTX counter。
+        排查时要从 SF 进程 transaction 接收点和 layer latch 看，不能按 BLAST 窗口经验找。
+      detection_skill: sf_composition_in_range
+
+    - id: consumer_late_consume_offscreen_invisible_to_sf
+      name: "纯离屏场景 SF 看不到中间结果"
+      description: |
+        若 HBR 输出仅供编码/缓存等纯离屏消费，SF 完全看不到这份内容。
+        分析时要分别看"中间结果生产线程"和"最终消费者"，FrameTimeline 不适用。
+      detection_skill: gpu_render_in_range
+
+  recommended_skills:
+    - sf_frame_consumption
+    - gpu_analysis
+    - present_fence_timing

package/skills/pipelines/imagereader_pipeline.skill.yaml

@@ -0,0 +1,237 @@
+# SPDX-License-Identifier: AGPL-3.0-or-later
+# Copyright (C) 2024-2026 Gracker (Chris)
+# This file is part of SmartPerfetto. See LICENSE for details.
+
+# =============================================================================
+# ImageReader Pipeline
+# =============================================================================
+# ImageReader API 渲染管线 — 应用通过 ImageReader 获取渲染帧进行二次处理。
+# 常见于 ML 推理、屏幕录制、自定义相机处理和部分 Chrome 渲染模式。
+# ImageReader 可与其他管线共存（如 Camera、MediaCodec），不互斥。
+# =============================================================================
+
+name: pipeline_imagereader_pipeline
+version: "1.0"
+type: pipeline_definition
+category: rendering
+
+meta:
+  pipeline_id: IMAGEREADER_PIPELINE
+  display_name: "ImageReader 渲染管线"
+  description: "通过 ImageReader API 获取渲染帧的管线，常见于 ML 推理、屏幕录制、自定义相机处理和部分 Chrome 渲染模式"
+  icon: "image"
+  family: specialized
+  doc_path: "rendering_pipelines/imagereader_pipeline.md"
+  # ----- Article-grounded signature (S07 + S09 + S11 cross-cutting) -----
+  s_article_ref: "S07"   # ImageReader 是离屏消费者；S09 提到 WebView 罕见 ImageReader 路径；S11 提到 Camera 分析路径
+  four_features:
+    producer_threads: ["any (Camera HAL / MediaCodec / GPU / Chromium)"]
+    consumer_threads: ["ImageReader callback thread", "App thread (acquireNextImage)"]
+    expected_layer_count: 0   # ImageReader 是离屏消费者，不在 SF
+    bufferqueue_path: "BUFFERQUEUE_AS_CONSUMER"   # ImageReader 作为 BQ consumer，从 producer 收 buffer
+    extra_rhythm_sources: ["producer_rhythm"]
+  deviation_anchors: "cross_cutting_consumer_no_sf_anchor_7_to_12"
+  # ImageReader 是 cross-cutting 消费者，不属于独立 pipeline。可与 Camera/MediaCodec/GPU 任何 Producer 共存。
+  cross_cutting_nature: |
+    ImageReader 不是独立 pipeline——它是任何 Producer 的可选消费者。
+    可与 CAMERA_PIPELINE / VIDEO_OVERLAY_HWC / 任何渲染管线共存。
+    Detection 标志着"App 主动消费帧做二次处理"（ML 推理 / 屏幕录制 / 自定义 ISP / 帧分析）。
+  subvariants_note: |
+    文章 S11 把 Camera ImageReader 路径单列为 CAMERA_IMAGEANALYSIS_READER 子变种。
+    Phase E 评估是否拆分。
+
+# ==========================================================================
+# Detection Rules
+# ==========================================================================
+detection:
+  required_signals:
+    - slice_pattern: "*ImageReader*"
+      min_count: 1
+
+  scoring_signals:
+    - signal: has_acquire_next_image
+      slice_pattern: "*acquireNextImage*"
+      weight: 30
+    - signal: has_ndk_imagereader
+      slice_pattern: "*AImageReader*"
+      weight: 25
+    - signal: has_hardware_buffer
+      slice_pattern: "*HardwareBuffer*"
+      weight: 20
+    - signal: has_on_image_available
+      slice_pattern: "*onImageAvailable*"
+      weight: 20
+    - signal: has_queue_buffer
+      slice_pattern: "*queueBuffer*"
+      weight: 15
+    - signal: has_media_codec
+      slice_pattern: "*MediaCodec*"
+      weight: 10
+
+  # ImageReader can coexist with other pipelines — no exclusions needed
+
+# ==========================================================================
+# Teaching Content
+# ==========================================================================
+teaching:
+  title: "ImageReader 渲染管线"
+  summary: |
+    ImageReader 允许应用直接访问渲染到 Surface 的图像数据。它底层基于 BufferQueue，
+    作为 consumer 端从 producer（Camera HAL、MediaCodec 解码器、GPU 渲染等）获取帧。
+
+    典型使用场景：
+    - ML 推理：获取 Camera/GPU 帧进行实时模型推理
+    - 屏幕录制：捕获渲染帧编码为视频
+    - 自定义相机处理：Camera2 API + ImageReader 实现自定义 ISP
+    - 部分 Chrome 渲染模式：通过 ImageReader 获取合成帧
+
+    关键特征：
+    - Java API: `ImageReader.newInstance()` + `onImageAvailable` 回调
+    - NDK API: `AImageReader_new()` + `AImageReader_ImageListener`
+    - 与 HardwareBuffer 结合可实现零拷贝跨进程/跨 GPU 帧传递
+    - maxImages 参数控制 BufferQueue 深度，影响内存占用和延迟
+
+  mermaid: |
+    sequenceDiagram
+      participant P as Producer<br/>(Camera/GPU/Codec)
+      participant BQ as BufferQueue
+      participant IR as ImageReader
+      participant App as App (Consumer)
+      participant Proc as Processing<br/>(ML/Encode/Display)
+
+      Note over P,Proc: 📍 ImageReader 帧获取流程
+      P->>BQ: dequeueBuffer
+      P->>P: 渲染/解码/捕获
+      P->>BQ: queueBuffer (帧就绪)
+
+      BQ->>IR: onImageAvailable 回调
+      activate IR
+      IR->>App: 通知新帧可用
+      deactivate IR
+
+      activate App
+      App->>IR: acquireNextImage
+      IR->>BQ: acquireBuffer (获取帧)
+      IR-->>App: Image (HardwareBuffer)
+      App->>Proc: 处理帧 (ML 推理/编码/展示)
+      App->>IR: Image.close()
+      IR->>BQ: releaseBuffer
+      deactivate App
+
+      Note over P,Proc: ⏱️ 关键耗时点：queueBuffer→回调延迟、帧处理耗时、Buffer 释放速度
+
+  thread_roles:
+    - thread: main
+      role: "应用主线程"
+      description: "配置 ImageReader, 注册回调, 管理生命周期"
+      trace_tags: "bindApplication, activityStart, ImageReader"
+    - thread: ImageReader
+      role: "ImageReader 回调"
+      description: "处理 onImageAvailable 回调, 获取和释放 Image"
+      trace_tags: "ImageReader, onImageAvailable, acquireNextImage"
+    - thread: Producer
+      role: "帧生产者"
+      description: "帧生产线程 — 可以是 Camera HAL, MediaCodec 解码器, 或 GPU 渲染线程"
+      trace_tags: "Camera, MediaCodec, dequeueBuffer, queueBuffer"
+
+  key_slices:
+    - name: "acquireNextImage"
+      thread: any
+      description: "获取下一帧 Image — 从 BufferQueue 获取渲染好的帧"
+    - name: "onImageAvailable"
+      thread: any
+      description: "帧可用回调 — ImageReader 通知应用有新帧"
+    - name: "queueBuffer"
+      thread: any
+      description: "提交 Buffer — 生产者将渲染好的帧提交到 BufferQueue"
+    - name: "HardwareBuffer"
+      thread: any
+      description: "硬件 Buffer 操作 — GPU/Camera/Codec 直接读写"
+
+# ==========================================================================
+# Auto Pin Configuration
+# ==========================================================================
+auto_pin:
+  instructions:
+    - pattern: "^main(\\s+\\d+)?$"
+      match_by: name
+      priority: 1
+      reason: "App 主线程 (配置 ImageReader)"
+      expand: true
+      smart_filter:
+        enabled: true
+        description: "仅 Pin 活跃渲染进程的主线程"
+
+    - pattern: "ImageReader"
+      match_by: name
+      priority: 2
+      reason: "ImageReader 回调线程 (帧获取)"
+      expand: true
+
+    - pattern: "Camera"
+      match_by: name
+      priority: 3
+      reason: "Camera 服务 (帧生产者)"
+
+    - pattern: "MediaCodec"
+      match_by: name
+      priority: 4
+      reason: "MediaCodec 解码 (帧生产者)"
+
+    - 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 Configuration
+# ==========================================================================
+analysis:
+  common_issues:
+    - id: buffer_backpressure
+      name: "ImageReader Buffer 积压"
+      description: "acquireNextImage 获取帧速度跟不上生产速度，导致 BufferQueue 满"
+      detection_skill: gpu_analysis
+
+    - id: callback_heavy
+      name: "onImageAvailable 回调耗时"
+      description: "回调中做了重计算 (ML 推理), 阻塞后续帧获取"
+      detection_skill: cpu_analysis
+
+    - id: cross_process_delay
+      name: "HardwareBuffer 跨进程传递延迟"
+      description: "当 producer 和 consumer 在不同进程时，Buffer 传递延迟增大"
+      detection_skill: binder_analysis
+
+    # ----- Article-grounded issues (S11 Camera ImageReader 路径) -----
+    - id: imagereader_back_pressures_camera_hal
+      name: "ImageReader 回压 Camera HAL"
+      description: |
+        Camera 多路输出场景下，App 不及时 Image.close() 导致 ImageReader pool 满。
+        backward pressure 经 BufferQueue 传到 HAL，HAL 拿不到 buffer slot 让 capture pipeline 整体停摆。
+        分析时要看 acquireNextImage 频率与 close() 频率是否匹配。S11 §"buffer 回收压力"。
+      detection_skill: gpu_render_in_range
+
+    - id: maximages_too_low
+      name: "ImageReader maxImages 配置过小"
+      description: |
+        maxImages 决定 BufferQueue 深度，过小会触发 producer 频繁阻塞。
+        典型经验：ML 推理场景 maxImages >= 2；高吞吐场景 >= 4。但越大越占内存。
+      detection_skill: memory_analysis
+
+  recommended_skills:
+    - gpu_analysis
+    - memory_analysis
+    - binder_analysis
+    - cpu_analysis

package/skills/pipelines/index.yaml

@@ -0,0 +1,122 @@
+# SPDX-License-Identifier: AGPL-3.0-or-later
+# Copyright (C) 2024-2026 Gracker (Chris)
+# This file is part of SmartPerfetto. See LICENSE for details.
+
+# =============================================================================
+# Pipeline Skills Index
+# =============================================================================
+# Lists all available pipeline definitions for quick lookup.
+#
+# Pipeline Families:
+#   - hwui: Standard Android View system (HWUI/RenderThread)
+#   - surface: Surface-based rendering (SurfaceView, TextureView)
+#   - graphics: Graphics API rendering (OpenGL ES, Vulkan, ANGLE)
+#   - flutter: Flutter framework
+#   - webview: WebView/Chromium
+#   - specialized: Game engines, Camera, Video, etc.
+# =============================================================================
+
+version: "1.1"
+description: "Pipeline skills index - 31 rendering pipeline types (Phase E added React Native)"
+
+families:
+  hwui:
+    name: "HWUI Family"
+    description: "Standard Android View system using HWUI/RenderThread"
+    pipelines:
+      - ANDROID_VIEW_STANDARD_BLAST
+      - ANDROID_VIEW_STANDARD_LEGACY
+      - ANDROID_VIEW_SOFTWARE
+      - ANDROID_VIEW_MIXED
+      - ANDROID_VIEW_MULTI_WINDOW
+      - COMPOSE_STANDARD
+
+  surface:
+    name: "Surface-Based"
+    description: "SurfaceView, TextureView, and SurfaceControl patterns"
+    pipelines:
+      - ANDROID_PIP_FREEFORM
+      - SURFACEVIEW_BLAST
+      - TEXTUREVIEW_STANDARD
+      - SURFACE_CONTROL_API
+
+  graphics:
+    name: "Graphics APIs"
+    description: "Direct graphics API usage (OpenGL ES, Vulkan, ANGLE)"
+    pipelines:
+      - OPENGL_ES
+      - VULKAN_NATIVE
+      - ANGLE_GLES_VULKAN
+
+  flutter:
+    name: "Flutter"
+    description: "Flutter framework rendering"
+    pipelines:
+      - FLUTTER_SURFACEVIEW_IMPELLER
+      - FLUTTER_SURFACEVIEW_SKIA
+      - FLUTTER_TEXTUREVIEW
+
+  webview:
+    name: "WebView/Chromium"
+    description: "WebView/Chromium rendering modes (including standalone Chrome)"
+    pipelines:
+      - CHROME_BROWSER_VIZ
+      - WEBVIEW_GL_FUNCTOR
+      - WEBVIEW_SURFACE_CONTROL
+      - WEBVIEW_SURFACEVIEW_WRAPPER
+      - WEBVIEW_TEXTUREVIEW_CUSTOM
+
+  react_native:
+    name: "React Native"
+    description: "React Native (S14): Old Arch Bridge / New Arch Fabric / Skia self-draw"
+    pipelines:
+      - RN_OLD_ARCH_HWUI
+      - RN_NEW_ARCH_HWUI
+      - RN_SKIA_RENDERER
+
+  specialized:
+    name: "Specialized"
+    description: "Game engines, Camera, Video, VRR, etc."
+    pipelines:
+      - GAME_ENGINE
+      - CAMERA_PIPELINE
+      - VIDEO_OVERLAY_HWC
+      - HARDWARE_BUFFER_RENDERER
+      - VARIABLE_REFRESH_RATE
+      - IMAGEREADER_PIPELINE
+      - SOFTWARE_COMPOSITING
+
+# Quick lookup: pipeline_id -> skill file
+pipeline_files:
+  ANDROID_VIEW_STANDARD_BLAST: android_view_standard_blast.skill.yaml
+  ANDROID_VIEW_STANDARD_LEGACY: android_view_standard_legacy.skill.yaml
+  ANDROID_VIEW_SOFTWARE: android_view_software.skill.yaml
+  ANDROID_VIEW_MIXED: android_view_mixed.skill.yaml
+  ANDROID_VIEW_MULTI_WINDOW: android_view_multi_window.skill.yaml
+  ANDROID_PIP_FREEFORM: android_pip_freeform.skill.yaml
+  SURFACEVIEW_BLAST: surfaceview_blast.skill.yaml
+  TEXTUREVIEW_STANDARD: textureview_standard.skill.yaml
+  SURFACE_CONTROL_API: surface_control_api.skill.yaml
+  OPENGL_ES: opengl_es.skill.yaml
+  VULKAN_NATIVE: vulkan_native.skill.yaml
+  ANGLE_GLES_VULKAN: angle_gles_vulkan.skill.yaml
+  FLUTTER_SURFACEVIEW_IMPELLER: flutter_surfaceview_impeller.skill.yaml
+  FLUTTER_SURFACEVIEW_SKIA: flutter_surfaceview_skia.skill.yaml
+  FLUTTER_TEXTUREVIEW: flutter_textureview.skill.yaml
+  WEBVIEW_GL_FUNCTOR: webview_gl_functor.skill.yaml
+  WEBVIEW_SURFACE_CONTROL: webview_surface_control.skill.yaml
+  WEBVIEW_SURFACEVIEW_WRAPPER: webview_surfaceview_wrapper.skill.yaml
+  WEBVIEW_TEXTUREVIEW_CUSTOM: webview_textureview_custom.skill.yaml
+  GAME_ENGINE: game_engine.skill.yaml
+  CAMERA_PIPELINE: camera_pipeline.skill.yaml
+  VIDEO_OVERLAY_HWC: video_overlay_hwc.skill.yaml
+  HARDWARE_BUFFER_RENDERER: hardware_buffer_renderer.skill.yaml
+  COMPOSE_STANDARD: compose_standard.skill.yaml
+  VARIABLE_REFRESH_RATE: variable_refresh_rate.skill.yaml
+  IMAGEREADER_PIPELINE: imagereader_pipeline.skill.yaml
+  CHROME_BROWSER_VIZ: chrome_browser_viz.skill.yaml
+  SOFTWARE_COMPOSITING: software_compositing.skill.yaml
+  # ----- Phase E: React Native (S14) -----
+  RN_OLD_ARCH_HWUI: rn_old_arch.skill.yaml
+  RN_NEW_ARCH_HWUI: rn_new_arch.skill.yaml
+  RN_SKIA_RENDERER: rn_skia.skill.yaml