@quicktvui/ai 1.1.19 → 1.1.20

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quicktvui/ai",
-  "version": "1.1.19",
+  "version": "1.1.20",
   "description": "QuickTVUI AI 开发规范与脚手架注入工具",
   "main": "index.js",
   "scripts": {

package/rules/.claude/commands/create-component.md

@@ -1,6 +1,6 @@
 ---
 name: create-component.md
-version: 1.1.19
+version: 1.1.20
 ---
 
 # 创建 QuickTVUI 组件

package/rules/.claude/commands/create-page.md

@@ -1,6 +1,6 @@
 ---
 name: create-page.md
-version: 1.1.19
+version: 1.1.20
 ---
 
 # 创建 TV 页面

package/rules/.claude/commands/create-project.md

@@ -1,6 +1,6 @@
 ---
 name: create-project.md
-version: 1.1.19
+version: 1.1.20
 ---
 
 # 创建 QuickTVUI 项目

package/rules/.claude/commands/lookup-api.md

@@ -1,6 +1,6 @@
 ---
 name: lookup-api.md
-version: 1.1.19
+version: 1.1.20
 ---
 
 # 查询 QuickTVUI 组件 API

package/rules/.claude/commands/lookup-css.md

@@ -1,6 +1,6 @@
 ---
 name: lookup-css.md
-version: 1.1.19
+version: 1.1.20
 ---
 
 # 查询 QuickTVUI CSS 属性

package/rules/.clinerules

@@ -79,9 +79,10 @@ Hard requirements:
   `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
 - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
 - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
-- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
+- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result via `quicktvui_runtime_status` / `quicktvui-ai runtime-status` when available, otherwise via logs or foreground activity status.
 - If user asks to launch a specific ES app/version/source, run:
   `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
+- After `run-esapp` or any other quick-app launch action, if the task is to confirm whether launch succeeded or whether the runtime reported an error, AI SHOULD query `quicktvui_runtime_status` / `quicktvui-ai runtime-status`.
 
 ## Runtime Debug Data Workflow (CRITICAL)
 

package/rules/.cursorrules

@@ -79,9 +79,10 @@ Hard requirements:
   `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
 - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
 - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
-- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
+- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result via `quicktvui_runtime_status` / `quicktvui-ai runtime-status` when available, otherwise via logs or foreground activity status.
 - If user asks to launch a specific ES app/version/source, run:
   `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
+- After `run-esapp` or any other quick-app launch action, if the task is to confirm whether launch succeeded or whether the runtime reported an error, AI SHOULD query `quicktvui_runtime_status` / `quicktvui-ai runtime-status`.
 
 ## Runtime Debug Data Workflow (CRITICAL)
 

package/rules/.github/copilot-instructions.md

@@ -1,6 +1,6 @@
 ---
 name: copilot-instructions.md
-version: 1.1.19
+version: 1.1.20
 ---
 
 # copilot-instructions.md - QuickTVUI AI Development Guide

package/rules/.windsurfrules

@@ -79,9 +79,10 @@ Hard requirements:
   `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
 - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
 - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
-- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
+- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result via `quicktvui_runtime_status` / `quicktvui-ai runtime-status` when available, otherwise via logs or foreground activity status.
 - If user asks to launch a specific ES app/version/source, run:
   `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
+- After `run-esapp` or any other quick-app launch action, if the task is to confirm whether launch succeeded or whether the runtime reported an error, AI SHOULD query `quicktvui_runtime_status` / `quicktvui-ai runtime-status`.
 
 ## Runtime Debug Data Workflow (CRITICAL)
 

package/rules/AGENTS.md

@@ -1,6 +1,6 @@
 ---
 name: AGENTS.md
-version: 1.1.19
+version: 1.1.20
 ---
 
 # AGENTS.md - QuickTVUI AI Development Guide
@@ -111,9 +111,10 @@ Hard requirements:
   `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
 - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
 - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
-- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
+- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from `quicktvui_runtime_status` / `quicktvui-ai runtime-status` when available, otherwise from logs or foreground activity status.
 - If user asks to launch a specific ES app/version/source, run:
   `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
+- After `run-esapp` or any other quick-app launch action, if the task is to confirm whether launch succeeded or whether the runtime reported an error, AI SHOULD query `quicktvui_runtime_status` / `quicktvui-ai runtime-status` before concluding success or failure.
 
 ## Runtime Debug Data Workflow (CRITICAL)
 
@@ -133,6 +134,7 @@ Required non-MCP command order:
 4. `quicktvui-ai debug-events --client-id <clientId> --limit 100`
 5. `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
 6. `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
+7. If the task is to confirm recent quick-app launch/load success or error state, `quicktvui-ai runtime-status --device <serial>` or MCP `quicktvui_runtime_status`
 
 Hard requirements:
 

package/rules/AI_HANDOFF.md

@@ -1,6 +1,6 @@
 ---
 name: AI_HANDOFF.md
-version: 1.1.19
+version: 1.1.20
 ---
 
 # QuickTVUI AI 集成 - 工作交接文档
@@ -84,6 +84,7 @@ AI 在编写业务逻辑时，极易带入传统 Web 开发习惯导致严重报
 - `debug-targets` 返回空数组时，应先回到 run/dev 链路，确认 `ESDebugServer /ai/targets` 已建立
 - `debug-screenshot` 默认会把图片写到 `<project>/.quicktvui-ai/debug-screenshots/`，后续 AI 应优先使用命令返回的 `savedTo` 路径
 - `debug-native-logs` 与 `debug-screenshot` 的失败信息应直接向用户透明披露，不要二次包装成模糊描述
+- 如果接手时正在排查 `run-dev`、`run-esapp`、`run_to_tv` 或其他快应用拉起后“到底有没有真正成功”这类问题，应优先补一份 `quicktvui_runtime_status` / `quicktvui-ai runtime-status` 快照，再下结论
 
 ## 插件服务工作流 (CRITICAL)
 

package/rules/CLAUDE.md

@@ -1,6 +1,6 @@
 ---
 name: CLAUDE.md
-version: 1.1.19
+version: 1.1.20
 ---
 
 # QuickTVUI - AI 开发指南
@@ -111,9 +111,10 @@ Hard requirements:
   `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
 - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
 - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
-- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
+- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result by first querying `quicktvui_runtime_status` / `quicktvui-ai runtime-status`; if that path is unavailable, fall back to logs or foreground activity status.
 - If user asks to launch a specific ES app/version/source, run:
   `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
+- `run-esapp` 或其他快应用拉起动作后，如果任务目标是确认是否拉起成功、是否有 runtime 报错，AI 也应优先补查 `quicktvui_runtime_status` / `quicktvui-ai runtime-status`。
 
 ## Runtime Debug Data Workflow (CRITICAL)
 
@@ -133,6 +134,7 @@ Hard requirements:
 4. `quicktvui-ai debug-events --client-id <clientId> --limit 100`
 5. `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
 6. `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
+7. 如果任务是确认最近一次快应用拉起 / 加载是否成功，或是否有 runtime 错误，还应补查 `quicktvui_runtime_status` / `quicktvui-ai runtime-status`
 
 硬约束：
 

package/rules/GEMINI.md

@@ -1,6 +1,6 @@
 ---
 name: GEMINI.md
-version: 1.1.19
+version: 1.1.20
 ---
 
 # GEMINI.md - QuickTVUI AI 开发指南
@@ -102,9 +102,10 @@ Hard requirements:
   `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
 - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
 - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
-- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
+- AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result via `quicktvui_runtime_status` / `quicktvui-ai runtime-status` when available, otherwise via logs or foreground activity status.
 - If user asks to launch a specific ES app/version/source, run:
   `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
+- After `run-esapp` or any other quick-app launch action, if the task is to confirm whether launch succeeded or whether the runtime reported an error, AI SHOULD query `quicktvui_runtime_status` / `quicktvui-ai runtime-status` before concluding success or failure.
 
 ## Runtime Debug Data Workflow (CRITICAL)
 
@@ -124,6 +125,7 @@ Required non-MCP order:
 4. `quicktvui-ai debug-events --client-id <clientId> --limit 100`
 5. `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
 6. `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
+7. If the task is to confirm recent quick-app launch/load success or runtime error state, also query `quicktvui_runtime_status` / `quicktvui-ai runtime-status`
 
 Hard requirements: