@buaa_smat/hometrans 0.1.15 → 0.1.17

package/dist/cli/uninstall.js

@@ -22,9 +22,19 @@ import { removeEnvVars } from './env-vars.js';
 const execFileAsync = promisify(execFile);
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
-/** Names + readable count of env vars that have a non-empty value in config. */
-function plannedEnvVarNames(env) {
-    return MACHINE_ENV_KEYS.filter((k) => (env[k] ?? '').trim().length > 0);
+/**
+ * Global Node CLIs that `ht init` installs as a pair (`npm install -g homegraph
+ * arkanalyzer`). `ht uninstall` removes the same pair so the two commands stay
+ * symmetric.
+ */
+const NODE_DEPS = ['homegraph', 'arkanalyzer'];
+/**
+ * Machine env var names that `ht init` may have set and that have a non-empty
+ * value in config.env: the SDK paths / tool dir plus the mirrored unified model
+ * fields (HOMETRANS_MODEL_*, kept in sync with autotest.unified_model on load).
+ */
+function plannedEnvVarNames(config) {
+    return MACHINE_ENV_KEYS.filter((k) => (config.env[k] ?? '').trim().length > 0);
 }
 /* ------------------------------------------------------------------ */
 /*  Bundled content discovery                                          */
@@ -68,6 +78,57 @@ async function listBundledAgentEntries(agentsRoot) {
     }
 }
 /* ------------------------------------------------------------------ */
+/*  Global npm dependency removal                                      */
+/* ------------------------------------------------------------------ */
+/**
+ * Is `npm` runnable? On Windows the global npm bin is a `.cmd` shim, so the
+ * command must run through the shell there (same as init's homegraphVersion()).
+ */
+async function npmAvailable() {
+    try {
+        await execFileAsync('npm', ['--version'], {
+            timeout: 15000,
+            shell: process.platform === 'win32',
+        });
+        return true;
+    }
+    catch {
+        return false;
+    }
+}
+/**
+ * Does `homegraph --version` return normally (exit 0)? Used as the presence
+ * probe for the homegraph/arkanalyzer pair — the symmetric counterpart to
+ * init's idempotency check, which skips the install when homegraph is already
+ * present.
+ */
+async function homegraphInstalled() {
+    try {
+        await execFileAsync('homegraph', ['--version'], {
+            timeout: 15000,
+            shell: process.platform === 'win32',
+        });
+        return true;
+    }
+    catch {
+        return false;
+    }
+}
+/**
+ * Decide which global npm packages to remove. Returns the homegraph/arkanalyzer
+ * pair when homegraph is detected on the machine (mirroring init, which installs
+ * them together), or an empty list when npm is unavailable or homegraph is not
+ * present — so a machine that never ran `ht init`'s dependency install shows
+ * nothing to remove here.
+ */
+async function detectNodeDepsToRemove() {
+    if (!(await npmAvailable()))
+        return [];
+    if (!(await homegraphInstalled()))
+        return [];
+    return [...NODE_DEPS];
+}
+/* ------------------------------------------------------------------ */
 /*  MCP config removal helpers                                         */
 /* ------------------------------------------------------------------ */
 function detectIndentation(raw) {
@@ -299,6 +360,7 @@ function renderDiff(oldContent, newContent, context = 3) {
 function isPlanEmpty(plan) {
     return (plan.deletions.length === 0 &&
         plan.modifications.length === 0 &&
+        plan.npmDeps.length === 0 &&
         plan.envVars.length === 0 &&
         plan.configDir === null);
 }
@@ -325,6 +387,14 @@ function renderPlan(plan) {
             console.log('');
         }
     }
+    if (plan.npmDeps.length > 0) {
+        console.log(chalk.red.bold(`  Global npm packages to remove (${plan.npmDeps.length}):`));
+        console.log(chalk.gray(`    (will run: npm uninstall -g ${plan.npmDeps.join(' ')})`));
+        for (const dep of plan.npmDeps) {
+            console.log(`    ${chalk.red('-')} ${dep}`);
+        }
+        console.log('');
+    }
     if (plan.envVars.length > 0) {
         console.log(chalk.red.bold(`  Environment variables to remove (${plan.envVars.length}):`));
         console.log(chalk.gray(process.platform === 'win32'
@@ -347,6 +417,7 @@ function renderPlan(plan) {
 async function executePlan(plan) {
     let deleted = 0;
     let modified = 0;
+    let npmNote = null;
     let envNote = null;
     for (const mod of plan.modifications) {
         await fs.writeFile(mod.absPath, mod.newContent, 'utf-8');
@@ -362,6 +433,22 @@ async function executePlan(plan) {
             // codex CLI unavailable or failed — TOML path already handled above
         }
     }
+    // Remove the global npm CLIs installed by `ht init` (homegraph + arkanalyzer).
+    // Best-effort: a failure is reported in the note but never aborts the rest of
+    // the uninstall.
+    if (plan.npmDeps.length > 0) {
+        console.log(chalk.gray(`  Running: npm uninstall -g ${plan.npmDeps.join(' ')} ...`));
+        try {
+            await execFileAsync('npm', ['uninstall', '-g', ...plan.npmDeps], {
+                timeout: 5 * 60 * 1000,
+                shell: process.platform === 'win32',
+            });
+            npmNote = `removed ${plan.npmDeps.join(', ')}`;
+        }
+        catch (err) {
+            npmNote = `failed (${err.message}) — remove manually: npm uninstall -g ${plan.npmDeps.join(' ')}`;
+        }
+    }
     for (const del of plan.deletions) {
         try {
             await fs.rm(del.absPath, { recursive: true, force: true });
@@ -384,7 +471,7 @@ async function executePlan(plan) {
             // best-effort
         }
     }
-    return { deleted, modified, envNote };
+    return { deleted, modified, npmNote, envNote };
 }
 /* ------------------------------------------------------------------ */
 /*  Entry point                                                        */
@@ -398,20 +485,25 @@ export async function uninstallCommand() {
         console.log(chalk.gray('  Reinstall hometrans or manually remove skill/agent directories from your editors.\n'));
         return;
     }
-    const { editors, env } = await loadHomeTransConfig();
+    const config = await loadHomeTransConfig();
+    const { editors } = config;
     const plan = {
         deletions: [],
         modifications: [],
         codexRemove: false,
+        npmDeps: [],
         envVars: [],
         configDir: null,
     };
     for (const editor of editors) {
         await buildPlanForEditor(editor, skillNames, agentEntries, plan);
     }
-    // Env vars to remove come from config.json `env`; the ~/.hometrans dir
-    // (which holds config.json) is deleted last.
-    plan.envVars = plannedEnvVarNames(env);
+    // Global npm CLIs installed by `ht init` (homegraph + arkanalyzer) — detected
+    // the same way init decides whether to (re)install them.
+    plan.npmDeps = await detectNodeDepsToRemove();
+    // Env vars to remove come from config.json (`env` + the unified model
+    // fields); the ~/.hometrans dir (which holds config.json) is deleted last.
+    plan.envVars = plannedEnvVarNames(config);
     const configDir = getConfigDir();
     if (await dirExists(configDir)) {
         plan.configDir = configDir;
@@ -446,6 +538,9 @@ export async function uninstallCommand() {
     const summary = await executePlan(plan);
     console.log('');
     console.log(chalk.green(`  Uninstalled: ${summary.deleted} entries deleted, ${summary.modified} files modified.`));
+    if (summary.npmNote) {
+        console.log(chalk.green(`  Global npm packages: ${summary.npmNote}`));
+    }
     if (summary.envNote) {
         console.log(chalk.green(`  Environment variables: ${summary.envNote}`));
     }

package/dist/context/index.js

@@ -10,8 +10,25 @@ import {
 } from "arkanalyzer";
 
 // src/cli/config-store.ts
+import { readFileSync } from "node:fs";
 import path from "node:path";
 import os from "node:os";
+function getConfigDir() {
+  return path.join(os.homedir(), ".hometrans");
+}
+function getConfigPath() {
+  return path.join(getConfigDir(), "config.json");
+}
+function readConfigEnvFieldSync(key) {
+  try {
+    const raw = readFileSync(getConfigPath(), "utf-8");
+    const parsed = JSON.parse(raw);
+    const v = parsed?.env?.[key];
+    return typeof v === "string" ? v : "";
+  } catch {
+    return "";
+  }
+}
 function expandHome(p) {
   if (!p) return p;
   if (p === "~") return os.homedir();
@@ -594,10 +611,10 @@ async function extractCommitContext(input) {
   const { projectPath, commitId } = input;
   const mode = input.mode ?? "default";
   const ohosSdkPath = expandHome(
-    input.ohosSdkPath ?? process.env.OHOS_SDK_PATH ?? ""
+    input.ohosSdkPath || process.env.OHOS_SDK_PATH || readConfigEnvFieldSync("OHOS_SDK_PATH")
   );
   const hmsSdkPath = expandHome(
-    input.hmsSdkPath ?? process.env.HMS_SDK_PATH ?? ""
+    input.hmsSdkPath || process.env.HMS_SDK_PATH || readConfigEnvFieldSync("HMS_SDK_PATH")
   );
   if (!projectPath) {
     throw new Error("extractCommitContext: projectPath is required");

package/env-requirements.json

@@ -27,6 +27,7 @@
 
   "tools": {
     "deveco": {
+      "label": "harmony sdk",
       "source": "env-dir",
       "envVar": "DEVECO_SDK_HOME",
       "hint": "set DEVECO_SDK_HOME via `ht init` (DevEco Studio install)"
@@ -46,20 +47,12 @@
       "fallback": { "base": "DEVECO_SDK_HOME", "segments": ["default", "openharmony", "toolchains"], "exe": "hdc" },
       "hint": "ships with DevEco: <sdk>/default/openharmony/toolchains"
     },
-    "python": {
-      "source": "path",
-      "aliases": ["python", "python3", "py"],
-      "verify": ["--version"],
-      "versionRegex": "(\\d+\\.\\d+(?:\\.\\d+)?)",
-      "version": { "min": "3.10.0", "max": null },
-      "hint": "install Python >= 3.10 and add to PATH (UI-align capture/parse scripts)"
-    },
     "uv": {
       "source": "path",
       "aliases": ["uv"],
       "verify": ["--version"],
       "versionRegex": "(\\d+\\.\\d+(?:\\.\\d+)?)",
-      "hint": "https://docs.astral.sh/uv (AutoTest runs under uv)"
+      "hint": "https://docs.astral.sh/uv — runs every Python script (AutoTest, UI-align, logic) via `uv run` and provides Python ≥ 3.10 on demand (no standalone Python needed)"
     },
     "java": {
       "source": "path",
@@ -70,12 +63,12 @@
       "fallback": { "base": "DEVECO_HOME", "segments": ["jbr", "bin"], "exe": "java" },
       "hint": "any JDK 17+, or reuse DevEco jbr: <deveco>/jbr/bin"
     },
-    "gitnexus": {
+    "homegraph": {
       "source": "path",
-      "aliases": ["gitnexus"],
+      "aliases": ["homegraph"],
       "verify": ["--version"],
       "versionRegex": "(\\d+\\.\\d+(?:\\.\\d+)?)",
-      "hint": "npm i -g gitnexus && gitnexus setup"
+      "hint": "npm install -g homegraph arkanalyzer (code-graph backend for spec generation)"
     }
   },
 
@@ -83,7 +76,7 @@
     {
       "name": "hmos-spec-generate",
       "kind": "skill",
-      "dependencies": [{ "tool": "gitnexus", "level": "required" }]
+      "dependencies": [{ "tool": "homegraph", "level": "required" }]
     },
     {
       "name": "hmos-resources-convert",
@@ -95,20 +88,21 @@
       "name": "hmos-batch-ui-align",
       "kind": "skill",
       "dependencies": [
-        { "tool": "python", "level": "required", "version": { "min": "3.10.0", "max": null } },
+        { "tool": "uv", "level": "required" },
         { "tool": "adb", "level": "optional" }
       ],
-      "note": "adb only for page exploration"
+      "note": "android_parse_fast.py runs via `uv run` (uv provides Python); adb only for page exploration"
     },
     {
       "name": "hmos-incremental-ui-align",
       "kind": "skill",
       "dependencies": [
         { "tool": "deveco", "level": "required" },
-        { "tool": "python", "level": "required", "version": { "min": "3.10.0", "max": null } },
+        { "tool": "uv", "level": "required" },
         { "tool": "hdc", "level": "required" },
         { "tool": "adb", "level": "required" }
-      ]
+      ],
+      "note": "app_feature_verify.py / page_capture.py run via `uv run` (PEP 723 inline deps; uv provides Python)"
     },
     {
       "name": "hmos-integration-test",
@@ -117,7 +111,8 @@
         { "tool": "deveco", "level": "required" },
         { "tool": "uv", "level": "required" },
         { "tool": "hdc", "level": "required" }
-      ]
+      ],
+      "note": "self_test_runner.py runs via `uv run --no-project python` (uv provides Python) and then `uv sync`s the AutoTest venv"
     },
     {
       "name": "hmos-fix-build-errors",
@@ -132,22 +127,22 @@
         { "tool": "uv", "level": "optional" },
         { "tool": "hdc", "level": "optional" }
       ],
-      "note": "test stage skippable via skip_test"
+      "note": "test stage skippable via skip_test; when run it needs uv + hdc"
     },
     {
       "name": "logic-context-builder",
       "kind": "agent",
-      "dependencies": [{ "tool": "python", "level": "optional" }]
+      "dependencies": [{ "tool": "uv", "level": "optional" }]
     },
     {
       "name": "logic-coder",
       "kind": "agent",
-      "dependencies": [{ "tool": "python", "level": "optional" }]
+      "dependencies": [{ "tool": "uv", "level": "optional" }]
     },
     {
       "name": "spec-generator",
       "kind": "agent",
-      "dependencies": [{ "tool": "gitnexus", "level": "required" }]
+      "dependencies": [{ "tool": "homegraph", "level": "required" }]
     },
     {
       "name": "build-fixer",
@@ -170,7 +165,8 @@
       "dependencies": [
         { "tool": "uv", "level": "required" },
         { "tool": "hdc", "level": "required" }
-      ]
+      ],
+      "note": "invokes `uv run --no-project python self_test_runner.py run/status/kill` (uv provides Python; --no-project keeps the interpreter out of the .venv it rebuilds)"
     },
     {
       "name": "self-test-fixer",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@buaa_smat/hometrans",
-  "version": "0.1.15",
+  "version": "0.1.17",
   "description": "HomeTrans (Android-to-HarmonyOS) skill + agent installer. Run `ht init` to distribute conversion skills and subagents into AI editors.",
   "license": "MIT",
   "repository": {

package/skills/hmos-batch-ui-align/SKILL.md

@@ -9,13 +9,13 @@ Batch-convert a set of Android page snapshots (each snapshot is a `page_NNNN_Act
 
 ## Step 0 — Environment Variables Check (run first)
 
-The final build (Step 6, via `hmos_fix_build_errors`) reads the DevEco location **directly from the OS environment variables** (`echo "$VAR"` on macOS/Linux; `$env:VAR` in PowerShell on Windows):
+The final build (Step 6, via `hmos_fix_build_errors`) resolves the DevEco location along the standard chain — **OS environment variable first, then `~/.hometrans/config.json`, then ask the user** (read env vars with `echo "$VAR"` on macOS/Linux; `$env:VAR` in PowerShell on Windows):
 
-| Variable | Needed for | Valid when |
-|---|---|---|
-| `DEVECO_HOME` *(or `DEVECO_SDK_HOME`)* | Step 6 unified build | resolves to a valid DevEco install |
+| Variable | config.json fallback | Needed for | Valid when |
+|---|---|---|---|
+| `DEVECO_HOME` *(or `DEVECO_SDK_HOME`)* | `env.DEVECO_HOME` / `env.DEVECO_SDK_HOME` | Step 6 unified build | resolves to a valid DevEco install |
 
-If neither `DEVECO_HOME` nor `DEVECO_SDK_HOME` is set, **ask the user** for the DevEco Studio install path before proceeding (suggest running `ht init` to persist it as a machine environment variable).
+If neither the env var nor `~/.hometrans/config.json` yields a valid DevEco install, **ask the user** for the DevEco Studio install path before proceeding (suggest running `ht init` to persist it as a machine environment variable).
 
 ## Step 1 — Parse User Request
 
@@ -27,6 +27,7 @@ Extract 4 paths from the user's message (natural language, no fixed format):
 | `harmony_project_dir` | HarmonyOS target project root | "target Harmony project", "鸿蒙项目", "output project" |
 | `ui_info_root` | **Parent directory containing all `page_NNNN_*` subdirectories** | "page screenshots and view tree", "page snapshots", "page folder" |
 | `pages` (optional) | User-explicitly listed page subset | When user lists `1. .../page_0001_X` ... take these |
+| `apk_path` (optional) | Full path of the Android APK corresponding to `android_project_dir`. Passed through to `hmos-resources-convert` in Step 2 to skip the Gradle build and decompile this APK directly with apktool to extract resources | "APK path", "apk文件", "安卓apk" |
 
 **`references_dir` and MVVM document directories always use skill-bundled relative paths** — **do not** accept user-provided overrides:
 
@@ -41,6 +42,7 @@ Invoke the `hmos-resources-convert` skill with the following parameters:
 1. **Android project path** = `android_project_dir`
 2. **HarmonyOS project output path** = `harmony_project_dir`
 3. **resource_mapping_path** = generate the resource mapping document under `harmony_project_dir` at `${harmony_project_dir}/resource_mapping.md`
+4. **Android apk path** = `apk_path` — **only if the user provided it**. When passed through, `hmos-resources-convert` skips the Gradle build and decompiles this APK directly with apktool to extract resources. Omit this parameter entirely when `apk_path` was not provided.
 
 This skill batch-converts Android resources (strings, colors, drawables, images, etc.) to HarmonyOS resource format and generates the mapping document.
 
@@ -50,7 +52,7 @@ This skill batch-converts Android resources (strings, colors, drawables, images,
 2. Otherwise, determine the target App package name (`package`). If the user didn't provide it, extract the `package` attribute from `AndroidManifest.xml` in `android_project_dir`; if still unavailable, ask the user.
 3. Execute with Bash:
    ```
-   python ./scripts/android_parse_fast.py --package <package_name> --output <ui_info_root_absolute_path>
+   uv run --no-project python ./scripts/android_parse_fast.py --package <package_name> --output <ui_info_root_absolute_path>
    ```
    This script connects to the Android emulator via ADB, BFS-traverses all reachable pages in the App, and for each page saves `screenshot.png`, `view.xml`, `meta.json` into `page_NNNN_ActivityName/` subdirectories. It also generates `index.json` and `report.html` under `ui_info_root`.
 4. After execution, confirm that `index.json` has been generated under `ui_info_root`. If not, report an error and abort.

package/skills/hmos-convert-pipeline/SKILL.md

@@ -47,15 +47,15 @@ Define shorthand variables for the instructions below:
 
 ## Environment Variables Check (run before Stage 1)
 
-The pipeline's sub-agents read their settings **directly from the OS environment variables**. Verify upfront so the long pipeline fails fast (read each from the OS environment: `echo "$VAR"` on macOS/Linux; `$env:VAR` in PowerShell on Windows):
+The pipeline's sub-agents resolve each setting along the standard chain — **OS environment variable first, then `~/.hometrans/config.json`, then ask the user**. Verify upfront so the long pipeline fails fast (read env vars with `echo "$VAR"` on macOS/Linux; `$env:VAR` in PowerShell on Windows):
 
-| Variable | Needed for | Valid when |
-|---|---|---|
-| `DEVECO_HOME` *(or `DEVECO_SDK_HOME`)* | Stage 2 build + Stage 3a/4b rebuilds | resolves to a valid DevEco install |
-| `TEST_API_KEY` | Stage 4 self-test (only when `SKIP_TEST=false`) | non-empty |
-| `HOMETRANS_TOOL_PATH` | Stage 4 self-test AutoTest dir; defaults to `~/.hometrans/tools` | path exists on disk |
+| Variable | config.json fallback | Needed for | Valid when |
+|---|---|---|---|
+| `DEVECO_HOME` *(or `DEVECO_SDK_HOME`)* | `env.DEVECO_HOME` / `env.DEVECO_SDK_HOME` | Stage 2 build + Stage 3a/4b rebuilds | resolves to a valid DevEco install |
+| `HOMETRANS_MODEL_API_KEY` *(legacy `TEST_API_KEY` still honored as a fallback)* | `autotest.unified_model.api_key` | Stage 4 self-test (only when `SKIP_TEST=false`) | non-empty / not the placeholder |
+| `HOMETRANS_TOOL_PATH` | `env.HOMETRANS_TOOL_PATH` (defaults to `~/.hometrans/tools`) | Stage 4 self-test AutoTest dir | path exists on disk |
 
-If `DEVECO_HOME`/`DEVECO_SDK_HOME` is missing, **ask the user** for the DevEco Studio install path before starting. When `SKIP_TEST=false`, also require `TEST_API_KEY` — if missing, **ask the user** for it (or have them pass `skip_test=true`). Suggest running `ht init` to persist these as machine environment variables.
+For each value, if the env var is unset, fall back to the listed `~/.hometrans/config.json` field. If neither yields a value: for the DevEco path / model api_key, **ask the user** (for the api_key they may instead pass `skip_test=true`). Suggest running `ht init` to persist these as machine environment variables.
 
 ---
 

package/skills/hmos-fix-build-errors/SKILL.md

@@ -21,10 +21,11 @@ Automatically build a HarmonyOS NEXT project from the command line, parse compil
 
 1. **Verify project exists** — Check that `$ARGUMENTS[0]` contains a valid HarmonyOS project (look for `build-profile.json5`, `entry/src` directory, `oh-package.json5`).
 
-2. **Resolve `<deveco-path>`** — read **directly from the OS environment**; stop at the first source that yields a valid path:
+2. **Resolve `<deveco-path>`** — follow the standard config chain, stopping at the first source that yields a valid path:
    1. `$ARGUMENTS[1]` if provided (and not `--signed`).
-   2. Environment variables (`echo "$VAR"` on macOS/Linux; `$env:VAR` in PowerShell on Windows): `DEVECO_HOME` → parent of `DEVECO_SDK_HOME` → strip the trailing `/sdk/default/openharmony/ets` from `OHOS_SDK_PATH` (legacy).
-   3. **Ask the user** for the DevEco Studio install path (suggest running `ht init` to persist it as an environment variable).
+   2. **OS environment variables** (`echo "$VAR"` on macOS/Linux; `$env:VAR` in PowerShell on Windows): `DEVECO_HOME` → parent of `DEVECO_SDK_HOME` → strip the trailing `/sdk/default/openharmony/ets` from `OHOS_SDK_PATH` (legacy).
+   3. **`~/.hometrans/config.json`** — read `env.DEVECO_HOME`, else parent of `env.DEVECO_SDK_HOME` (written by `ht init`).
+   4. **Ask the user** for the DevEco Studio install path (suggest running `ht init` to persist it as an environment variable).
 
    **Verify the resolved `<deveco-path>`** contains:
    - `tools/node/node.exe`

package/skills/hmos-incremental-ui-align/README.md

@@ -13,7 +13,7 @@ HarmonyOS-Android UI 自动对齐流水线。
 每多一个页面/弹窗/tab，上述步骤都要重复一遍，非常费时。
 
 本 skill 做了三件事：
-- 用智谱 GLM 驱动的 phone-agent 自动**寻路**（根据自然语言点到指定页面）
+- 用 phone-agent 自动**寻路**（根据自然语言点到指定页面，模型复用 `~/.hometrans/config.json` 统一配置）
 - 自动**采集** view tree + 截图（安卓走 adb、鸿蒙走 hdc）
 - 自动**对比 + 改码**，并按 MVVM 模式把 mock 数据放到 Model 层
 
@@ -31,12 +31,10 @@ HarmonyOS-Android UI 自动对齐流水线。
    - 两台设备建议都保持亮屏解锁
 
 2. **Python 依赖**
-   ```bash
-   pip install openpyxl phone-agent
-   ```
+   无需手动安装。脚本通过 `uv run` 调用，`openpyxl` / `phone-agent` 已在 `app_feature_verify.py` 顶部的 PEP 723 内联元数据里声明，uv 首次运行时自动解析安装（走清华镜像）。只需确保已安装 `uv`（`uv --version`）。
 
-3. **智谱 GLM API Key**（phone-agent 调用的模型）
-   到 https://open.bigmodel.cn/ 申请，有免费额度。设为 OS 环境变量 `GLM_API_KEY`（`ht init` 可帮你写入机器环境变量）。
+3. **模型配置**（phone-agent 导航用）
+   与自测共用同一个多模态模型：`ht init` 把模型四要素（api_key / name / base_url / provider）写入 `~/.hometrans/config.json` 的 `autotest.unified_model`，并导出为 `HOMETRANS_MODEL_*` 环境变量。脚本优先读环境变量，缺失时回落 config.json；都没有时兼容老版本的 `GLM_API_KEY`（走智谱 GLM 端点）。无需单独设置 API Key。
 
 4. **鸿蒙 SDK 路径**（给改码阶段查 API 用）
    取自 OS 环境变量 `OHOS_SDK_PATH` / `HMS_SDK_PATH`（为空时由 `DEVECO_SDK_HOME` 派生），由 `ht init` 写入机器环境变量；例如 DevEco Studio 自带的 `E:\DevEco Studio\sdk\default\openharmony\ets`。
@@ -55,9 +53,9 @@ HarmonyOS-Android UI 自动对齐流水线。
 | `harmony_project_dir` | 是 | 鸿蒙工程根目录（会被直接修改）                                                    |
 | `capture_output_dir` | 否 | 采集产物输出目录（截图/view tree/分析报告）。默认 `<harmony_project_dir>/.hometrans/capture_output` |
 
-**② 从 OS 环境变量直接读取的全局配置**（由 `ht init` 写入机器环境变量，无需每次传）：
+**② 全局配置**（统一链路「环境变量 → `~/.hometrans/config.json` → 询问用户」，由 `ht init` 同时写入机器环境变量与 config.json，无需每次传）：
 
-- GLM key ← 环境变量 `GLM_API_KEY`
+- 模型配置 ← `HOMETRANS_MODEL_*` 环境变量（缺失时回落 `~/.hometrans/config.json` 的 `autotest.unified_model`；与自测共用同一个模型）
 - 鸿蒙 SDK ETS API 目录 ← 环境变量 `OHOS_SDK_PATH` / `HMS_SDK_PATH`（为空时由 `DEVECO_SDK_HOME` 派生为 `<DEVECO_SDK_HOME>/default/openharmony/ets`、`.../hms/ets`）
 
 > **Step 0.0** 会在执行前检查这些环境变量是否存在；缺失时会要求用户输入。
@@ -120,7 +118,7 @@ HarmonyOS-Android UI 自动对齐流水线。
 skill 会严格按 `SKILL.md` 里的 5 步流水线跑：
 
 ### Step 0 · 解析入参
-读取调用入参 `android_project_dir` / `harmony_project_dir` / `capture_output_dir`，并从 OS 环境变量直接读取 `GLM_API_KEY` 与 `OHOS_SDK_PATH` / `HMS_SDK_PATH`（**Step 0.0** 会先做存在性检查，缺失则要求用户输入）。随后 **Step 0.1** 按两个工程目录自动解析两端的 App 显示名与包名（无需手动配置）。
+读取调用入参 `android_project_dir` / `harmony_project_dir` / `capture_output_dir`，并按统一链路「环境变量 → config.json → 询问」解析 `HOMETRANS_MODEL_*`（统一模型，回落 `~/.hometrans/config.json` 的 `autotest.unified_model`）与 `OHOS_SDK_PATH` / `HMS_SDK_PATH`（回落 config.json 的 `env.*`；**Step 0.0** 会先做存在性检查，两层都缺失才要求用户输入）。随后 **Step 0.1** 按两个工程目录自动解析两端的 App 显示名与包名（无需手动配置）。
 
 ### Step 1 · 双端页面采集
 1.1 解析你的需求，拆成一组「基础页」，每个基础页有 `android_nav_path` 和 `hmos_nav_path`
@@ -193,16 +191,15 @@ Agents/hmos-ui-align/
 ```powershell
 # 安卓寻路
 $env:PYTHONIOENCODING="utf-8"
-python Agents/hmos-ui-align/scripts/app_feature_verify.py `
+uv run Agents/hmos-ui-align/scripts/app_feature_verify.py `
   --device adb `
   --app "Salt Player" `
   --package "com.salt.music" `
   --prompt "进入首页-点击AI智能填报-点击专业筛选按钮" `
-  --api-key "$env:GLM_API_KEY" `
   --max-steps 15
 
 # 安卓采集
-python Agents/hmos-ui-align/scripts/page_capture.py --device adb -o ./tmp/android_page_1_xxx
+uv run Agents/hmos-ui-align/scripts/page_capture.py --device adb -o ./tmp/android_page_1_xxx
 
 # 鸿蒙同理，把 --device adb 换成 --device hdc
 ```

package/skills/hmos-incremental-ui-align/SKILL.md

@@ -18,7 +18,7 @@ You are writing ArkTS codes.
 
 ## Step 0: Resolve Inputs
 
-This skill takes three path inputs from the invocation and reads its other settings **directly from the OS environment variables**.
+This skill takes three path inputs from the invocation and resolves its other settings along the standard chain — **OS environment variable → `~/.hometrans/config.json` → ask the user** (see Step 0.0).
 
 ### Skill input arguments (provided by the user when invoking the skill)
 
@@ -32,17 +32,17 @@ The user may pass them as named args (e.g. `android_project_dir: D:\path\to\andr
 
 ### Step 0.0: Environment Variables Check (run first)
 
-Read each variable below **directly from the OS environment** (`echo "$VAR"` on macOS/Linux; `$env:VAR` in PowerShell / `echo %VAR%` in cmd on Windows).
+Resolve each value along the standard chain — **OS environment variable first, then `~/.hometrans/config.json`, then ask the user** (read env vars with `echo "$VAR"` on macOS/Linux; `$env:VAR` in PowerShell / `echo %VAR%` in cmd on Windows).
 
-| Variable | Purpose | Valid when |
-|---|---|---|
-| `GLM_API_KEY` | Zhipu GLM key for the phone-agent (Step 1 navigation) | non-empty |
-| `OHOS_SDK_PATH` | HarmonyOS SDK ETS API reference (Step 3) | path exists on disk |
-| `HMS_SDK_PATH` | HMS SDK ETS API reference (Step 3) | path exists on disk |
+| Variable | config.json fallback | Purpose | Valid when |
+|---|---|---|---|
+| `HOMETRANS_MODEL_*` (`HOMETRANS_MODEL_API_KEY` / `HOMETRANS_MODEL_NAME` / `HOMETRANS_MODEL_BASE_URL`) | `autotest.unified_model.{api_key,name,base_url}`（provider 默认 openai，不导出环境变量；再兜底老版本 `GLM_API_KEY` → 智谱 GLM 端点） | 统一多模态模型（UI 对齐 + 自测共用），由 `ht init` 导出 | `HOMETRANS_MODEL_API_KEY` 非空（或 config.json 已配置，或老版本 `GLM_API_KEY` 已设置） |
+| `OHOS_SDK_PATH` | `env.OHOS_SDK_PATH` | HarmonyOS SDK ETS API reference (Step 3) | path exists on disk |
+| `HMS_SDK_PATH` | `env.HMS_SDK_PATH` | HMS SDK ETS API reference (Step 3) | path exists on disk |
 
-For `OHOS_SDK_PATH` / `HMS_SDK_PATH`, if unset but `DEVECO_SDK_HOME` is set, derive them as `<DEVECO_SDK_HOME>/default/openharmony/ets` and `<DEVECO_SDK_HOME>/default/hms/ets`.
+The model config is resolved automatically by `scripts/app_feature_verify.py` (env → config.json), so you don't read it by hand — just confirm `HOMETRANS_MODEL_API_KEY` or `autotest.unified_model.api_key` is set. For `OHOS_SDK_PATH` / `HMS_SDK_PATH`, if both the env var and `~/.hometrans/config.json` are empty but `DEVECO_SDK_HOME` is set (env or `env.DEVECO_SDK_HOME` in config.json), derive them as `<DEVECO_SDK_HOME>/default/openharmony/ets` and `<DEVECO_SDK_HOME>/default/hms/ets`.
 
-For each variable that is still missing/empty (or a path that does not exist), **stop and ask the user to provide a value**, then use what they give for this run. Suggest running `ht init` to persist them as machine environment variables for next time.
+For each value that is still missing/empty (or a path that does not exist) after both the env var and `~/.hometrans/config.json`, **stop and ask the user to provide a value**, then use what they give for this run. Suggest running `ht init` to persist them as machine environment variables for next time.
 
 ### Step 0.1: Auto-derive App Names & Package Names