@buaa_smat/hometrans 0.1.1 → 0.1.3

package/agents/build-fixer.md

@@ -1,4 +1,5 @@
 ---
+name: build-fixer
 description: Automatically builds a HarmonyOS project, parses compile errors, fixes them, and retries in a loop until build succeeds
 color: orange
 ---
@@ -28,35 +29,40 @@ Execute a build-fix loop: resolve environment → validate project → build →
 
 The build requires the **DevEco Studio installation path**, from which Node.js, hvigor, and ohpm are derived.
 
-### 0a. Read the plugin config
+### 0a. Read the HomeTrans config
 
-Read the config file at `android-harmonyos-converter/.claude-plugin/converter-config.json` (locate the plugin root by searching for the `android-harmonyos-converter/.claude-plugin/plugin.json` file). It may contain:
+Read the config file written by `ht init` at `~/.hometrans/config.json` (`$HOME/.hometrans/config.json`; on Windows `%USERPROFILE%\.hometrans\config.json`). Its shape is:
 
 ```jsonc
 {
-  "node_path": "...",
-  "deveco_studio_path": "...",   // e.g. "D:\\DevEco Studio"
-  "harmonyos_sdk_path": "...",
-  "python_path": "...",
-  "java_home": "..."
+  "editors": [ /* ... */ ],
+  "params": {
+    "OHOS_SDK_PATH": "...",   // OpenHarmony SDK ETS path, e.g. "D:/DevEco Studio/sdk/default/openharmony/ets"
+    "HMS_SDK_PATH": "...",    // HMS SDK ETS path, e.g. "D:/DevEco Studio/sdk/default/hms/ets"
+    "TEST_API_KEY": "..."
+  }
 }
 ```
 
-Extract `deveco_studio_path` from this file.
+Read `params.OHOS_SDK_PATH` from this file.
 
-### 0b. Derive tool paths from DevEco Studio
+### 0b. Derive the DevEco Studio root and tool paths
 
-If `deveco_studio_path` is present and valid, derive:
-- **Node executable**: `<deveco_studio_path>/tools/node/node.exe`
-- **Hvigor script**: `<deveco_studio_path>/tools/hvigor/bin/hvigorw.js`
-- **ohpm**: `<deveco_studio_path>/tools/ohpm/bin/ohpm`
-- **SDK directory**: `<deveco_studio_path>/sdk`
+The DevEco Studio installation root is the part of `OHOS_SDK_PATH` before the SDK suffix. Strip the trailing `/sdk/default/openharmony/ets` (or `\sdk\default\openharmony\ets`) from `OHOS_SDK_PATH` to get `<deveco>`.
 
-Verify these files exist. If they do, use them and skip auto-detection.
+> Example: `OHOS_SDK_PATH = D:/DevEco Studio/sdk/default/openharmony/ets` → `<deveco> = D:/DevEco Studio`.
+
+From `<deveco>`, derive:
+- **Node executable**: `<deveco>/tools/node/node.exe`
+- **Hvigor script**: `<deveco>/tools/hvigor/bin/hvigorw.js`
+- **ohpm**: `<deveco>/tools/ohpm/bin/ohpm`
+- **SDK directory**: `<deveco>/sdk`
+
+Verify these files exist. If they do, use them and skip auto-detection. (Fall back to `params.HMS_SDK_PATH` — stripping `/sdk/default/hms/ets` — if `OHOS_SDK_PATH` is absent but `HMS_SDK_PATH` is present.)
 
 ### 0c. Auto-detect if config is missing or invalid
 
-If the config file is empty, missing, or the paths don't point to real files, auto-detect:
+If `~/.hometrans/config.json` is missing, has empty `params.OHOS_SDK_PATH`/`HMS_SDK_PATH`, or the derived paths don't point to real files, auto-detect:
 
 1. **Find DevEco Studio installation**:
    - Search common locations: `D:\DevEco Studio`, `C:\DevEco Studio`, `C:\Program Files\DevEco Studio`
@@ -67,7 +73,7 @@ If the config file is empty, missing, or the paths don't point to real files, au
    - `where node` (Windows) or `which node` (Unix)
    - Verify it runs: `node --version`
 
-If auto-detection fails for any critical path, **stop and report clearly** what is missing so the user can run `/setup` to configure it.
+If auto-detection fails for any critical path, **stop and report clearly** what is missing so the user can run `ht init` to configure it.
 
 ### 0d. Store resolved paths
 

package/agents/code-review-fix.md

@@ -1,4 +1,5 @@
 ---
+name: code-review-fix
 description: One-pass review-fix-build cycle — reviews HarmonyOS code against scenarios, verifies and fixes confirmed issues, rebuilds the project
 color: red
 ---
@@ -40,7 +41,7 @@ If `commit-id` is provided and is not `none`:
    - `projectPath`: `<harmonyos-project-path>`
    - `commitId`: `<commit-id>`
    - `mode`: `"default"`
-   - `ohosSdkPath` / `hmsSdkPath`: from environment or omit
+   - `ohosSdkPath` / `hmsSdkPath`: omit to let the tool read `params.OHOS_SDK_PATH` / `params.HMS_SDK_PATH` from the `ht init` config (`~/.hometrans/config.json`), falling back to the `OHOS_SDK_PATH` / `HMS_SDK_PATH` env vars
 
 2. **On failure**, fall back to:
    ```bash
@@ -230,16 +231,16 @@ Classify: **CONFIRMED** (fix) | **FALSE_POSITIVE** (skip, record reason) | **UNC
 
 ### Step 3.0: Resolve Build Environment
 
-1. Read `android-harmonyos-converter/.claude-plugin/converter-config.json` (locate plugin root by searching for `android-harmonyos-converter/.claude-plugin/plugin.json`). Extract `deveco_studio_path`.
+1. Read the `ht init` config at `~/.hometrans/config.json` (Windows: `%USERPROFILE%\.hometrans\config.json`). Take `params.OHOS_SDK_PATH` (e.g. `D:/DevEco Studio/sdk/default/openharmony/ets`) and strip the trailing `/sdk/default/openharmony/ets` to get the DevEco Studio root `<deveco>`. Fall back to `params.HMS_SDK_PATH` (strip `/sdk/default/hms/ets`) if needed.
 
 2. Derive tool paths:
    - `NODE_EXE`: `<deveco>/tools/node/node.exe`
    - `HVIGORW_JS`: `<deveco>/tools/hvigor/bin/hvigorw.js`
    - `OHPM`: `<deveco>/tools/ohpm/bin/ohpm`
 
-3. If config missing, auto-detect: search `D:\DevEco Studio`, `C:\DevEco Studio`, `C:\Program Files\DevEco Studio` for `tools/hvigor/bin/hvigorw.js`.
+3. If the config is missing or `params.OHOS_SDK_PATH`/`HMS_SDK_PATH` are empty, auto-detect: search `D:\DevEco Studio`, `C:\DevEco Studio`, `C:\Program Files\DevEco Studio` for `tools/hvigor/bin/hvigorw.js`.
 
-4. If detection fails, stop and report clearly what is missing.
+4. If detection fails, stop and report clearly what is missing so the user can run `ht init` to configure it.
 
 ### Step 3.1: Setup Project
 

package/agents/code-reviewer.md

@@ -1,4 +1,5 @@
 ---
+name: code-reviewer
 description: Reviews HarmonyOS code against user scenarios to validate functional coverage
 color: red
 ---

package/agents/logic-coding.md

@@ -1,4 +1,5 @@
 ---
+name: logic-coding
 description: "Execute the HarmonyOS ArkTS app contract without reopening design choices."
 color: blue
 min-model: sonnet

package/agents/logic-context-builder.md

@@ -1,4 +1,5 @@
 ---
+name: logic-context-builder
 description: "Constrain HarmonyOS ArkTS app changes into an executable decision contract."
 color: blue
 min-model: sonnet

package/agents/review-fixer.md

@@ -1,4 +1,5 @@
 ---
+name: review-fixer
 description: Fixes issues from code review reports — verifies each issue before fixing, references Android source, and uses cautious per-scenario fix strategies
 color: red
 ---

package/agents/self-test-fixer.md

@@ -1,4 +1,5 @@
 ---
+name: self-test-fixer
 description: Fixes issues identified by self-testing — reads self-test report, white-box verifies failures in HarmonyOS code, plans and executes fixes in order, produces detailed report
 color: cyan
 ---

package/agents/self-tester.md

@@ -1,4 +1,5 @@
 ---
+name: self-tester
 description: Self-Tester — parses test_case.md into testcases.json + app-metadata.json, runs on-device AutoTest verification, and produces self-test-report.md. The `setup` boolean controls whether the parse phase runs.
 color: green
 ---

package/agents/spec-generator.md

@@ -1,4 +1,5 @@
 ---
+name: spec-generator
 description: Generates requirement specification (spec) documents for each requirement description file in a given folder by exploring an Android project and decomposing each requirement into atomic user scenarios
 color: cyan
 ---

package/package.json

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