@buaa_smat/hometrans 0.1.13 → 0.1.15

package/agents/build-fixer.md

@@ -14,8 +14,8 @@ Execute a build-fix loop: resolve environment → validate project → build →
 
 ## Expected Input
 
-- `harmonyos-project-path`: Absolute path to the HarmonyOS project root (the directory containing `build-profile.json5`) — **required**
-- `output-path`: Absolute path to the directory where `build-fix-report.md` should be written — **optional** (defaults to cwd)
+- `harmony_project_dir`: Absolute path to the HarmonyOS project root (the directory containing `build-profile.json5`) — **required**
+- `output_path`: Absolute path to the directory where `build-fix-report.md` should be written — **optional** (defaults to cwd)
 - `--signed`: Optional flag. If present, build a signed HAP (signing config must already exist in `build-profile.json5`). Default is unsigned.
 
 ## Expected Output
@@ -29,34 +29,24 @@ 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 HomeTrans config
-
-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
-{
-  "editors": [ /* ... */ ],
-  "env": {
-    "DEVECO_SDK_HOME": "...", // DevEco sdk dir, e.g. "D:/DevEco Studio/sdk" — single source of truth
-    "DEVECO_PATH": "...",     // DevEco install root, e.g. "D:/DevEco Studio" (derived from DEVECO_SDK_HOME)
-    "OHOS_SDK_PATH": "...",   // <DEVECO_SDK_HOME>/default/openharmony/ets (derived)
-    "HMS_SDK_PATH": "...",    // <DEVECO_SDK_HOME>/default/hms/ets (derived)
-    "TEST_API_KEY": "...",
-    "TOOL_PATH": "..."        // HomeTrans tools dir, e.g. "C:/Users/<you>/.hometrans/tools"
-  }
-}
-```
+### 0a. Read the DevEco environment variables
+
+Read these **directly from the OS environment** — `ht init` persists them as machine environment variables (`echo "$VAR"` on macOS/Linux; `$env:VAR` in PowerShell on Windows):
+
+| Variable | Meaning |
+|---|---|
+| `DEVECO_SDK_HOME` | DevEco sdk dir, e.g. `D:/DevEco Studio/sdk` — single source of truth |
+| `DEVECO_HOME` | DevEco install root, e.g. `D:/DevEco Studio` |
+| `OHOS_SDK_PATH` | `<DEVECO_SDK_HOME>/default/openharmony/ets` |
+| `HMS_SDK_PATH` | `<DEVECO_SDK_HOME>/default/hms/ets` |
 
-### 0b. Resolve the DevEco root `<deveco>` — config first, then env vars, then ask
+### 0b. Resolve the DevEco root `<deveco>` — env vars first, then auto-detect, then ask
 
 Stop at the **first** source that yields a path:
 
-1. **Config file** (`~/.hometrans/config.json`):
-   - `env.DEVECO_PATH` if non-empty → that is `<deveco>`.
-   - else `env.DEVECO_SDK_HOME` → `<deveco>` is its **parent directory**.
-   - else (legacy configs) strip the trailing `/sdk/default/openharmony/ets` from `env.OHOS_SDK_PATH` (or `/sdk/default/hms/ets` from `env.HMS_SDK_PATH`) to get `<deveco>`.
-2. **Environment variables** (same precedence): `DEVECO_PATH` → `DEVECO_SDK_HOME` (parent dir) → `OHOS_SDK_PATH` / `HMS_SDK_PATH` (strip suffix as above).
-3. **Auto-detect** (0c below). If that also fails, **ask the user** for the DevEco Studio install path.
+1. **Environment variables**: `DEVECO_HOME` if non-empty → that is `<deveco>`; else `DEVECO_SDK_HOME` → `<deveco>` is its **parent directory**; else (legacy) strip the trailing `/sdk/default/openharmony/ets` from `OHOS_SDK_PATH` (or `/sdk/default/hms/ets` from `HMS_SDK_PATH`) to get `<deveco>`.
+2. **Auto-detect** (0c below).
+3. If both fail, **ask the user** for the DevEco Studio install path (suggest running `ht init` to persist it as an environment variable).
 
 > Example: `DEVECO_SDK_HOME = D:/DevEco Studio/sdk` → `<deveco> = D:/DevEco Studio`.
 
@@ -66,11 +56,11 @@ From `<deveco>`, derive:
 - **ohpm**: `<deveco>/tools/ohpm/bin/ohpm`
 - **SDK directory**: `<deveco>/sdk`
 
-Verify these files exist. If they do, use them and skip auto-detection. If a config-sourced path does **not** exist on disk, treat that source as invalid and continue down the resolution order.
+Verify these files exist. If they do, use them and skip auto-detection. If an env-sourced path does **not** exist on disk, treat that source as invalid and continue down the resolution order.
 
-### 0c. Auto-detect if config and env vars are missing or invalid
+### 0c. Auto-detect if env vars are missing or invalid
 
-If neither the config file nor environment variables yield a valid install, auto-detect:
+If the environment variables do not yield a valid install, auto-detect:
 
 1. **Find DevEco Studio installation**:
    - Search common locations: `D:\DevEco Studio`, `C:\DevEco Studio`, `C:\Program Files\DevEco Studio`
@@ -86,7 +76,7 @@ If auto-detection fails for any critical path, **ask the user directly** for the
 ### 0d. Store resolved paths
 
 Keep these resolved values for use in later steps:
-- `DEVECO_PATH` — absolute path to DevEco Studio installation root
+- `DEVECO_HOME` — absolute path to DevEco Studio installation root
 - `NODE_EXE` — absolute path to node executable
 - `HVIGORW_JS` — absolute path to hvigorw.js
 - `OHPM` — absolute path to ohpm executable
@@ -95,14 +85,14 @@ Keep these resolved values for use in later steps:
 
 ## Step 1: Validate Inputs & Setup Project
 
-1. **Verify project exists** — Check that `harmonyos-project-path` contains:
+1. **Verify project exists** — Check that `harmony_project_dir` contains:
    - `build-profile.json5`
    - `entry/src` directory
    - `oh-package.json5`
 
 2. **Set up `local.properties`** — Ensure the project root has `local.properties` with:
    ```properties
-   hwsdk.dir=<DEVECO_PATH>/sdk
+   hwsdk.dir=<DEVECO_HOME>/sdk
    ```
    Create it if missing. Use forward slashes in the path.
 
@@ -152,19 +142,19 @@ Execute the following loop. **Maximum 20 iterations** to prevent infinite loops.
    **For unsigned builds** (no `--signed`):
    ```bat
    @echo off
-   set "DEVECO_SDK_HOME=<DEVECO_PATH>\sdk"
+   set "DEVECO_SDK_HOME=<DEVECO_HOME>\sdk"
    cd /d "<project-dir>"
-   "<DEVECO_PATH>\tools\node\node.exe" "<DEVECO_PATH>\tools\hvigor\bin\hvigorw.js" assembleHap --mode module -p module=entry --no-daemon
+   "<DEVECO_HOME>\tools\node\node.exe" "<DEVECO_HOME>\tools\hvigor\bin\hvigorw.js" assembleHap --mode module -p module=entry --no-daemon
    ```
 
    **For signed builds** (`--signed`):
    ```bat
    @echo off
-   set "PATH=<DEVECO_PATH>\jbr\bin;%PATH%"
-   set "JAVA_HOME=<DEVECO_PATH>\jbr"
-   set "DEVECO_SDK_HOME=<DEVECO_PATH>\sdk"
+   set "PATH=<DEVECO_HOME>\jbr\bin;%PATH%"
+   set "JAVA_HOME=<DEVECO_HOME>\jbr"
+   set "DEVECO_SDK_HOME=<DEVECO_HOME>\sdk"
    cd /d "<project-dir>"
-   "<DEVECO_PATH>\tools\node\node.exe" "<DEVECO_PATH>\tools\hvigor\bin\hvigorw.js" assembleHap --mode module -p module=entry --no-daemon
+   "<DEVECO_HOME>\tools\node\node.exe" "<DEVECO_HOME>\tools\hvigor\bin\hvigorw.js" assembleHap --mode module -p module=entry --no-daemon
    ```
    Note: Signed builds need `JAVA_HOME` and `jbr\bin` in PATH because the `SignHap` step spawns `java` as a child process.
 
@@ -238,16 +228,16 @@ Then go back to **2.1** and rebuild.
 
 ## Step 2.6: Copy HAP to Output Directory
 
-If `output-path` was provided, copy the built HAP file to the output directory after a successful build:
+If `output_path` was provided, copy the built HAP file to the output directory after a successful build:
 
 1. **Locate the HAP file** under `<project-dir>/entry/build/default/outputs/default/`:
    - If `--signed`: search for `*-signed.hap`
    - If unsigned (no `--signed`): search for `*-unsigned.hap`
 2. **Copy** the HAP to the output directory:
    ```bash
-   cp "<hap-path>" "<output-path>/"
+   cp "<hap_path>" "<output_path>/"
    ```
-3. **Verify** the copied file exists in `output-path`.
+3. **Verify** the copied file exists in `output_path`.
 4. If no matching HAP is found, report the issue in `build-fix-report.md` and note the expected path.
 
 ---
@@ -297,25 +287,25 @@ Files modified: {comma-separated list of modified files}
    cd "<project-dir>" && git rev-parse HEAD
    ```
 
-4. **Write commit info** to `<output-path>/build-fix-commit-info.md`:
+4. **Write commit info** to `<output_path>/build-fix-commit-info.md`:
    ```
-   commit-id: <commit-id>
+   commit_id: <commit_id>
    ```
 
 **If no source files were modified** (build succeeded on first attempt with zero errors):
-- Write `<output-path>/build-fix-commit-info.md` with:
+- Write `<output_path>/build-fix-commit-info.md` with:
   ```
-  commit-id: none
+  commit_id: none
   ```
 
 **If not in a git repository**:
 - Record issue "Not a git repository — skipped commit" in `build-fix-report.md`.
-- Write `<output-path>/build-fix-commit-info.md` with:
+- Write `<output_path>/build-fix-commit-info.md` with:
   ```
-  commit-id: none
+  commit_id: none
   ```
 
-**If `output-path` was not provided**, skip writing `build-fix-commit-info.md`.
+**If `output_path` was not provided**, skip writing `build-fix-commit-info.md`.
 
 ---
 

package/agents/code-reviewer.md

@@ -14,14 +14,14 @@ Read the user scenario design document, then systematically verify the HarmonyOS
 
 ## Expected Input
 
-- `harmonyos-project-path`: Absolute path to the HarmonyOS project root (directory containing ArkTS source code)
-- `commit-id`: The commit ID of the code submission to review (required)
-- `output-path`: Absolute path to the directory where the review report should be written (required)
-- `test-case-path`: Absolute path to the user scenario design document. If not provided, defaults to `<output-path>/test_case.md`
+- `harmony_project_dir`: Absolute path to the HarmonyOS project root (directory containing ArkTS source code)
+- `commit_id`: The commit ID of the code submission to review (required)
+- `output_path`: Absolute path to the directory where the review report should be written (required)
+- `test_case_path`: Absolute path to the user scenario design document. If not provided, defaults to `<output_path>/test_case.md`
 
 ## Expected Output
 
-- A file named `code-review-report.md` in `output-path`
+- A file named `code-review-report.md` in `output_path`
 
 ---
 
@@ -30,19 +30,19 @@ Read the user scenario design document, then systematically verify the HarmonyOS
 Before starting the review, extract the code context for the commit via the `extract_commit_context` MCP tool.
 
 1. **Call the MCP tool** `extract_commit_context` with:
-   - `projectPath`: `<harmonyos-project-path>` (absolute path to the HarmonyOS project root containing the `.git` directory)
-   - `commitId`: `<commit-id>` (the git commit to analyze — diffs against its first parent)
+   - `projectPath`: `<harmony_project_dir>` (absolute path to the HarmonyOS project root containing the `.git` directory)
+   - `commitId`: `<commit_id>` (the git commit to analyze — diffs against its first parent)
    - `mode`: `"default"` (builds full call graph for call-chain context)
-   - `ohosSdkPath` / `hmsSdkPath`: the OpenHarmony / HMS SDK ETS directory paths. Resolve each in this order, stop at the first hit:
-     1. `env.OHOS_SDK_PATH` / `env.HMS_SDK_PATH` from `~/.hometrans/config.json` (on Windows `%USERPROFILE%\.hometrans\config.json`); if those are empty but `env.DEVECO_SDK_HOME` is set, derive them as `<DEVECO_SDK_HOME>/default/openharmony/ets` and `<DEVECO_SDK_HOME>/default/hms/ets`.
-     2. Omit the parameter to let the tool read `OHOS_SDK_PATH` / `HMS_SDK_PATH` from the environment variables.
-     3. If neither config nor environment provides a path that exists on disk, **ask the user** for the DevEco `sdk` directory (and suggest `ht init` to persist it).
+   - `ohosSdkPath` / `hmsSdkPath`: the OpenHarmony / HMS SDK ETS directory paths. Resolve each **from the OS environment**, stopping at the first hit:
+     1. `OHOS_SDK_PATH` / `HMS_SDK_PATH` environment variables; if those are empty but `DEVECO_SDK_HOME` is set, derive them as `<DEVECO_SDK_HOME>/default/openharmony/ets` and `<DEVECO_SDK_HOME>/default/hms/ets`.
+     2. Omit the parameter to let the tool read `OHOS_SDK_PATH` / `HMS_SDK_PATH` from the environment itself.
+     3. If the environment provides no path that exists on disk, **ask the user** for the DevEco `sdk` directory (and suggest running `ht init` to persist it as an environment variable).
 
 2. **On success** — the tool returns the affected code context (diffs, call graphs, impacted files). Treat this response as the **code context** for the review.
 
 3. **On failure** — if the MCP tool call fails (network error, tool unavailable, or returns an error), fall back to direct commit analysis:
-   - Run `git diff <commit-id>^..<commit-id>` in `<harmonyos-project-path>` to obtain the raw diff.
-   - Run `git show --stat <commit-id>` to list affected files.
+   - Run `git diff <commit_id>^..<commit_id>` in `<harmony_project_dir>` to obtain the raw diff.
+   - Run `git show --stat <commit_id>` to list affected files.
    - Read the changed files directly from the project to build the code context manually.
    - Proceed with the review using this manually assembled context — do not stop.
 
@@ -52,15 +52,15 @@ Before starting the review, extract the code context for the commit via the `ext
 
 0. **Resolve document paths**:
    
-   - If `test-case-path` is not provided, use `<output-path>/test_case.md`
+   - If `test_case_path` is not provided, use `<output_path>/test_case.md`
    
 1. **Read the code context** (from Step 0):
    - Parse the code context returned by the MCP tool (or the manually assembled fallback)
-   - This contains the diff and relevant code context for commit `commit-id`
+   - This contains the diff and relevant code context for commit `commit_id`
    - Understand the scope of changes: which files were modified, added, or deleted
    - Build a map of the changed code areas — these are the primary focus of the review
 
-3. **Read the user scenario design document** (`test-case-path`):
+3. **Read the user scenario design document** (`test_case_path`):
    
    - Extract every user scenario / user story / use case described
    - For each scenario, identify:
@@ -82,7 +82,7 @@ Before starting the review, extract the code context for the commit via the `ext
 Review the code based on the extracted code context (from the MCP tool or fallback) combined with the broader project structure:
 
 1. **Code context analysis** (primary focus): Analyze the extracted code context to understand:
-   - Which files were changed in commit `commit-id`
+   - Which files were changed in commit `commit_id`
    - The specific diffs and surrounding code for each changed file
    - The intent and scope of the changes relative to the commit
 
@@ -152,7 +152,7 @@ After per-scenario review, check these cross-cutting concerns that affect multip
 
 ## Step 5 — Write `code-review-report.md`
 
-Write the report to `output-path/code-review-report.md` with the following structure:
+Write the report to `output_path/code-review-report.md` with the following structure:
 
 ```markdown
 # Code Review Report
@@ -160,8 +160,8 @@ Write the report to `output-path/code-review-report.md` with the following struc
 ## Overview
 
 - **Project**: <project name/path>
-- **Commit ID**: <commit-id>
-- **Scenario Doc**: <test-case-path>
+- **Commit ID**: <commit_id>
+- **Scenario Doc**: <test_case_path>
 - **Code Context**: extract_commit_context MCP tool (or git-diff fallback)
 - **Review Date**: <date>
 - **Total Scenarios**: <N>

package/agents/logic-coder.md

@@ -7,10 +7,10 @@ min-model: sonnet
 
 ## Inputs
 
-- `plan-file` = `{output_path}/plan.md`
-- `harmonyos-project-path` (abs)
-- `output-path` (abs)
-- `plugin-path` (abs) — plugin root; `{scripts}` = `{plugin-path}/agents/logic-coder/scripts/`
+- `plan_file` = `{output_path}/plan.md`
+- `harmony_project_dir` (abs)
+- `output_path` (abs)
+- `plugin_path` (abs) — plugin root; `{scripts}` = `{plugin_path}/agents/logic-coder/scripts/`
 
 ## Tools
 
@@ -38,15 +38,15 @@ blocked, write the gap instead of fake completion.
 
 ## Procedure
 
-1. Read `plan-file` first.
-2. If runtime provides checked constraints, read them after `plan-file`; they
+1. Read `plan_file` first.
+2. If runtime provides checked constraints, read them after `plan_file`; they
    narrow unsafe choices but do not broaden plan scope.
 3. Verify local facts (per Verification, in stated order).
 4. Patch only plan-required behavior.
 5. Validate (per Validate And Output). Stage only plan-required files; do not
    use `git add -A`.
 6. Commit with a non-interactive message naming the decision contract.
-7. Write `{output_path}/commit-info.md` with `commit-id: <full hash>`.
+7. Write `{output_path}/commit-info.md` with `commit_id: <full hash>`.
 8. Write `{output_path}/issues.md` only for blocking `Unknown`,
    repo-vs-plan contradiction, platform drift, missing proof, or validation
    failure.
@@ -55,7 +55,7 @@ Never ask. Never commit outside plan scope.
 
 ## Read Scope
 
-After `plan-file`, read only plan-named files, direct imports/exports, needed
+After `plan_file`, read only plan-named files, direct imports/exports, needed
 symbol/type definitions, current producer/owner/consumer/target display,
 same-pattern local code, build-error files, and plan-named platform evidence.
 

package/agents/logic-context-builder.md

@@ -7,10 +7,10 @@ min-model: sonnet
 
 ## Inputs
 
-- `spec-file` (abs)
-- `harmonyos-project-path` (abs)
-- `output-path` (abs)
-- `plugin-path` (abs) — plugin root; `{scripts}` = `{plugin-path}/agents/logic-coder/scripts/`
+- `spec_file` (abs)
+- `harmony_project_dir` (abs)
+- `output_path` (abs)
+- `plugin_path` (abs) — plugin root; `{scripts}` = `{plugin_path}/agents/logic-coder/scripts/`
 
 ## Tools
 
@@ -66,7 +66,7 @@ chooses."
 Evidence priority: visible/resource text > render/caller path >
 producer/consumer > route/menu > file/class names. Reject name-only/comment-only.
 
-1. Read `spec-file`. Extract SPEC anchors: visible text/resources, route/menu,
+1. Read `spec_file`. Extract SPEC anchors: visible text/resources, route/menu,
    UI section, component/builder, entity/field/action, acceptance, non-goals.
 2. Reason internally until a chain node needs a concrete fact.
 3. Narrow chain nodes by project and platform evidence. Write plan.md.

package/agents/review-fixer.md

@@ -18,10 +18,10 @@ Read a code-review report (`code-review-report.md`), double-check every reported
 
 ## Expected Input
 
-- `review-report-path`: Path to the code-review report file (`.md`) — **required**
-- `harmonyos-project-path`: Path to the HarmonyOS project root — **required**
-- `android-project-path`: Path to the Android source project — **optional** (enables reference-based fixing)
-- `output-path`: Directory to store `review-fix-report.md` — **optional** (defaults to cwd)
+- `review_report_path`: Path to the code-review report file (`.md`) — **required**
+- `harmony_project_dir`: Path to the HarmonyOS project root — **required**
+- `android_project_dir`: Path to the Android source project — **optional** (enables reference-based fixing)
+- `output_path`: Directory to store `review-fix-report.md` — **optional** (defaults to cwd)
 
 ## Expected Output
 
@@ -134,7 +134,7 @@ For each **CONFIRMED** issue, apply the appropriate fix strategy based on the is
 
 **When**: A page or component referenced by a scenario does not exist.
 
-1. **Read the Android source** (if `android-project-path` is provided):
+1. **Read the Android source** (if `android_project_dir` is provided):
    - Find the corresponding Android Activity/Fragment/View.
    - Document: layout structure, event handlers, data sources, navigation targets.
 2. **Use Context7 MCP tool** to look up the HarmonyOS equivalent UI components (e.g., `Grid` for `RecyclerView`, `List` for `ListView`).
@@ -216,7 +216,7 @@ For each **CONFIRMED** issue, apply the appropriate fix strategy based on the is
 
 After completing fixes for a group of related issues (e.g., all issues in one scenario, or all permission issues), verify the project still compiles:
 
-1. Launch the **build-fixer** agent with `harmonyos-project-path` and `output-path`.
+1. Launch the **build-fixer** agent with `harmony_project_dir` and `output_path`.
 2. If compilation fails, the build-fixer agent will auto-fix compile errors — this does **not** count as an effective attempt.
 3. If compilation succeeds, proceed to the next group of issues.
 4. If compilation cannot be fixed after build-fixer's attempts, **revert the most recent changes** for that group and record the issue as "failed to fix — compilation error".
@@ -239,9 +239,9 @@ After processing all issues, write `review-fix-report.md` to the output director
 
 ## Overview
 
-- **Review Report**: <review-report-path>
-- **HarmonyOS Project**: <harmonyos-project-path>
-- **Android Source**: <android-project-path or "not provided">
+- **Review Report**: <review_report_path>
+- **HarmonyOS Project**: <harmony_project_dir>
+- **Android Source**: <android_project_dir or "not provided">
 - **Fix Date**: <date>
 - **Total Issues in Report**: <N>
 - **Verified (CONFIRMED)**: <X>
@@ -368,25 +368,25 @@ Confirmed: {X}, Fixed: {A}, False positives: {Y}
    cd "<project-dir>" && git rev-parse HEAD
    ```
 
-4. **Write commit info** to `<output-path>/review-fix-commit-info.md`:
+4. **Write commit info** to `<output_path>/review-fix-commit-info.md`:
    ```
-   commit-id: <commit-id>
+   commit_id: <commit_id>
    ```
 
 **If no files were modified** (all issues were false positives or all fix attempts failed):
-- Write `<output-path>/review-fix-commit-info.md` with:
+- Write `<output_path>/review-fix-commit-info.md` with:
   ```
-  commit-id: none
+  commit_id: none
   ```
 
 **If not in a git repository**:
 - Record issue "Not a git repository — skipped commit" in `review-fix-report.md`.
-- Write `<output-path>/review-fix-commit-info.md` with:
+- Write `<output_path>/review-fix-commit-info.md` with:
   ```
-  commit-id: none
+  commit_id: none
   ```
 
-**If `output-path` was not provided**, skip writing `review-fix-commit-info.md`.
+**If `output_path` was not provided**, skip writing `review-fix-commit-info.md`.
 
 ---
 

package/agents/self-test-fixer.md

@@ -14,10 +14,10 @@ Read a self-test report (`self-test-report.md`), extract all failed scenarios, w
 
 ## Expected Input
 
-- `self-test-report-path`: Path to the self-test report file (`.md`) — **required**
-- `harmonyos-project-path`: Path to the HarmonyOS project root — **required**
-- `android-project-path`: Path to the Android source project — **optional** (enables reference-based fixing)
-- `output-path`: Directory to store `self-test-fix-report.md` — **optional** (defaults to cwd)
+- `self_test_report_path`: Path to the self-test report file (`.md`) — **required**
+- `harmony_project_dir`: Path to the HarmonyOS project root — **required**
+- `android_project_dir`: Path to the Android source project — **optional** (enables reference-based fixing)
+- `output_path`: Directory to store `self-test-fix-report.md` — **optional** (defaults to cwd)
 
 ## Expected Output
 
@@ -28,7 +28,7 @@ Read a self-test report (`self-test-report.md`), extract all failed scenarios, w
 
 ## Step 1 — Read Report and Extract Failed Scenarios
 
-Read the self-test report file at `self-test-report-path`. **Do not assume any fixed format** — understand the report structure by reading it, then extract all scenarios that are marked as failed / not passed / unsuccessful.
+Read the self-test report file at `self_test_report_path`. **Do not assume any fixed format** — understand the report structure by reading it, then extract all scenarios that are marked as failed / not passed / unsuccessful.
 
 For each failed scenario, record whatever information is available:
 
@@ -102,7 +102,7 @@ Before modifying any code, analyze all `confirmed` failures together and create
 
 For each fix item in the plan:
 
-1. **Reference Android implementation** (if `android-project-path` is provided):
+1. **Reference Android implementation** (if `android_project_dir` is provided):
    - Search the Android source for the corresponding feature
    - Understand: entry point, event handling, business logic, persistence, UI feedback
    - Use the Android behavior as the specification for the fix
@@ -126,7 +126,7 @@ For each fix item in the plan:
 
 After **all** fix items are complete, launch the **build-fixer** agent **once** to verify compilation:
 
-- Pass `harmonyos-project-path` and `output-path` to the build-fixer agent
+- Pass `harmony_project_dir` and `output_path` to the build-fixer agent
 - If compilation fails, build-fixer will auto-fix compile errors
 - Compilation issues do NOT count as effective fix attempts
 
@@ -159,25 +159,25 @@ Fixed: {N}/{M} failed scenarios
    cd "<project-dir>" && git rev-parse HEAD
    ```
 
-4. **Write commit info** to `<output-path>/self-test-fix-commit-info.md`:
+4. **Write commit info** to `<output_path>/self-test-fix-commit-info.md`:
    ```
-   commit-id: <commit-id>
+   commit_id: <commit_id>
    ```
 
 **If no files were modified** (all failures were false positives):
-- Write `<output-path>/self-test-fix-commit-info.md` with:
+- Write `<output_path>/self-test-fix-commit-info.md` with:
   ```
-  commit-id: none
+  commit_id: none
   ```
 
 **If not in a git repository**:
 - Record issue "Not a git repository — skipped commit" in `self-test-fix-report.md`.
-- Write `<output-path>/self-test-fix-commit-info.md` with:
+- Write `<output_path>/self-test-fix-commit-info.md` with:
   ```
-  commit-id: none
+  commit_id: none
   ```
 
-**If `output-path` was not provided**, skip writing `self-test-fix-commit-info.md`.
+**If `output_path` was not provided**, skip writing `self-test-fix-commit-info.md`.
 
 ### 3d. Retry Logic (Maximum 2 Effective Attempts)
 
@@ -194,7 +194,7 @@ An "effective attempt" = code was modified AND compilation succeeded, but code r
 
 ## Step 4 — Generate Detailed Fix Report
 
-Write `self-test-fix-report.md` to `output-path`. The report must be comprehensive and actionable.
+Write `self-test-fix-report.md` to `output_path`. The report must be comprehensive and actionable.
 
 ### Report Structure