@gracker/smartperfetto 1.0.19 → 1.0.21

package/skills/atomic/cpu_topology_detection.skill.yaml

@@ -5,204 +5,167 @@
 # =============================================================================
 # CPU 拓扑动态检测 (CPU Topology Detection)
 # =============================================================================
-# 从 cpufreq 最大值动态推断 CPU 集群类型
+# Public compatibility wrapper around cpu_topology_view.
 #
-# 背景：
-# - 现代 SoC 使用异构多核设计 (big.LITTLE, DynamIQ)
-# - 不同芯片的 CPU 拓扑差异很大：
-#   - Snapdragon 8 Gen 3: 2 小核 + 3 中核 + 1 Prime + 2 超大核
-#   - Dimensity 9300: 4 大核 + 4 超大核 (全大核设计)
-#   - Tensor G3: 4 小核 + 3 中核 + 1 大核
-#
-# 检测方法：
-# - 通过每个 CPU 核心的最大频率推断其类型
-# - 最高频率的 90%+ 归为 prime/big
-# - 60%-90% 归为 mid
-# - 60% 以下归为 little
+# Keep CPU topology inference centralized in `_cpu_topology`; do not maintain
+# another threshold-based classifier here. The shared view:
+# - builds the CPU universe from observed trace evidence first;
+# - ignores stale CPU table rows unless no observed CPU evidence exists;
+# - classifies common Android layouts such as 6+2, 4+3+1, 4+4, 4+2, 4-only,
+#   and 10-core tri-cluster layouts from capacity/frequency scale clusters;
+# - keeps unsupported/insufficient scale evidence explicit as `unknown`.
 # =============================================================================
 
 name: cpu_topology_detection
 version: "1.0"
-type: atomic
+type: composite
 category: hardware
 tier: B
 
 meta:
   display_name: "CPU 拓扑检测"
-  description: "从 cpufreq 动态检测 CPU 大小核拓扑"
+  description: "基于共享 _cpu_topology 视图检测 CPU 大小核拓扑"
   icon: "memory"
   tags: [cpu, topology, cluster, atomic]
 
-prerequisites:
-  required_tables:
-    - counter
-    - cpu_counter_track
-
 inputs:
   - name: start_ts
     type: timestamp
     required: false
-    description: "分析起始时间（可选）"
+    description: "分析起始时间（保留兼容；共享拓扑检测使用整条 trace 的观测证据）"
   - name: end_ts
     type: timestamp
     required: false
-    description: "分析结束时间（可选）"
+    description: "分析结束时间（保留兼容；共享拓扑检测使用整条 trace 的观测证据）"
 
 steps:
-  # Step 1: 检测每个 CPU 的最大频率
+  - id: init_cpu_topology
+    type: skill
+    name: "初始化 CPU 拓扑"
+    skill: cpu_topology_view
+    display:
+      level: hidden
+    optional: true
+
   - id: detect_cpu_clusters
     type: atomic
     name: "检测 CPU 集群"
     display:
       level: summary
+      layer: overview
       title: "CPU 拓扑检测结果"
+      columns:
+        - name: cpu
+          label: "CPU"
+          type: number
+        - name: cluster_type
+          label: "核心类型"
+          type: string
+        - name: max_freq_mhz
+          label: "Max Freq"
+          type: number
+        - name: capacity
+          label: "Capacity"
+          type: number
+        - name: topology_source
+          label: "判定来源"
+          type: string
+        - name: cluster_rank
+          label: "簇档位"
+          type: number
+        - name: cluster_count
+          label: "簇数量"
+          type: number
     sql: |
-      WITH
-      -- 获取时间范围
-      time_bounds AS (
-        SELECT
-          COALESCE(${start_ts}, (SELECT MIN(ts) FROM counter)) as start_ts,
-          COALESCE(${end_ts}, (SELECT MAX(ts) FROM counter)) as end_ts
-      ),
-      -- 获取每个 CPU 的最大频率
-      cpu_max_freq AS (
-        SELECT 
-          t.cpu,
-          MAX(c.value) as max_freq_khz,
-          MIN(c.value) as min_freq_khz,
-          AVG(c.value) as avg_freq_khz,
-          COUNT(*) as sample_count
-        FROM counter c
-        JOIN cpu_counter_track t ON c.track_id = t.id
-        WHERE t.name = 'cpufreq'
-          AND c.ts >= (SELECT start_ts FROM time_bounds)
-          AND c.ts <= (SELECT end_ts FROM time_bounds)
-        GROUP BY t.cpu
-      ),
-      -- 获取全局最大频率用于计算比例
-      global_max AS (
-        SELECT MAX(max_freq_khz) as global_max_freq FROM cpu_max_freq
-      ),
-      -- 根据最大频率比例推断集群类型
-      cpu_clusters AS (
-        SELECT 
-          cpu,
-          max_freq_khz,
-          min_freq_khz,
-          ROUND(max_freq_khz / 1000.0, 0) as max_freq_mhz,
-          ROUND(100.0 * max_freq_khz / (SELECT global_max_freq FROM global_max), 1) as freq_ratio_pct,
-          CASE
-            -- 最高频率的 90%+ 归为 prime (超大核)
-            WHEN max_freq_khz >= (SELECT global_max_freq FROM global_max) * 0.95 THEN 'prime'
-            -- 75%-95% 归为 big (大核)
-            WHEN max_freq_khz >= (SELECT global_max_freq FROM global_max) * 0.75 THEN 'big'
-            -- 50%-75% 归为 mid (中核)
-            WHEN max_freq_khz >= (SELECT global_max_freq FROM global_max) * 0.50 THEN 'mid'
-            -- 50% 以下归为 little (小核)
-            ELSE 'little'
-          END as cluster_type,
-          sample_count
-        FROM cpu_max_freq
-      )
       SELECT
-        cpu,
-        cluster_type,
-        max_freq_mhz,
-        freq_ratio_pct,
-        CASE cluster_type
+        cpu_id as cpu,
+        core_type as cluster_type,
+        CASE WHEN max_freq IS NULL THEN NULL ELSE ROUND(max_freq / 1000.0, 0) END as max_freq_mhz,
+        capacity,
+        topology_source,
+        cluster_rank,
+        cluster_count,
+        CASE core_type
           WHEN 'prime' THEN '超大核'
           WHEN 'big' THEN '大核'
-          WHEN 'mid' THEN '中核'
-          ELSE '小核'
+          WHEN 'medium' THEN '中核'
+          WHEN 'little' THEN '小核'
+          ELSE '未知'
         END as cluster_type_cn
-      FROM cpu_clusters
-      ORDER BY max_freq_khz DESC, cpu
+      FROM _cpu_topology
+      ORDER BY
+        CASE core_type
+          WHEN 'prime' THEN 1
+          WHEN 'big' THEN 2
+          WHEN 'medium' THEN 3
+          WHEN 'little' THEN 4
+          ELSE 5
+        END,
+        cpu_id
     save_as: cpu_clusters
 
-  # Step 2: 集群汇总
   - id: cluster_summary
     type: atomic
     name: "集群汇总"
     display:
       level: summary
+      layer: overview
       title: "CPU 集群汇总"
+      columns:
+        - name: cluster_type
+          label: "核心类型"
+          type: string
+        - name: cpu_count
+          label: "CPU 数"
+          type: number
+        - name: cpus
+          label: "CPU 列表"
+          type: string
+        - name: max_freq_mhz
+          label: "最高频率"
+          type: number
+        - name: min_freq_mhz
+          label: "最低频率"
+          type: number
+        - name: topology_source
+          label: "判定来源"
+          type: string
     sql: |
-      WITH
-      cpu_max_freq AS (
-        SELECT 
-          t.cpu,
-          MAX(c.value) as max_freq_khz
-        FROM counter c
-        JOIN cpu_counter_track t ON c.track_id = t.id
-        WHERE t.name = 'cpufreq'
-        GROUP BY t.cpu
-      ),
-      global_max AS (
-        SELECT MAX(max_freq_khz) as global_max_freq FROM cpu_max_freq
-      ),
-      cpu_clusters AS (
-        SELECT 
-          cpu,
-          max_freq_khz,
-          CASE
-            WHEN max_freq_khz >= (SELECT global_max_freq FROM global_max) * 0.95 THEN 'prime'
-            WHEN max_freq_khz >= (SELECT global_max_freq FROM global_max) * 0.75 THEN 'big'
-            WHEN max_freq_khz >= (SELECT global_max_freq FROM global_max) * 0.50 THEN 'mid'
-            ELSE 'little'
-          END as cluster_type
-        FROM cpu_max_freq
-      )
       SELECT
-        cluster_type,
+        core_type as cluster_type,
         COUNT(*) as cpu_count,
-        GROUP_CONCAT(cpu, ', ') as cpus,
-        ROUND(MAX(max_freq_khz) / 1000.0, 0) as max_freq_mhz,
-        ROUND(MIN(max_freq_khz) / 1000.0, 0) as min_freq_mhz,
-        CASE cluster_type
+        GROUP_CONCAT(cpu_id, ', ') as cpus,
+        CASE WHEN MAX(max_freq) IS NULL THEN NULL ELSE ROUND(MAX(max_freq) / 1000.0, 0) END as max_freq_mhz,
+        CASE WHEN MIN(max_freq) IS NULL THEN NULL ELSE ROUND(MIN(max_freq) / 1000.0, 0) END as min_freq_mhz,
+        GROUP_CONCAT(DISTINCT topology_source) as topology_source,
+        CASE core_type
           WHEN 'prime' THEN 1
           WHEN 'big' THEN 2
-          WHEN 'mid' THEN 3
-          ELSE 4
+          WHEN 'medium' THEN 3
+          WHEN 'little' THEN 4
+          ELSE 5
         END as cluster_order
-      FROM cpu_clusters
-      GROUP BY cluster_type
+      FROM _cpu_topology
+      GROUP BY core_type
       ORDER BY cluster_order
     save_as: cluster_summary
 
-  # Step 3: 导出供其他 skill 使用的集群映射
   - id: cluster_mapping
     type: atomic
     name: "集群映射"
     sql: |
-      WITH
-      cpu_max_freq AS (
-        SELECT 
-          t.cpu,
-          MAX(c.value) as max_freq_khz
-        FROM counter c
-        JOIN cpu_counter_track t ON c.track_id = t.id
-        WHERE t.name = 'cpufreq'
-        GROUP BY t.cpu
-      ),
-      global_max AS (
-        SELECT MAX(max_freq_khz) as global_max_freq FROM cpu_max_freq
-      )
       SELECT
-        cpu,
-        max_freq_khz,
+        cpu_id as cpu,
+        max_freq as max_freq_khz,
+        core_type as cluster_type,
         CASE
-          WHEN max_freq_khz >= (SELECT global_max_freq FROM global_max) * 0.95 THEN 'prime'
-          WHEN max_freq_khz >= (SELECT global_max_freq FROM global_max) * 0.75 THEN 'big'
-          WHEN max_freq_khz >= (SELECT global_max_freq FROM global_max) * 0.50 THEN 'mid'
-          ELSE 'little'
-        END as cluster_type,
-        -- 简化的 big/little 分类 (兼容旧逻辑)
-        CASE
-          WHEN max_freq_khz >= (SELECT global_max_freq FROM global_max) * 0.60 THEN 'big'
-          ELSE 'little'
-        END as simple_cluster_type
-      FROM cpu_max_freq
-      ORDER BY cpu
+          WHEN core_type IN ('prime', 'big', 'medium') THEN 'big'
+          WHEN core_type = 'little' THEN 'little'
+          ELSE 'unknown'
+        END as simple_cluster_type,
+        topology_source
+      FROM _cpu_topology
+      ORDER BY cpu_id
     save_as: cluster_mapping
 
 output:
@@ -214,20 +177,3 @@ output:
       description: "集群汇总（每种类型的核心数）"
     - name: cluster_mapping
       description: "集群映射表（供其他 skill 使用）"
-
-# =============================================================================
-# 使用示例
-# =============================================================================
-# 其他 skill 可以通过以下 CTE 使用动态检测的集群：
-#
-# WITH cpu_clusters AS (
-#   -- 复制 cluster_mapping 的 SQL
-# )
-# SELECT
-#   CASE 
-#     WHEN cpu IN (SELECT cpu FROM cpu_clusters WHERE cluster_type = 'prime') THEN 'prime'
-#     WHEN cpu IN (SELECT cpu FROM cpu_clusters WHERE cluster_type = 'big') THEN 'big'
-#     WHEN cpu IN (SELECT cpu FROM cpu_clusters WHERE cluster_type = 'mid') THEN 'mid'
-#     ELSE 'little'
-#   END as core_type
-# FROM ...

package/skills/atomic/cpu_topology_view.skill.yaml

@@ -194,6 +194,7 @@ steps:
         cs.scale_bucket,
         CASE
           WHEN cs.scale_bucket IS NULL OR cs.scale_bucket <= 0 THEN 'unknown'
+          WHEN sc.cluster_count <= 1 AND (SELECT COUNT(*) FROM cpu_scale) <= 4 THEN 'little'
           WHEN sc.cluster_count <= 1 THEN 'unknown'
           WHEN sc.cluster_count = 2 AND sc.cluster_rank = sc.cluster_count THEN 'big'
           WHEN sc.cluster_rank = 1 THEN 'little'
@@ -205,6 +206,7 @@ steps:
         END as core_type,
         CASE
           WHEN cs.scale_bucket IS NULL OR cs.scale_bucket <= 0 THEN cs.topology_source
+          WHEN sc.cluster_count <= 1 AND (SELECT COUNT(*) FROM cpu_scale) <= 4 THEN cs.topology_source || '_uniform_four_little'
           WHEN sc.cluster_count <= 1 THEN cs.topology_source || '_uniform'
           ELSE cs.topology_source
         END as topology_source,

package/skills/composite/device_state_snapshot.skill.yaml

@@ -0,0 +1,204 @@
+# SPDX-License-Identifier: AGPL-3.0-or-later
+# Copyright (C) 2024-2026 Gracker (Chris)
+# This file is part of SmartPerfetto. See LICENSE for details.
+
+# =============================================================================
+# 设备环境状态快照（组合 Skill）
+# =============================================================================
+# 采集指定窗口内的屏幕、电量、温度、频率、内存压力与 idle 状态。
+
+name: device_state_snapshot
+version: "2.0"
+type: composite
+category: system_context
+tier: B
+
+meta:
+  display_name: "设备环境状态快照"
+  description: "采集 trace 期间的设备环境信息（屏幕、电量、温度、CPU、内存、idle 窗口等）"
+  icon: "devices"
+  tags: [device, state, environment, context, composite]
+
+prerequisites:
+  required_tables:
+    - slice
+    - counter
+    - counter_track
+
+inputs:
+  - name: start_ts
+    type: timestamp
+    required: false
+    description: "分析起始时间戳(ns)"
+  - name: end_ts
+    type: timestamp
+    required: false
+    description: "分析结束时间戳(ns)"
+
+steps:
+  - id: environment_snapshot
+    type: atomic
+    name: "设备环境快照"
+    display:
+      level: summary
+      layer: overview
+      title: "设备环境状态"
+      columns:
+        - name: metric
+          label: "指标"
+          type: string
+        - name: value
+          label: "值"
+          type: string
+        - name: ts
+          label: "时间戳"
+          type: timestamp
+          unit: ns
+          clickAction: navigate_timeline
+    sql: |
+      WITH trace_bounds AS (
+        SELECT
+          COALESCE(${start_ts}, (SELECT MIN(ts) FROM slice)) as t_start,
+          COALESCE(${end_ts}, (SELECT MAX(ts + dur) FROM slice)) as t_end
+      ),
+      screen_state AS (
+        SELECT
+          'screen_state' as metric,
+          CASE WHEN c.value > 0 THEN 'ON' ELSE 'OFF' END as value,
+          c.ts as ts
+        FROM counter c
+        JOIN counter_track ct ON c.track_id = ct.id
+        CROSS JOIN trace_bounds tb
+        WHERE (ct.name GLOB '*ScreenState*' OR ct.name GLOB '*screen_state*')
+          AND c.ts >= tb.t_start AND c.ts <= tb.t_end
+        ORDER BY c.ts DESC
+        LIMIT 1
+      ),
+      battery_info AS (
+        SELECT
+          'battery_level' as metric,
+          CAST(c.value AS TEXT) as value,
+          c.ts as ts
+        FROM counter c
+        JOIN counter_track ct ON c.track_id = ct.id
+        CROSS JOIN trace_bounds tb
+        WHERE (ct.name GLOB '*battery_level*' OR ct.name GLOB '*BatteryLevel*')
+          AND c.ts >= tb.t_start AND c.ts <= tb.t_end
+        ORDER BY c.ts DESC
+        LIMIT 1
+      ),
+      charging_info AS (
+        SELECT
+          'charging_state' as metric,
+          CASE WHEN c.value > 0 THEN 'CHARGING' ELSE 'NOT_CHARGING' END as value,
+          c.ts as ts
+        FROM counter c
+        JOIN counter_track ct ON c.track_id = ct.id
+        CROSS JOIN trace_bounds tb
+        WHERE (ct.name GLOB '*battery_status*' OR ct.name GLOB '*charging*' OR ct.name GLOB '*BatteryStatus*')
+          AND c.ts >= tb.t_start AND c.ts <= tb.t_end
+        ORDER BY c.ts DESC
+        LIMIT 1
+      ),
+      thermal_info AS (
+        SELECT
+          'thermal_zone' as metric,
+          ct.name || ': ' || CAST(ROUND(MAX(CASE WHEN c.value > 1000 THEN c.value / 1000.0 ELSE c.value END), 1) AS TEXT) || ' C' as value,
+          MAX(c.ts) as ts
+        FROM counter c
+        JOIN counter_track ct ON c.track_id = ct.id
+        CROSS JOIN trace_bounds tb
+        WHERE (ct.name GLOB '*thermal_zone*' OR ct.name GLOB '*Temperature*' OR ct.name GLOB '*temp*')
+          AND c.ts >= tb.t_start AND c.ts <= tb.t_end
+        GROUP BY ct.name
+        ORDER BY MAX(c.value) DESC
+        LIMIT 5
+      ),
+      memory_info AS (
+        SELECT
+          'memory_pressure' as metric,
+          ct.name || ': ' || CAST(ROUND(MAX(c.value), 0) AS TEXT) as value,
+          MAX(c.ts) as ts
+        FROM counter c
+        JOIN counter_track ct ON c.track_id = ct.id
+        CROSS JOIN trace_bounds tb
+        WHERE (ct.name GLOB '*mem.*pressure*' OR ct.name GLOB '*MemFree*' OR ct.name GLOB '*MemAvailable*' OR ct.name GLOB '*psi*mem*')
+          AND c.ts >= tb.t_start AND c.ts <= tb.t_end
+        GROUP BY ct.name
+        ORDER BY MAX(c.value) DESC
+        LIMIT 5
+      )
+      SELECT metric, value, printf('%d', ts) as ts FROM screen_state
+      UNION ALL SELECT metric, value, printf('%d', ts) as ts FROM battery_info
+      UNION ALL SELECT metric, value, printf('%d', ts) as ts FROM charging_info
+      UNION ALL SELECT metric, value, printf('%d', ts) as ts FROM thermal_info
+      UNION ALL SELECT metric, value, printf('%d', ts) as ts FROM memory_info
+    save_as: environment_snapshot
+    synthesize:
+      role: overview
+      fields:
+        - key: metric
+          label: 指标
+        - key: value
+          label: 值
+
+  - id: idle_window_summary
+    type: atomic
+    name: "Idle 窗口摘要"
+    optional: true
+    display:
+      level: detail
+      layer: list
+      title: "Idle / 空闲窗口"
+      columns:
+        - name: start_ts
+          label: "开始"
+          type: timestamp
+          unit: ns
+          clickAction: navigate_timeline
+        - name: end_ts
+          label: "结束"
+          type: timestamp
+          unit: ns
+          clickAction: navigate_timeline
+        - name: dur_ms
+          label: "时长"
+          type: duration
+          unit: ms
+        - name: source
+          label: "来源"
+          type: string
+    sql: |
+      WITH trace_bounds AS (
+        SELECT
+          COALESCE(${start_ts}, (SELECT MIN(ts) FROM slice)) as t_start,
+          COALESCE(${end_ts}, (SELECT MAX(ts + dur) FROM slice)) as t_end
+      )
+      SELECT
+        printf('%d', s.ts) as start_ts,
+        printf('%d', s.ts + s.dur) as end_ts,
+        ROUND(s.dur / 1000000.0, 2) as dur_ms,
+        s.name as source
+      FROM slice s
+      CROSS JOIN trace_bounds tb
+      WHERE s.dur > 0
+        AND s.ts + s.dur > tb.t_start
+        AND s.ts < tb.t_end
+        AND (
+          s.name GLOB '*idle*'
+          OR s.name GLOB '*Idle*'
+          OR s.name GLOB '*suspend*'
+          OR s.name GLOB '*doze*'
+        )
+      ORDER BY s.dur DESC
+      LIMIT 20
+    save_as: idle_window_summary
+    synthesize:
+      role: list
+      fields:
+        - key: dur_ms
+          label: Idle 时长
+          format: "{{value}} ms"
+
+output:
+  format: structured

package/skills/composite/scene_reconstruction.skill.yaml

@@ -573,6 +573,9 @@ steps:
         - name: gesture_id
           label: "手势ID"
           type: number
+        - name: app_package
+          label: "前台应用"
+          type: string
         - name: category
           label: "类别"
           type: string
@@ -633,6 +636,7 @@ steps:
           ELSE ''
         END AS event,
         gesture_id,
+        app AS app_package,
         'scroll_start' AS category,
         '💡 此时刻手指已移动足够距离，系统开始响应滑动' AS explanation
       FROM scroll_starts
@@ -2785,4 +2789,4 @@ steps:
 
 output:
   format: layered
-  default_expanded: [L1, L2]
+  default_expanded: [L1, L2]

package/strategies/prompt-openai-final-report-continuation-en.template.md

@@ -8,7 +8,9 @@ Now output only the final report body. The first line must be `## Final Conclusi
 The report must include: final conclusion, key evidence chain, root-cause breakdown, ruled-out factors, recommendations, and confidence/limitations.
 
 Continue to obey the scene strategy, Final Report Contract, and latest next_phase_reminder constraints from this run. If the scene strategy or contract requires root-cause distributions, representative samples, phase-duration breakdowns, dual-audience recommendations, architecture branch judgments, or any other scene-specific structure, keep that structure in the final report instead of compressing it into a short summary.
+When the Final Report Contract names required items, prefer explicit matching sections or labels, for example "Phase Duration Breakdown", "[App Layer]", and "[System/Platform Layer]", instead of only implying those items inside prose.
+Output all structures required by the Final Report Contract before long trees, appendices, or expanded details. Do not place required recommendations, audience/layered recommendations, or limitations after a long code block or long tree where a truncated report could lose key conclusions.
 
 Do not merely restate phase summaries; synthesize the collected concrete values and evidence into a readable conclusion.
 
-Length target: about 1,200-1,800 English words. Use compact aggregation tables where helpful; do not expand into a phase-by-phase log, do not copy raw artifact tables, do not output the data-source/evidence-table index because the system will generate it, and do not repeat raw SQL. When evidence is abundant, prioritize the key evidence chain, structures required by the scene contract, and the highest-priority root causes.
+Prioritize completeness. Use compact aggregation tables where helpful; do not expand into a phase-by-phase log, do not copy raw artifact tables, do not output the data-source/evidence-table index because the system will generate it, and do not repeat raw SQL. When evidence is abundant, prioritize the key evidence chain, structures required by the scene contract, and the highest-priority root causes; do not omit key conclusions or evidence just to shorten the report.

package/strategies/prompt-openai-final-report-continuation-zh.template.md

@@ -8,7 +8,9 @@
 报告必须包含：综合结论、关键证据链、根因拆解、已排除因素、优化建议、置信度/限制。
 
 必须继续遵守本轮场景策略、Final Report Contract 和最后一个 next_phase_reminder 的输出约束。若场景策略或契约要求根因分布、代表样本、阶段耗时拆分、双受众建议、架构分支判断或其他专属结构，最终报告必须保留这些结构，不能降级为短摘要。
+如果 Final Report Contract 给出了必检项名称，优先用同名小节或清晰标签呈现，例如“阶段耗时分解”、“[App层]”、“[系统/平台层]”，避免只把契约内容隐含在叙述里。
+先输出 Final Report Contract 要求的必需结构，再输出长树状图、附录或扩展说明；不要把必需的优化建议、分层建议、限制说明放在长代码块或长树之后，以免报告中途截断时缺失关键结论。
 
 不要只复述阶段摘要；必须把已采集到的具体数值和证据串成可读结论。
 
-长度目标：约 2500-3500 个中文字符。可以用小型聚合表压缩信息；不要展开逐阶段流水账，不要复制 artifact 原表，不要重复 SQL 原文，不要输出“数据来源索引/证据表索引”（系统会自动生成）。若证据很多，优先保留关键证据链、场景契约要求的结构和最高优先级根因。
+完整性优先。可以用小型聚合表压缩信息；不要展开逐阶段流水账，不要复制 artifact 原表，不要重复 SQL 原文，不要输出“数据来源索引/证据表索引”（系统会自动生成）。若证据很多，优先保留关键证据链、场景契约要求的结构和最高优先级根因，不要为了压缩长度裁剪关键结论或证据。

package/strategies/prompt-output-format.template.md

@@ -84,7 +84,7 @@ graph LR
 ```
 
 ### 结论结构
-结论必须完整但克制：优先输出能支撑决策的证据链，避免把已经展示过的大表逐行搬进最终报告。中文目标长度控制在约 2500-3500 字符，英文目标长度控制在约 1200-1800 words；如果证据很多，用聚合表和证据索引压缩，不要生成会在 token 上限处截断的超长报告。
+结论必须完整但克制：优先输出能支撑决策的证据链，避免把已经展示过的大表逐行搬进最终报告。如果证据很多，用聚合表和证据索引压缩，降低重复信息密度；不要为了压缩长度裁剪关键结论或证据，也不要生成会在 token 上限处截断的超长报告。
 
 1. **概览**: 一句话总结性能状况。如果架构检测置信度 < 80%，在概览中标注（如"⚠️ 架构检测置信度 50%，分析策略可能不完全匹配"），帮助用户理解分析的局限性
 2. **关键发现**: 按严重程度排列的发现列表（含根因推理链 + 📚 背景知识）

package/strategies/scene-reconstruction-verifier.template.md

@@ -0,0 +1,18 @@
+<!-- SPDX-License-Identifier: AGPL-3.0-or-later -->
+<!-- Copyright (C) 2024-2026 Gracker (Chris) -->
+<!-- This file is part of SmartPerfetto. See LICENSE for details. -->
+
+你是 Android Perfetto trace 的场景还原复核器。请检查下面的 Smart 场景时间线是否存在明显的拆分、合并、类型或归因问题。
+
+只能基于输入证据判断，不要创造没有证据的场景。不要输出长报告。
+
+请只输出 JSON，格式：{"status":"passed|needs_review","summary":"一句中文复核意见"}。
+
+deterministic_summary:
+{{deterministicSummary}}
+
+deterministic_issues:
+{{deterministicIssues}}
+
+scenes:
+{{scenes}}

package/strategies/scrolling.strategy.md

@@ -107,7 +107,7 @@ phase_hints:
     critical: false
   - id: conclusion
     keywords: ['结论', 'conclusion', '输出', 'output', '报告', 'report', '总结']
-    constraints: '输出必须包含：全帧根因分布表（按 reason_code 聚合）+ 代表帧分析（含四象限+频率+根因推理链）+ 按优先级排序的优化建议。每个 CRITICAL/HIGH 必须有量化证据+因果链。'
+    constraints: '输出必须包含：全帧根因分布表（按 reason_code 聚合）+ 代表帧分析（含四象限+频率+根因推理链）+ 按优先级排序的优化建议。每个 CRITICAL/HIGH 必须有量化证据+因果链。若深钻证据纠正了 batch reason_code（例如 lock_binder_wait 但 binder_overlap_ms=0，render_slices_json 指向 cache_miss/makePipeline/shader 编译），最终结论必须使用纠正后的根因命名，并明确标注原 reason_code 为误分类。'
     critical_tools: []
     critical: false
 
@@ -347,6 +347,10 @@ Phase 1 的 `batch_frame_root_cause` 已包含每帧的**完整统计数据**（
 - **reason_code 为 unknown 且帧数 >5%**：必须对至少 1 帧调用 jank_frame_detail 获取更多线索，不能在分布表中仅标记"未分类"就跳过
 - reason_code 与实际数据矛盾时（如 `lock_binder_wait` 但 Binder 耗时 0ms）：应在结论中标注可能的误分类原因
 
+如果深钻结果已给出更具体的根因，不要在最终报告继续把原始 `reason_code` 当作根因名称。典型例子：
+- `lock_binder_wait` 但 `binder_overlap_ms=0`，且 `render_slices_json` 出现 `cache_miss: makePipeline` / shader 编译 / Vulkan finish frame / `postAndWait`，最终根因应写成 **shader_compile + sync_wait** 或等价机制，并说明 `lock_binder_wait` 是批量分类误判。
+- `workload_heavy` 但 `main_slices_json` 明确指向应用自定义方法，最终根因应写具体方法名和所处阶段，例如 `CustomScroll_longFrameLoad` 在 ANIMATION 回调同步执行，而不是只写 "workload_heavy"。
+
 `frame_blocking_calls` 是 Phase 1.9 的帧内阻塞证据补充，不占 `jank_frame_detail` 的 2 帧上限。遇到 Binder/IO/futex/锁相关根因时，优先用它确认阻塞调用是否真的与掉帧帧重叠。
 
 ```