@buaa_smat/hometrans 0.1.13 → 0.1.15

package/skills/hmos-fix-build-errors/references/known-patterns.md

@@ -1,157 +1,157 @@
-# Known Compile Error Patterns
-
-> **This file is auto-maintained by `a2h-retrospect`.**
-> Manual edits are allowed but may be overwritten when retrospect detects updated patterns.
-> Last updated: 2026-03-27
-
----
-
-## Pattern Index
-
-| # | Error Code / Type | Frequency | Short Description |
-|---|-------------------|-----------|-------------------|
-| 1 | arkts-identifiers-as-prop-names | 85 | ValuesBucket computed property name |
-| 2 | type mismatch (EventData) | 16 | EventData double type cast |
-| 3 | arkts-no-untyped-obj-literals | 9 | Untyped object literal |
-| 4 | type mismatch (promptAction) | 8 | promptAction button color type |
-| 5 | type error (@Prop) | 3 | @Prop naming conflict |
-
----
-
-## 1. ValuesBucket Computed Property Name
-
-- **Date**: 2026-03-27
-- **Error code**: `arkts-identifiers-as-prop-names`
-- **Frequency**: 85 occurrences
-- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
-
-**Error code**:
-```typescript
-const bucket: ValuesBucket = {
-  [ColumnName.TITLE]: title,   // ERROR: computed property name not allowed
-  [ColumnName.URL]: url,
-};
-```
-
-**Correct code**:
-```typescript
-const bucket: ValuesBucket = {};
-bucket[ColumnName.TITLE] = title;
-bucket[ColumnName.URL] = url;
-```
-
-**Rule**: ArkTS forbids computed property names (`[expr]: value`) in object literals. Build the object first, then assign properties via bracket notation.
-
----
-
-## 2. EventData Double Type Cast
-
-- **Date**: 2026-03-27
-- **Error code**: type mismatch
-- **Frequency**: 16 occurrences
-- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
-
-**Error code**:
-```typescript
-emitter.on({ eventId: 1 }, (data: emitter.EventData) => {
-  const value = data.data?.['key'] as string;  // ERROR: data.data is optional Record, direct cast fails
-});
-```
-
-**Correct code**:
-```typescript
-emitter.on({ eventId: 1 }, (data: emitter.EventData) => {
-  const raw = data.data as Record<string, Object>;
-  const value = raw['key'] as string;
-});
-```
-
-**Rule**: `EventData.data` is typed `Record<string, Object> | undefined`. Access requires two steps: (1) cast to `Record<string, Object>`, (2) cast the extracted value to the target type.
-
----
-
-## 3. Untyped Object Literal
-
-- **Date**: 2026-03-27
-- **Error code**: `arkts-no-untyped-obj-literals`
-- **Frequency**: 9 occurrences
-- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
-
-**Error code**:
-```typescript
-const options = {
-  title: 'Hello',
-  message: 'World',
-};  // ERROR: object literal without explicit type annotation
-```
-
-**Correct code**:
-```typescript
-interface DialogOptions {
-  title: string;
-  message: string;
-}
-const options: DialogOptions = {
-  title: 'Hello',
-  message: 'World',
-};
-```
-
-**Rule**: ArkTS requires all object literals to have an explicit type. Define an `interface` or `class` and annotate the variable.
-
----
-
-## 4. promptAction Button Color Type
-
-- **Date**: 2026-03-27
-- **Error code**: type mismatch
-- **Frequency**: 8 occurrences
-- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
-
-**Error code**:
-```typescript
-promptAction.showDialog({
-  buttons: [
-    { text: 'OK', color: '#ff0000' }   // ERROR: color expects ResourceColor, not string
-  ]
-});
-```
-
-**Correct code**:
-```typescript
-promptAction.showDialog({
-  buttons: [
-    { text: 'OK', color: Color.Red }
-  ]
-});
-// Or use $r('app.color.xxx') for resource reference
-```
-
-**Rule**: `promptAction.showDialog` button `color` property expects `ResourceColor` type (Color enum or `$r()` resource reference), not a raw hex string.
-
----
-
-## 5. @Prop Naming Conflict
-
-- **Date**: 2026-03-27
-- **Error code**: type error
-- **Frequency**: 3 occurrences
-- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
-
-**Error code**:
-```typescript
-@Component
-struct MyComponent {
-  @Prop title: string = '';   // ERROR: 'title' conflicts with built-in component property
-}
-```
-
-**Correct code**:
-```typescript
-@Component
-struct MyComponent {
-  @Prop itemTitle: string = '';   // Renamed to avoid conflict
-}
-```
-
-**Rule**: Certain property names (`title`, `content`, `action`, etc.) conflict with built-in component attributes. Prefix with a domain-specific qualifier (e.g., `itemTitle`, `feedTitle`).
+# Known Compile Error Patterns
+
+> **This file is auto-maintained by `a2h-retrospect`.**
+> Manual edits are allowed but may be overwritten when retrospect detects updated patterns.
+> Last updated: 2026-03-27
+
+---
+
+## Pattern Index
+
+| # | Error Code / Type | Frequency | Short Description |
+|---|-------------------|-----------|-------------------|
+| 1 | arkts-identifiers-as-prop-names | 85 | ValuesBucket computed property name |
+| 2 | type mismatch (EventData) | 16 | EventData double type cast |
+| 3 | arkts-no-untyped-obj-literals | 9 | Untyped object literal |
+| 4 | type mismatch (promptAction) | 8 | promptAction button color type |
+| 5 | type error (@Prop) | 3 | @Prop naming conflict |
+
+---
+
+## 1. ValuesBucket Computed Property Name
+
+- **Date**: 2026-03-27
+- **Error code**: `arkts-identifiers-as-prop-names`
+- **Frequency**: 85 occurrences
+- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
+
+**Error code**:
+```typescript
+const bucket: ValuesBucket = {
+  [ColumnName.TITLE]: title,   // ERROR: computed property name not allowed
+  [ColumnName.URL]: url,
+};
+```
+
+**Correct code**:
+```typescript
+const bucket: ValuesBucket = {};
+bucket[ColumnName.TITLE] = title;
+bucket[ColumnName.URL] = url;
+```
+
+**Rule**: ArkTS forbids computed property names (`[expr]: value`) in object literals. Build the object first, then assign properties via bracket notation.
+
+---
+
+## 2. EventData Double Type Cast
+
+- **Date**: 2026-03-27
+- **Error code**: type mismatch
+- **Frequency**: 16 occurrences
+- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
+
+**Error code**:
+```typescript
+emitter.on({ eventId: 1 }, (data: emitter.EventData) => {
+  const value = data.data?.['key'] as string;  // ERROR: data.data is optional Record, direct cast fails
+});
+```
+
+**Correct code**:
+```typescript
+emitter.on({ eventId: 1 }, (data: emitter.EventData) => {
+  const raw = data.data as Record<string, Object>;
+  const value = raw['key'] as string;
+});
+```
+
+**Rule**: `EventData.data` is typed `Record<string, Object> | undefined`. Access requires two steps: (1) cast to `Record<string, Object>`, (2) cast the extracted value to the target type.
+
+---
+
+## 3. Untyped Object Literal
+
+- **Date**: 2026-03-27
+- **Error code**: `arkts-no-untyped-obj-literals`
+- **Frequency**: 9 occurrences
+- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
+
+**Error code**:
+```typescript
+const options = {
+  title: 'Hello',
+  message: 'World',
+};  // ERROR: object literal without explicit type annotation
+```
+
+**Correct code**:
+```typescript
+interface DialogOptions {
+  title: string;
+  message: string;
+}
+const options: DialogOptions = {
+  title: 'Hello',
+  message: 'World',
+};
+```
+
+**Rule**: ArkTS requires all object literals to have an explicit type. Define an `interface` or `class` and annotate the variable.
+
+---
+
+## 4. promptAction Button Color Type
+
+- **Date**: 2026-03-27
+- **Error code**: type mismatch
+- **Frequency**: 8 occurrences
+- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
+
+**Error code**:
+```typescript
+promptAction.showDialog({
+  buttons: [
+    { text: 'OK', color: '#ff0000' }   // ERROR: color expects ResourceColor, not string
+  ]
+});
+```
+
+**Correct code**:
+```typescript
+promptAction.showDialog({
+  buttons: [
+    { text: 'OK', color: Color.Red }
+  ]
+});
+// Or use $r('app.color.xxx') for resource reference
+```
+
+**Rule**: `promptAction.showDialog` button `color` property expects `ResourceColor` type (Color enum or `$r()` resource reference), not a raw hex string.
+
+---
+
+## 5. @Prop Naming Conflict
+
+- **Date**: 2026-03-27
+- **Error code**: type error
+- **Frequency**: 3 occurrences
+- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
+
+**Error code**:
+```typescript
+@Component
+struct MyComponent {
+  @Prop title: string = '';   // ERROR: 'title' conflicts with built-in component property
+}
+```
+
+**Correct code**:
+```typescript
+@Component
+struct MyComponent {
+  @Prop itemTitle: string = '';   // Renamed to avoid conflict
+}
+```
+
+**Rule**: Certain property names (`title`, `content`, `action`, etc.) conflict with built-in component attributes. Prefix with a domain-specific qualifier (e.g., `itemTitle`, `feedTitle`).

package/skills/hmos-fix-build-errors/references/rdb-entity-pattern.md

@@ -1,131 +1,131 @@
-# RDB Entity 确定性修复 Pattern
-# 适用于: ArkTS 严格模式 + @kit.ArkData relationalStore
-# 触发场景: 迁移 Android RDB 实体类到 ArkTS 时
-# 经验来源: EinkBro 迁移 (2026-03-26)
-
----
-
-## Pattern 1: ValuesBucket 正确用法
-
-### 错误写法 (编译报错)
-```typescript
-import { relationalStore, ValuesBucket } from '@kit.ArkData';
-
-toValuesBucket(): ValuesBucket {
-  const bucket = new ValuesBucket();  // ERROR: 'ValuesBucket' only refers to a type
-  bucket.put('key', value);           // ERROR: ValuesBucket has no .put() method
-  return bucket;
-}
-```
-
-### 正确写法
-```typescript
-type EntityValuesBucket = Record<string, number | string | boolean | Uint8Array | null>;
-
-toValuesBucket(): EntityValuesBucket {
-  const bucket: EntityValuesBucket = {};
-  bucket['key'] = value;
-  return bucket;
-}
-```
-
-**原因**: `ValuesBucket` 在 SDK 中是 type alias (`Record<string, ValueType>`)，不是可实例化的类。
-
----
-
-## Pattern 2: fromResultSet 参数类型 (禁止 any)
-
-### 错误写法 (编译报错)
-```typescript
-// ArkTS 严格模式禁止 any
-static fromResultSet(resultSet: any): EntityName {  // ERROR: arkts-no-any-unknown
-```
-
-### 正确写法
-```typescript
-static fromResultSet(resultSet: Object): EntityName {
-  const rs = resultSet as Record<string, Object>;
-  const colIndex = (name: string): number =>
-    (rs['getColumnIndex'] as Function)(name) as number;
-
-  entity.field = (rs['getLong'] as Function)(colIndex('field_name')) as number;
-  entity.name  = (rs['getString'] as Function)(colIndex('name')) as string;
-  return entity;
-}
-```
-
-**替代方案** (更简洁但运行时开销略高):
-```typescript
-// 使用类型断言避免 any，运行时通过 Record<string, Function> 调用
-static fromResultSet(resultSet: Object): EntityName {
-  const getCol = (name: string): number =>
-    (resultSet as Record<string, Function>)['getColumnIndex'](name) as number;
-  const getLong = (name: string): number =>
-    (resultSet as Record<string, Function>)['getLong'](getCol(name)) as number;
-  const getStr = (name: string): string =>
-    (resultSet as Record<string, Function>)['getString'](getCol(name)) as string;
-
-  const entity = new EntityName();
-  entity.id   = getLong('id');
-  entity.name = getStr('name');
-  return entity;
-}
-```
-
----
-
-## Pattern 3: // @ts-ignore 不可用
-
-### 错误尝试
-```typescript
-// @ts-ignore  // ERROR: Switching off type checks with in-place comments is not allowed
-static fromResultSet(resultSet: any): EntityName {
-```
-
-### 必须用 Pattern 2 替代
-
----
-
-## Pattern 4: toValuesBucket() 返回类型注解
-
-```typescript
-type EntityValuesBucket = Record<string, number | string | boolean | Uint8Array | null>;
-
-toValuesBucket(): EntityValuesBucket {
-  const bucket: EntityValuesBucket = {} as EntityValuesBucket;
-  // ...
-  return bucket;
-}
-```
-
----
-
-## 完整 Entity 模板
-
-```typescript
-type EntityValuesBucket = Record<string, number | string | boolean | Uint8Array | null>;
-
-export class MyEntity {
-  id: number = 0;
-  name: string = '';
-  value: number = 0;
-
-  static fromResultSet(resultSet: Object): MyEntity {
-    const rs = resultSet as Record<string, Object>;
-    const col = (n: string): number => (rs['getColumnIndex'] as Function)(n) as number;
-    const entity = new MyEntity();
-    entity.id   = (rs['getLong']   as Function)(col('id'))   as number;
-    entity.name = (rs['getString'] as Function)(col('name')) as string;
-    entity.value = (rs['getLong']  as Function)(col('value')) as number;
-    return entity;
-  }
-
-  toValuesBucket(): EntityValuesBucket {
-    const bucket: EntityValuesBucket = {} as EntityValuesBucket;
-    if (this.id > 0) { bucket['id'] = this.id; }
-    bucket['name'] = this.name;
-    bucket['value'] = this.value;
-    return bucket;
-  }
-}
-```
+# RDB Entity 确定性修复 Pattern
+# 适用于: ArkTS 严格模式 + @kit.ArkData relationalStore
+# 触发场景: 迁移 Android RDB 实体类到 ArkTS 时
+# 经验来源: EinkBro 迁移 (2026-03-26)
+
+---
+
+## Pattern 1: ValuesBucket 正确用法
+
+### 错误写法 (编译报错)
+```typescript
+import { relationalStore, ValuesBucket } from '@kit.ArkData';
+
+toValuesBucket(): ValuesBucket {
+  const bucket = new ValuesBucket();  // ERROR: 'ValuesBucket' only refers to a type
+  bucket.put('key', value);           // ERROR: ValuesBucket has no .put() method
+  return bucket;
+}
+```
+
+### 正确写法
+```typescript
+type EntityValuesBucket = Record<string, number | string | boolean | Uint8Array | null>;
+
+toValuesBucket(): EntityValuesBucket {
+  const bucket: EntityValuesBucket = {};
+  bucket['key'] = value;
+  return bucket;
+}
+```
+
+**原因**: `ValuesBucket` 在 SDK 中是 type alias (`Record<string, ValueType>`)，不是可实例化的类。
+
+---
+
+## Pattern 2: fromResultSet 参数类型 (禁止 any)
+
+### 错误写法 (编译报错)
+```typescript
+// ArkTS 严格模式禁止 any
+static fromResultSet(resultSet: any): EntityName {  // ERROR: arkts-no-any-unknown
+```
+
+### 正确写法
+```typescript
+static fromResultSet(resultSet: Object): EntityName {
+  const rs = resultSet as Record<string, Object>;
+  const colIndex = (name: string): number =>
+    (rs['getColumnIndex'] as Function)(name) as number;
+
+  entity.field = (rs['getLong'] as Function)(colIndex('field_name')) as number;
+  entity.name  = (rs['getString'] as Function)(colIndex('name')) as string;
+  return entity;
+}
+```
+
+**替代方案** (更简洁但运行时开销略高):
+```typescript
+// 使用类型断言避免 any，运行时通过 Record<string, Function> 调用
+static fromResultSet(resultSet: Object): EntityName {
+  const getCol = (name: string): number =>
+    (resultSet as Record<string, Function>)['getColumnIndex'](name) as number;
+  const getLong = (name: string): number =>
+    (resultSet as Record<string, Function>)['getLong'](getCol(name)) as number;
+  const getStr = (name: string): string =>
+    (resultSet as Record<string, Function>)['getString'](getCol(name)) as string;
+
+  const entity = new EntityName();
+  entity.id   = getLong('id');
+  entity.name = getStr('name');
+  return entity;
+}
+```
+
+---
+
+## Pattern 3: // @ts-ignore 不可用
+
+### 错误尝试
+```typescript
+// @ts-ignore  // ERROR: Switching off type checks with in-place comments is not allowed
+static fromResultSet(resultSet: any): EntityName {
+```
+
+### 必须用 Pattern 2 替代
+
+---
+
+## Pattern 4: toValuesBucket() 返回类型注解
+
+```typescript
+type EntityValuesBucket = Record<string, number | string | boolean | Uint8Array | null>;
+
+toValuesBucket(): EntityValuesBucket {
+  const bucket: EntityValuesBucket = {} as EntityValuesBucket;
+  // ...
+  return bucket;
+}
+```
+
+---
+
+## 完整 Entity 模板
+
+```typescript
+type EntityValuesBucket = Record<string, number | string | boolean | Uint8Array | null>;
+
+export class MyEntity {
+  id: number = 0;
+  name: string = '';
+  value: number = 0;
+
+  static fromResultSet(resultSet: Object): MyEntity {
+    const rs = resultSet as Record<string, Object>;
+    const col = (n: string): number => (rs['getColumnIndex'] as Function)(n) as number;
+    const entity = new MyEntity();
+    entity.id   = (rs['getLong']   as Function)(col('id'))   as number;
+    entity.name = (rs['getString'] as Function)(col('name')) as string;
+    entity.value = (rs['getLong']  as Function)(col('value')) as number;
+    return entity;
+  }
+
+  toValuesBucket(): EntityValuesBucket {
+    const bucket: EntityValuesBucket = {} as EntityValuesBucket;
+    if (this.id > 0) { bucket['id'] = this.id; }
+    bucket['name'] = this.name;
+    bucket['value'] = this.value;
+    return bucket;
+  }
+}
+```

package/skills/hmos-incremental-ui-align/{readme.md → README.md}

@@ -36,39 +36,47 @@ HarmonyOS-Android UI 自动对齐流水线。
    ```
 
 3. **智谱 GLM API Key**（phone-agent 调用的模型）
-   到 https://open.bigmodel.cn/ 申请，有免费额度，填到 `config.json` 的 `glm_api_key`。
+   到 https://open.bigmodel.cn/ 申请，有免费额度。设为 OS 环境变量 `GLM_API_KEY`（`ht init` 可帮你写入机器环境变量）。
 
 4. **鸿蒙 SDK 路径**（给改码阶段查 API 用）
-   例如 DevEco Studio 自带的 `E:\DevEco Studio\sdk\default`。
+   取自 OS 环境变量 `OHOS_SDK_PATH` / `HMS_SDK_PATH`（为空时由 `DEVECO_SDK_HOME` 派生），由 `ht init` 写入机器环境变量；例如 DevEco Studio 自带的 `E:\DevEco Studio\sdk\default\openharmony\ets`。
 
 ---
 
-## 配置 `config.json`
+## 入参与配置
 
-首次使用前，自行准备一份 `config.json`（放任何位置都可以），调用 skill 时把它的**绝对路径**作为参数传给 skill。可复制同目录下的 `config-example.json` 作为模板。字段说明：
+本 skill 需要两类信息：
 
-| 字段 | 说明 | 示例 |
-|---|---|---|
-| `android.app_name` | 安卓端 App 显示名（桌面上看到的名字，phone-agent 打开 app 时用） | `"Salt Player"` |
-| `android.package` | 安卓包名 | `"com.salt.music"` |
-| `android.project_dir` | 安卓源码根目录 | `"E:\\SaltPlayerAndroid-main\\SuvineMusicX"` |
-| `harmony.app_name` | 鸿蒙端 App 显示名 | `"Salt Player"` |
-| `harmony.package` | 鸿蒙包名 | `"com.xuncorp.sp2"` |
-| `harmony.project_dir` | 鸿蒙工程根目录（会被直接修改） | `"E:\\SPH"` |
-| `hmos_sdk_dir` | 鸿蒙 SDK 路径 | `"E:\\DevEco Studio\\sdk\\default"` |
-| `glm_api_key` | 智谱 GLM API Key | `"xxx.yyy"` |
-| `capture_output_dir` | 采集产物输出目录（截图/view tree/分析报告都在这） | `"./tmp_saltplayer"` |
+**① 调用时传入的入参**（每次按需提供）：
 
-可以直接参考同目录下的 `config-example.json`。
+| 入参 | 必填 | 说明                                                                 |
+|---|---|--------------------------------------------------------------------|
+| `android_project_dir` | 是 | 安卓源码根目录                                                            |
+| `harmony_project_dir` | 是 | 鸿蒙工程根目录（会被直接修改）                                                    |
+| `capture_output_dir` | 否 | 采集产物输出目录（截图/view tree/分析报告）。默认 `<harmony_project_dir>/.hometrans/capture_output` |
+
+**② 从 OS 环境变量直接读取的全局配置**（由 `ht init` 写入机器环境变量，无需每次传）：
+
+- GLM key ← 环境变量 `GLM_API_KEY`
+- 鸿蒙 SDK ETS API 目录 ← 环境变量 `OHOS_SDK_PATH` / `HMS_SDK_PATH`（为空时由 `DEVECO_SDK_HOME` 派生为 `<DEVECO_SDK_HOME>/default/openharmony/ets`、`.../hms/ets`）
+
+> **Step 0.0** 会在执行前检查这些环境变量是否存在；缺失时会要求用户输入。
+
+> 安卓/鸿蒙两端的 **App 显示名**（`android.app_name` / `harmony.app_name`）和 **包名**（`android.package` / `harmony.package`）也无需提供——skill 的 **Step 0.1** 会按 `android_project_dir` / `harmony_project_dir` 自动解析：
+> - 安卓包名取自 app 模块 `build.gradle(.kts)` 的 `applicationId`（兜底 `AndroidManifest.xml` 的 `package`）；App 名取自启动 Activity / `<application>` 的 `android:label`（`@string/xxx` 会去 `res/values*/strings.xml` 解析，优先中文）。
+> - 鸿蒙包名取自 `AppScope/app.json5` 的 `bundleName`；App 名取自 `app.json5` 的 `label`（`$string:xxx` 会去 `AppScope/resources/**/element/string.json` 解析，优先中文）。
+>
+> 若某项无法从工程目录解析，skill 会回到询问用户。
 
 ---
 
 ## 使用方式
 
-在 Claude Code 里直接调用 skill，**必须把准备好的 `config.json` 的绝对路径附在需求里**：
+在 Claude Code 里直接调用 skill，**把两个工程目录附在需求里**（可作为命名参数，也可在自然语言里说明）：
 
 ```
-/hmos-ui-align config: <绝对路径/config.json>  <自然语言需求，描述要对齐的页面+点击路径>
+/hmos-ui-align android_project_dir: <安卓工程绝对路径> harmony_project_dir: <鸿蒙工程绝对路径>
+<自然语言需求，描述要对齐的页面+点击路径>
 ```
 
 ### 写需求的三个要点
@@ -111,8 +119,8 @@ HarmonyOS-Android UI 自动对齐流水线。
 
 skill 会严格按 `SKILL.md` 里的 5 步流水线跑：
 
-### Step 0 · 加载 config
-读用户指定路径下的 `config.json`，解析出所有路径和 API Key。
+### 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 显示名与包名（无需手动配置）。
 
 ### Step 1 · 双端页面采集
 1.1 解析你的需求，拆成一组「基础页」，每个基础页有 `android_nav_path` 和 `hmos_nav_path`
@@ -161,7 +169,6 @@ skill 会严格按 `SKILL.md` 里的 5 步流水线跑：
 Agents/hmos-ui-align/
 ├── SKILL.md                    # 流水线定义（主 agent 执行逻辑）
 ├── readme.md                   # 本文档
-├── config-example.json         # 配置样例（实际使用的 config.json 由用户自备并显式传路径）
 ├── page_align.md               # Step 3 的转换规则
 ├── diff_analysis.md            # 内部说明
 ├── scripts/