@harmonyos-arkts/d2h 0.1.11 → 0.1.12

package/skills/d2h-hypium-forge/scripts/validate_scenarios.py

@@ -1,84 +1,84 @@
-#!/usr/bin/env python3
-"""validate_scenarios.py — 场景库质量门禁（下游唯一基础的准入校验）。
-
-校验规则（不通过进 scenarios_blocker.md，禁止进入用例生成）：
-  1. 必备字段：id / name / desc / converted / test_intent
-  2. 可观察业务效果：desc 须含效果关键词（新增/删除/…），纯导航词（进入/打开/跳转XX页）
-     且无效果词 = 拦截
-  3. 入口可定位：page_path 或前置路径字段存在（深层链路须写明）
-  4. converted=false 必须带 reason（未迁移/能力缺失/暂不测试）
-  5. 行为预期依据：source_ref / spec_ref 至少其一（默认值/联动从源码或规格推导）
-
-用法: python3 validate_scenarios.py scenarios.json [--out scenarios_blocker.md]
-退出码：0=全过（或仅警告）；1=存在 blocker。
-"""
-import argparse
-import json
-import re
-import sys
-
-REQUIRED = ['id', 'name', 'desc', 'converted', 'test_intent']
-EFFECT_WORDS = ['新增', '删除', '修改', '保存', '收藏', '取消', '成功', '失败', '提示',
-                '计数', '状态', '切换', '变为', '出现', '消失', '显示', '回显', '+1', '变更为']
-NAV_ONLY = re.compile(r'^(进入|打开|跳转|前往|查看)[^，。]{1,12}(页|面|界面)$')
-INTENTS = ('资源渲染', '功能交互', '配置生效', '导航流转', '状态机', '数据输入')
-
-
-def check(sc):
-    bid = sc.get('id', '?')
-    errs, warns = [], []
-    for f in REQUIRED:
-        if not str(sc.get(f, '')).strip():
-            errs.append(f'缺必备字段 {f}')
-    desc = str(sc.get('desc', ''))
-    if desc:
-        if NAV_ONLY.match(desc.strip()):
-            errs.append('desc 纯导航无可观察效果（"进入XX页"不是业务效果）')
-        elif not any(w in desc for w in EFFECT_WORDS):
-            errs.append(f'desc 无效果关键词（须含 {"/".join(EFFECT_WORDS[:6])}… 之一）')
-    if not (sc.get('page_path') or sc.get('precond_pages') or '前置' in desc or '路径' in desc):
-        warns.append('入口路径未标注（深层链路须在 desc 写前置路径）')
-    if sc.get('converted') is False and not str(sc.get('reason', '')).strip():
-        errs.append('converted=false 必须带 reason（未迁移/能力缺失/暂不测试）')
-    if not (sc.get('source_ref') or sc.get('spec_ref') or sc.get('evidence')):
-        warns.append('行为预期无源码/规格依据标注（默认值/联动禁直觉推断）')
-    ti = str(sc.get('test_intent', ''))
-    if ti and not any(t in ti for t in INTENTS):
-        errs.append(f'test_intent 非法 "{ti}"')
-    return bid, errs, warns
-
-
-def main():
-    ap = argparse.ArgumentParser()
-    ap.add_argument('scenarios')
-    ap.add_argument('--out', default='scenarios_blocker.md')
-    args = ap.parse_args()
-    try:
-        scenes = json.load(open(args.scenarios, encoding='utf-8'))
-    except Exception as e:
-        print(f'✗ scenarios.json 解析失败: {e}')
-        sys.exit(1)
-    if not scenes:
-        print('✗ 场景库为空——空库不允许生成用例（空跑=伪覆盖）')
-        sys.exit(1)
-
-    lines = ['# 场景库 Blocker（未通过质量门禁，禁止进入用例生成）', '']
-    n_err = n_warn = 0
-    for sc in scenes:
-        bid, errs, warns = check(sc)
-        for e in errs:
-            lines.append(f'- **BLOCKER** {bid}: {e}')
-        for w in warns:
-            lines.append(f'- ⚠ {bid}: {w}')
-        n_err += len(errs)
-        n_warn += len(warns)
-    print(f'场景库校验: {len(scenes)} 场景 | {n_err} blocker / {n_warn} 警告')
-    if n_err:
-        open(args.out, 'w', encoding='utf-8').write('\n'.join(lines) + '\n')
-        print(f'→ {args.out}（blocker 场景退回宿主 agent 修复）')
-        sys.exit(1)
-    print('✓ 全部通过（警告项自行斟酌）')
-
-
-if __name__ == '__main__':
-    main()
+#!/usr/bin/env python3
+"""validate_scenarios.py — 场景库质量门禁（下游唯一基础的准入校验）。
+
+校验规则（不通过进 scenarios_blocker.md，禁止进入用例生成）：
+  1. 必备字段：id / name / desc / converted / test_intent
+  2. 可观察业务效果：desc 须含效果关键词（新增/删除/…），纯导航词（进入/打开/跳转XX页）
+     且无效果词 = 拦截
+  3. 入口可定位：page_path 或前置路径字段存在（深层链路须写明）
+  4. converted=false 必须带 reason（未迁移/能力缺失/暂不测试）
+  5. 行为预期依据：source_ref / spec_ref 至少其一（默认值/联动从源码或规格推导）
+
+用法: python3 validate_scenarios.py scenarios.json [--out scenarios_blocker.md]
+退出码：0=全过（或仅警告）；1=存在 blocker。
+"""
+import argparse
+import json
+import re
+import sys
+
+REQUIRED = ['id', 'name', 'desc', 'converted', 'test_intent']
+EFFECT_WORDS = ['新增', '删除', '修改', '保存', '收藏', '取消', '成功', '失败', '提示',
+                '计数', '状态', '切换', '变为', '出现', '消失', '显示', '回显', '+1', '变更为']
+NAV_ONLY = re.compile(r'^(进入|打开|跳转|前往|查看)[^，。]{1,12}(页|面|界面)$')
+INTENTS = ('资源渲染', '功能交互', '配置生效', '导航流转', '状态机', '数据输入')
+
+
+def check(sc):
+    bid = sc.get('id', '?')
+    errs, warns = [], []
+    for f in REQUIRED:
+        if not str(sc.get(f, '')).strip():
+            errs.append(f'缺必备字段 {f}')
+    desc = str(sc.get('desc', ''))
+    if desc:
+        if NAV_ONLY.match(desc.strip()):
+            errs.append('desc 纯导航无可观察效果（"进入XX页"不是业务效果）')
+        elif not any(w in desc for w in EFFECT_WORDS):
+            errs.append(f'desc 无效果关键词（须含 {"/".join(EFFECT_WORDS[:6])}… 之一）')
+    if not (sc.get('page_path') or sc.get('precond_pages') or '前置' in desc or '路径' in desc):
+        warns.append('入口路径未标注（深层链路须在 desc 写前置路径）')
+    if sc.get('converted') is False and not str(sc.get('reason', '')).strip():
+        errs.append('converted=false 必须带 reason（未迁移/能力缺失/暂不测试）')
+    if not (sc.get('source_ref') or sc.get('spec_ref') or sc.get('evidence')):
+        warns.append('行为预期无源码/规格依据标注（默认值/联动禁直觉推断）')
+    ti = str(sc.get('test_intent', ''))
+    if ti and not any(t in ti for t in INTENTS):
+        errs.append(f'test_intent 非法 "{ti}"')
+    return bid, errs, warns
+
+
+def main():
+    ap = argparse.ArgumentParser()
+    ap.add_argument('scenarios')
+    ap.add_argument('--out', default='scenarios_blocker.md')
+    args = ap.parse_args()
+    try:
+        scenes = json.load(open(args.scenarios, encoding='utf-8'))
+    except Exception as e:
+        print(f'✗ scenarios.json 解析失败: {e}')
+        sys.exit(1)
+    if not scenes:
+        print('✗ 场景库为空——空库不允许生成用例（空跑=伪覆盖）')
+        sys.exit(1)
+
+    lines = ['# 场景库 Blocker（未通过质量门禁，禁止进入用例生成）', '']
+    n_err = n_warn = 0
+    for sc in scenes:
+        bid, errs, warns = check(sc)
+        for e in errs:
+            lines.append(f'- **BLOCKER** {bid}: {e}')
+        for w in warns:
+            lines.append(f'- ⚠ {bid}: {w}')
+        n_err += len(errs)
+        n_warn += len(warns)
+    print(f'场景库校验: {len(scenes)} 场景 | {n_err} blocker / {n_warn} 警告')
+    if n_err:
+        open(args.out, 'w', encoding='utf-8').write('\n'.join(lines) + '\n')
+        print(f'→ {args.out}（blocker 场景退回宿主 agent 修复）')
+        sys.exit(1)
+    print('✓ 全部通过（警告项自行斟酌）')
+
+
+if __name__ == '__main__':
+    main()

package/skills/d2h-page-develop/SKILL.md

@@ -1,112 +1,112 @@
----
-name: d2h-page-develop
-description: Implement ordered Android-to-HarmonyOS page tasks from pages.json, batch_report.md, and page-scoped spec.md files. Use during page development when the current agent must complete each page serially through ArkTS implementation, managed build, Python Hypium tests, scoped commits, migration-report evidence, and in-place ledger updates before starting the next page. Do not delegate page work to subagents.
----
-
-# Page development loop
-
-Implement and verify one ordered page task at a time in the current agent. Own each page's complete loop and do not delegate page implementation, build, testing, reporting, commits, or ledger updates to subagents.
-
-## Inputs and boundaries
-
-- Use `.migration/page-specs/pages.json` as the immutable page order and `batch_report.md` as the mutable execution ledger.
-- Use the selected page package's `spec.md` as the authority for page scope, behavior, acceptance sequences, Android evidence, and expected HarmonyOS files.
-- Read `.migration/utg/page.json` when the Spec references a UTG node or the arrival path needs clarification. Read cited Android source before implementing behavior.
-- Do not require or generate `ui-design.md`, copied screenshots, copied `view.xml`, or any other page-package artifact. Each `page_NNNN_<name>-<id>/` directory continues to contain only `spec.md`.
-- Do not regenerate `pages.json`, page Specs, or `batch_report.md` during ordinary development. Correct an owning artifact only when current source proves it wrong, record the reason, and preserve execution history.
-- Use `droid2hmos` managed build and test entry points. Do not use task-planning commands or static scripts to choose or execute page work.
-- Preserve unrelated user changes. Never reset, discard, or include them in a page commit.
-
-## Single-agent mode
-
-1. Read `pages.json` and `batch_report.md`; use AI judgment to verify their task IDs, order, links, counts, and current states agree.
-2. Select the earliest ordered page whose development/build/validation states are not `implemented/passed/passed` and whose declared dependencies are satisfied.
-3. Resolve the page package, Android root, HarmonyOS root, repository root, current `HEAD`, Git status, device target, and task evidence directory.
-4. Record the current `HEAD` and Git status as the task baseline, then execute the selected page through the complete per-page loop below.
-5. Verify the resulting implementation, current managed build/test evidence, migration report, commits, batch ledger, and Git status.
-6. If the page is incomplete or fails verification, repair the same page; do not select another page.
-7. Only after the selected task is genuinely `implemented/passed/passed` may the current agent select the next task.
-8. After all tasks are complete, explicitly enumerate every Python Hypium test list and run one managed batch regression. Append the batch evidence to `batch_report.md` and the migration report.
-
-## Per-page execution
-
-### 1. Claim and understand the page
-
-- Confirm the task is the earliest incomplete eligible row and no other task is `in_progress`.
-- Compare the checkout with the recorded task baseline. Preserve and avoid unrelated dirty files; if ownership conflicts with a build-affecting file, return the exact conflict instead of overwriting it.
-- Mark only the selected task `in_progress` in the working copy of `batch_report.md`.
-- Read the complete `spec.md`, the referenced `.migration/utg/page.json` node, every cited Fact, and every cited Android source file. Follow handlers, state transitions, repositories, navigation, persistence, error paths, and platform side effects far enough to establish the observable result.
-- Inspect the HarmonyOS architecture, routes, resources, shared components, tests, and current implementation. Load `arkts-mvvm-architecture` before planning or writing ArkTS.
-- Build a private checklist mapping every `F-xxx` to reachable code, a stable semantic locator, an executed test assertion, and an observable result. Do not create another planning file.
-- Resume valid existing work for this same task instead of duplicating it.
-
-### 2. Implement
-
-- Implement all page-scoped UI, navigation, overlays, state transitions, persistence/data effects, error paths, resources, and required shared integration.
-- Use the Android source and observable behavior for functional truth. Use HarmonyOS-native architecture and components for the target implementation.
-- Give tested interactive elements stable, unique semantic locators. Do not add controls solely to make testing easier.
-- Load the applicable domain Skill for identity, i18n, drawable conversion, icon sizing, or third-party substitution when the page touches that domain.
-- Keep shared changes limited to capabilities this page actually needs and record downstream consumers.
-- Do not leave stubs, fixed success values, swallowed errors, unreachable pages, placeholder controls, or TODO implementations.
-
-### 3. Managed build
-
-- Run a fresh, non-interactive, bounded build through `droid2hmos build harmony <ANDROID_PROJECT>` using the resolved project configuration.
-- Save the exact command, exit status, timestamps, relevant log, produced HAP path, and HAP SHA-256 in the task evidence directory.
-- Treat compilation errors caused or exposed by the implementation as work to fix. Repeat edit/build until the managed build passes.
-- An older HAP, static analysis result, direct Hvigor run, or previous log is not current build evidence.
-
-### 4. Managed page tests
-
-- Load `d2h-hypium-forge`. Add or update executable Python Hypium tests for every `F-xxx`, with paired `.py` and `.json` test-list assets and stable semantic locators.
-- Cover navigation or overlay lifecycle, state changes, data effects, and error behavior required by the Spec. Assertions must prove the declared result, not merely that a page or button exists.
-- Run the affected lists through the managed entry point:
-
-  ```text
-  droid2hmos test harmony <ANDROID_PROJECT> \
-    --runner python --hypium-project <HARMONY_PROJECT>/.hypium_forge \
-    --test-list <AFFECTED_LIST> --target <DEVICE> \
-    --ref <ACTUALLY_ASSERTED_REF>...
-  ```
-
-- Save the exact command, result, native report/log, device target, timestamps, hashes, and returned `managedEvidence` in the task evidence directory.
-- A written-but-unexecuted test, screenshot-only check, coordinate-only replay, direct local runner, old log, or zero-test result is not a pass.
-- Fix implementation or test defects and repeat managed build/test until both pass. Only a persistent external environment, signing, or device failure may become `blocked`, after bounded retries with diagnostics recorded.
-
-### 5. Report and commit
-
-- Load `maintaining-migration-report` while evidence is fresh. Record real HarmonyOS files, Android source provenance, current managed evidence, differences, and source-proven discoveries; run report validation.
-- Inspect Git status and diff. Stage only the selected page's implementation, resources, tests, necessary shared files, and a source-proven correction to this page's `spec.md` when required. Do not include unrelated changes.
-- Create a scoped implementation commit only after the managed build and page tests pass. Record its commit ID.
-- If build-affecting page changes remain after the commit, correct the commit and rerun build/test so the evidence proves the committed tree.
-- Update the existing `batch_report.md` queue row, detail section, counts, evidence, files, implementation commit, timestamp, blocker, and chronological notes in place. Do not rerun `build_batch_report.py`.
-- Set `implemented/passed/passed` only when all three states are supported by current evidence. Use AI inspection to confirm queue/detail/count consistency and preserve all prior history.
-- Commit the ledger and immutable task evidence separately from the implementation commit. Do not create a self-referential commit field.
-
-## Page completion verification
-
-Before marking the page complete, confirm:
-
-- every `F-xxx` has reachable implementation, a stable locator, and an actually executed assertion;
-- the page is reachable from the real app entry without a test-only route or replacement control;
-- build logs, HAP hash, test reports, managed evidence, and migration-report refs correspond to the implementation commit;
-- `batch_report.md` is internally consistent and the selected row is `implemented/passed/passed`;
-- both scoped commits exist and no uncommitted change owned by the page remains;
-- user changes and other pages were not reset or included;
-- no implementation defect was reclassified as a platform difference or external blocker.
-
-If verification fails, repair the same task before selecting or starting the next task.
-
-## Batch regression
-
-After every page task is complete:
-
-1. Enumerate every current Python Hypium test list explicitly; the Python runner does not use `--all`.
-2. Run one managed command with all required `--test-list` values on the qualified device, using only refs actually asserted by the batch.
-3. Require non-zero execution with no failures, errors, or ignored tests.
-4. Append the managed batch evidence and timestamp to `batch_report.md`, then update and validate the migration report.
-5. A targeted Python batch receipt does not replace the separate ArkTS `--all` receipt required by the Migration Kernel final completion gate.
-
-## Final result
-
-Return each task ID and page, final states, implementation and test files, managed build command/HAP/evidence, managed test command/evidence, implementation and ledger commit IDs, batch regression evidence, unrelated Git changes left untouched, and any genuine blocker or unresolved item.
+---
+name: d2h-page-develop
+description: Implement ordered Android-to-HarmonyOS page tasks from pages.json, batch_report.md, and page-scoped spec.md files. Use during page development when the current agent must complete each page serially through ArkTS implementation, managed build, Python Hypium tests, scoped commits, migration-report evidence, and in-place ledger updates before starting the next page. Do not delegate page work to subagents.
+---
+
+# Page development loop
+
+Implement and verify one ordered page task at a time in the current agent. Own each page's complete loop and do not delegate page implementation, build, testing, reporting, commits, or ledger updates to subagents.
+
+## Inputs and boundaries
+
+- Use `.migration/page-specs/pages.json` as the immutable page order and `batch_report.md` as the mutable execution ledger.
+- Use the selected page package's `spec.md` as the authority for page scope, behavior, acceptance sequences, Android evidence, and expected HarmonyOS files.
+- Read `.migration/utg/page.json` when the Spec references a UTG node or the arrival path needs clarification. Read cited Android source before implementing behavior.
+- Do not require or generate `ui-design.md`, copied screenshots, copied `view.xml`, or any other page-package artifact. Each `page_NNNN_<name>-<id>/` directory continues to contain only `spec.md`.
+- Do not regenerate `pages.json`, page Specs, or `batch_report.md` during ordinary development. Correct an owning artifact only when current source proves it wrong, record the reason, and preserve execution history.
+- Use `droid2hmos` managed build and test entry points. Do not use task-planning commands or static scripts to choose or execute page work.
+- Preserve unrelated user changes. Never reset, discard, or include them in a page commit.
+
+## Single-agent mode
+
+1. Read `pages.json` and `batch_report.md`; use AI judgment to verify their task IDs, order, links, counts, and current states agree.
+2. Select the earliest ordered page whose development/build/validation states are not `implemented/passed/passed` and whose declared dependencies are satisfied.
+3. Resolve the page package, Android root, HarmonyOS root, repository root, current `HEAD`, Git status, device target, and task evidence directory.
+4. Record the current `HEAD` and Git status as the task baseline, then execute the selected page through the complete per-page loop below.
+5. Verify the resulting implementation, current managed build/test evidence, migration report, commits, batch ledger, and Git status.
+6. If the page is incomplete or fails verification, repair the same page; do not select another page.
+7. Only after the selected task is genuinely `implemented/passed/passed` may the current agent select the next task.
+8. After all tasks are complete, explicitly enumerate every Python Hypium test list and run one managed batch regression. Append the batch evidence to `batch_report.md` and the migration report.
+
+## Per-page execution
+
+### 1. Claim and understand the page
+
+- Confirm the task is the earliest incomplete eligible row and no other task is `in_progress`.
+- Compare the checkout with the recorded task baseline. Preserve and avoid unrelated dirty files; if ownership conflicts with a build-affecting file, return the exact conflict instead of overwriting it.
+- Mark only the selected task `in_progress` in the working copy of `batch_report.md`.
+- Read the complete `spec.md`, the referenced `.migration/utg/page.json` node, every cited Fact, and every cited Android source file. Follow handlers, state transitions, repositories, navigation, persistence, error paths, and platform side effects far enough to establish the observable result.
+- Inspect the HarmonyOS architecture, routes, resources, shared components, tests, and current implementation. Load `arkts-mvvm-architecture` before planning or writing ArkTS.
+- Build a private checklist mapping every `F-xxx` to reachable code, a stable semantic locator, an executed test assertion, and an observable result. Do not create another planning file.
+- Resume valid existing work for this same task instead of duplicating it.
+
+### 2. Implement
+
+- Implement all page-scoped UI, navigation, overlays, state transitions, persistence/data effects, error paths, resources, and required shared integration.
+- Use the Android source and observable behavior for functional truth. Use HarmonyOS-native architecture and components for the target implementation.
+- Give tested interactive elements stable, unique semantic locators. Do not add controls solely to make testing easier.
+- Load the applicable domain Skill for identity, i18n, drawable conversion, icon sizing, or third-party substitution when the page touches that domain.
+- Keep shared changes limited to capabilities this page actually needs and record downstream consumers.
+- Do not leave stubs, fixed success values, swallowed errors, unreachable pages, placeholder controls, or TODO implementations.
+
+### 3. Managed build
+
+- Run a fresh, non-interactive, bounded build through `droid2hmos build harmony <ANDROID_PROJECT>` using the resolved project configuration.
+- Save the exact command, exit status, timestamps, relevant log, produced HAP path, and HAP SHA-256 in the task evidence directory.
+- Treat compilation errors caused or exposed by the implementation as work to fix. Repeat edit/build until the managed build passes.
+- An older HAP, static analysis result, direct Hvigor run, or previous log is not current build evidence.
+
+### 4. Managed page tests
+
+- Load `d2h-hypium-forge`. Add or update executable Python Hypium tests for every `F-xxx`, with paired `.py` and `.json` test-list assets and stable semantic locators.
+- Cover navigation or overlay lifecycle, state changes, data effects, and error behavior required by the Spec. Assertions must prove the declared result, not merely that a page or button exists.
+- Run the affected lists through the managed entry point:
+
+  ```text
+  droid2hmos test harmony <ANDROID_PROJECT> \
+    --runner python --hypium-project <HARMONY_PROJECT>/.hypium_forge \
+    --test-list <AFFECTED_LIST> --target <DEVICE> \
+    --ref <ACTUALLY_ASSERTED_REF>...
+  ```
+
+- Save the exact command, result, native report/log, device target, timestamps, hashes, and returned `managedEvidence` in the task evidence directory.
+- A written-but-unexecuted test, screenshot-only check, coordinate-only replay, direct local runner, old log, or zero-test result is not a pass.
+- Fix implementation or test defects and repeat managed build/test until both pass. Only a persistent external environment, signing, or device failure may become `blocked`, after bounded retries with diagnostics recorded.
+
+### 5. Report and commit
+
+- Load `maintaining-migration-report` while evidence is fresh. Record real HarmonyOS files, Android source provenance, current managed evidence, differences, and source-proven discoveries; run report validation.
+- Inspect Git status and diff. Stage only the selected page's implementation, resources, tests, necessary shared files, and a source-proven correction to this page's `spec.md` when required. Do not include unrelated changes.
+- Create a scoped implementation commit only after the managed build and page tests pass. Record its commit ID.
+- If build-affecting page changes remain after the commit, correct the commit and rerun build/test so the evidence proves the committed tree.
+- Update the existing `batch_report.md` queue row, detail section, counts, evidence, files, implementation commit, timestamp, blocker, and chronological notes in place. Do not rerun `build_batch_report.py`.
+- Set `implemented/passed/passed` only when all three states are supported by current evidence. Use AI inspection to confirm queue/detail/count consistency and preserve all prior history.
+- Commit the ledger and immutable task evidence separately from the implementation commit. Do not create a self-referential commit field.
+
+## Page completion verification
+
+Before marking the page complete, confirm:
+
+- every `F-xxx` has reachable implementation, a stable locator, and an actually executed assertion;
+- the page is reachable from the real app entry without a test-only route or replacement control;
+- build logs, HAP hash, test reports, managed evidence, and migration-report refs correspond to the implementation commit;
+- `batch_report.md` is internally consistent and the selected row is `implemented/passed/passed`;
+- both scoped commits exist and no uncommitted change owned by the page remains;
+- user changes and other pages were not reset or included;
+- no implementation defect was reclassified as a platform difference or external blocker.
+
+If verification fails, repair the same task before selecting or starting the next task.
+
+## Batch regression
+
+After every page task is complete:
+
+1. Enumerate every current Python Hypium test list explicitly; the Python runner does not use `--all`.
+2. Run one managed command with all required `--test-list` values on the qualified device, using only refs actually asserted by the batch.
+3. Require non-zero execution with no failures, errors, or ignored tests.
+4. Append the managed batch evidence and timestamp to `batch_report.md`, then update and validate the migration report.
+5. A targeted Python batch receipt does not replace the separate ArkTS `--all` receipt required by the Migration Kernel final completion gate.
+
+## Final result
+
+Return each task ID and page, final states, implementation and test files, managed build command/HAP/evidence, managed test command/evidence, implementation and ledger commit IDs, batch regression evidence, unrelated Git changes left untouched, and any genuine blocker or unresolved item.

package/skills/d2h-page-develop/agents/openai.yaml

@@ -1,7 +1,7 @@
-interface:
-  display_name: "HarmonyOS Page Development Loop"
-  short_description: "按 spec.md 完成单页面受管开发、测试与提交闭环"
-  default_prompt: "Use $d2h-page-develop to serially implement ordered HarmonyOS page tasks from pages.json, batch_report.md, and spec.md in the current agent without delegating page work to subagents."
-
-policy:
-  allow_implicit_invocation: true
+interface:
+  display_name: "HarmonyOS Page Development Loop"
+  short_description: "按 spec.md 完成单页面受管开发、测试与提交闭环"
+  default_prompt: "Use $d2h-page-develop to serially implement ordered HarmonyOS page tasks from pages.json, batch_report.md, and spec.md in the current agent without delegating page work to subagents."
+
+policy:
+  allow_implicit_invocation: true