@quicktvui/ai 1.1.3 → 1.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (7) hide show
  1. package/package.json +1 -1
  2. package/rules/.clinerules +8 -0
  3. package/rules/.cursorrules +8 -0
  4. package/rules/.windsurfrules +8 -0
  5. package/rules/AGENTS.md +8 -0
  6. package/rules/CLAUDE.md +8 -0
  7. package/rules/GEMINI.md +8 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@quicktvui/ai",
3
- "version": "1.1.3",
3
+ "version": "1.1.5",
4
4
  "description": "QuickTVUI AI 开发规范与脚手架注入工具",
5
5
  "main": "index.js",
6
6
  "scripts": {
package/rules/.clinerules CHANGED
@@ -59,6 +59,14 @@ Hard requirements:
59
59
  - If multiple devices are connected, AI MUST ask user to choose target serial and MUST NOT silently pick one.
60
60
  - AI MUST verify the selected device is TV-like (`leanback`/`television` feature or TV characteristics). For phone/tablet devices, AI MUST ask user confirmation before continuing.
61
61
  - If runtime already exists on target device, AI MUST ask whether to reinstall/reset runtime before run.
62
+ - Before runtime launch, AI MUST verify the target runtime package exposes runtime-launch activity capability (expected activity: `eskit.sdk.core.ui.BrowserProxyActivity` with `android.intent.action.VIEW` + `esapp` scheme).
63
+ - Recommended check commands:
64
+ `adb -s <serial> shell cmd package resolve-activity -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -p <runtime-package>`
65
+ and fallback:
66
+ `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
67
+ - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
68
+ - 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.
69
+ - 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.
62
70
  - If user asks to launch a specific ES app/version/source, run:
63
71
  `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
64
72
 
package/rules/.cursorrules CHANGED
@@ -59,6 +59,14 @@ Hard requirements:
59
59
  - If multiple devices are connected, AI MUST ask user to choose target serial and MUST NOT silently pick one.
60
60
  - AI MUST verify the selected device is TV-like (`leanback`/`television` feature or TV characteristics). For phone/tablet devices, AI MUST ask user confirmation before continuing.
61
61
  - If runtime already exists on target device, AI MUST ask whether to reinstall/reset runtime before run.
62
+ - Before runtime launch, AI MUST verify the target runtime package exposes runtime-launch activity capability (expected activity: `eskit.sdk.core.ui.BrowserProxyActivity` with `android.intent.action.VIEW` + `esapp` scheme).
63
+ - Recommended check commands:
64
+ `adb -s <serial> shell cmd package resolve-activity -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -p <runtime-package>`
65
+ and fallback:
66
+ `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
67
+ - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
68
+ - 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.
69
+ - 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.
62
70
  - If user asks to launch a specific ES app/version/source, run:
63
71
  `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
64
72
 
package/rules/.windsurfrules CHANGED
@@ -59,6 +59,14 @@ Hard requirements:
59
59
  - If multiple devices are connected, AI MUST ask user to choose target serial and MUST NOT silently pick one.
60
60
  - AI MUST verify the selected device is TV-like (`leanback`/`television` feature or TV characteristics). For phone/tablet devices, AI MUST ask user confirmation before continuing.
61
61
  - If runtime already exists on target device, AI MUST ask whether to reinstall/reset runtime before run.
62
+ - Before runtime launch, AI MUST verify the target runtime package exposes runtime-launch activity capability (expected activity: `eskit.sdk.core.ui.BrowserProxyActivity` with `android.intent.action.VIEW` + `esapp` scheme).
63
+ - Recommended check commands:
64
+ `adb -s <serial> shell cmd package resolve-activity -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -p <runtime-package>`
65
+ and fallback:
66
+ `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
67
+ - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
68
+ - 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.
69
+ - 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.
62
70
  - If user asks to launch a specific ES app/version/source, run:
63
71
  `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
64
72
 
package/rules/AGENTS.md CHANGED
@@ -61,6 +61,14 @@ Hard requirements:
61
61
  - If multiple devices are connected, AI MUST ask user to choose target serial and MUST NOT silently pick one.
62
62
  - AI MUST verify the selected device is TV-like (`leanback`/`television` feature or TV characteristics). For phone/tablet devices, AI MUST ask user confirmation before continuing.
63
63
  - If runtime already exists on target device, AI MUST ask whether to reinstall/reset runtime before run.
64
+ - Before runtime launch, AI MUST verify the target runtime package exposes runtime-launch activity capability (expected activity: `eskit.sdk.core.ui.BrowserProxyActivity` with `android.intent.action.VIEW` + `esapp` scheme).
65
+ - Recommended check commands:
66
+ `adb -s <serial> shell cmd package resolve-activity -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -p <runtime-package>`
67
+ and fallback:
68
+ `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
69
+ - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
70
+ - 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.
71
+ - 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.
64
72
  - If user asks to launch a specific ES app/version/source, run:
65
73
  `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
66
74
 
package/rules/CLAUDE.md CHANGED
@@ -61,6 +61,14 @@ Hard requirements:
61
61
  - If multiple devices are connected, AI MUST ask user to choose target serial and MUST NOT silently pick one.
62
62
  - AI MUST verify the selected device is TV-like (`leanback`/`television` feature or TV characteristics). For phone/tablet devices, AI MUST ask user confirmation before continuing.
63
63
  - If runtime already exists on target device, AI MUST ask whether to reinstall/reset runtime before run.
64
+ - Before runtime launch, AI MUST verify the target runtime package exposes runtime-launch activity capability (expected activity: `eskit.sdk.core.ui.BrowserProxyActivity` with `android.intent.action.VIEW` + `esapp` scheme).
65
+ - Recommended check commands:
66
+ `adb -s <serial> shell cmd package resolve-activity -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -p <runtime-package>`
67
+ and fallback:
68
+ `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
69
+ - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
70
+ - 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.
71
+ - 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.
64
72
  - If user asks to launch a specific ES app/version/source, run:
65
73
  `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
66
74
 
package/rules/GEMINI.md CHANGED
@@ -53,6 +53,14 @@ Hard requirements:
53
53
  - If multiple devices are connected, AI MUST ask user to choose target serial and MUST NOT silently pick one.
54
54
  - AI MUST verify the selected device is TV-like (`leanback`/`television` feature or TV characteristics). For phone/tablet devices, AI MUST ask user confirmation before continuing.
55
55
  - If runtime already exists on target device, AI MUST ask whether to reinstall/reset runtime before run.
56
+ - Before runtime launch, AI MUST verify the target runtime package exposes runtime-launch activity capability (expected activity: `eskit.sdk.core.ui.BrowserProxyActivity` with `android.intent.action.VIEW` + `esapp` scheme).
57
+ - Recommended check commands:
58
+ `adb -s <serial> shell cmd package resolve-activity -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -p <runtime-package>`
59
+ and fallback:
60
+ `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
61
+ - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
62
+ - 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.
63
+ - 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.
56
64
  - If user asks to launch a specific ES app/version/source, run:
57
65
  `quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
58
66