chore: upgrade EvoZeus harness to v0.10.1

.evozeus-wrapper/CHANGELOG.md

@@ -9,6 +9,7 @@ Wrapper harness migrations are recorded under `.evozeus-wrapper/docs/migrations/
 ### Skill changes
 
 - Upgraded the embedded EvoZeus-wrapper harness from v0.9.1 to v0.10.0.
+- Applied the v0.10.1 patch that preserves target-owned Markdown boundaries during harness refresh.
 - Clarified that the project hook covers canonical-repository maintenance while Skill-entry preflight remains prompt-enforced.
 
 ### Feedback / Issues
@@ -21,6 +22,8 @@ Wrapper harness migrations are recorded under `.evozeus-wrapper/docs/migrations/
 - `python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py structure`
 - `python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py doctor --repo MetaInFLow/metainflow-dev-tasks`
 - Skill format validation and repository hook adapter smoke test.
+- Confirmed the v0.10.1 refresh changed only wrapper-owned version references and appended the correct version-refresh note in `SKILL.md`.
+
 
 
 ## [v0.1.0] - 2026-07-20

.evozeus-wrapper/docs/designs/2026-07-20-upgrade-wrapper-v0.10.1.md

@@ -0,0 +1,36 @@
+# Upgrade EvoZeus-wrapper Harness to v0.10.1
+
+## Related Issue
+
+MetaInFLow/EvoZeus-wrapper#14 reported that the v0.10.0 migration refresh could remove a target-owned H1 and record an incorrect layout transition. EvoZeus-wrapper v0.10.1 is the patch release for that issue.
+
+## Optimization Goal
+
+Apply v0.10.1 to the target harness and prove that wrapper status refreshes preserve the complete development-task management instruction surface.
+
+## Direction
+
+- Treat the change as a consolidated-v2 version refresh, not a layout migration.
+- Preserve the target H1, metadata, business sections, whitespace, and existing migration notes.
+- Refresh only wrapper-owned assets and version references.
+- Keep Skill release v0.1.0 independent from wrapper harness v0.10.1.
+
+## Implementation Plan
+
+1. Resolve v0.10.1 from the authoritative GitHub release.
+2. Run a conflict-free `migrate-layout` dry-run against the clean canonical repository.
+3. Apply the patch migration and create its wrapper migration record.
+4. Inspect the `SKILL.md` diff to verify that target-owned content remains unchanged.
+5. Refresh the global dispatcher separately while leaving trust state explicit.
+
+## Verification Plan
+
+- Run wrapper structure, source-contract, and latest-version checks.
+- Validate the Skill format.
+- Execute the repository hook adapter with synthetic `SessionStart` input.
+- Run the target PR preflight and GitHub pull-request gate.
+- Confirm the final canonical worktree is clean.
+
+## Release Plan
+
+Merge the harness-only PR after its gate passes. Do not create a new Skill release because no task-management behavior changes; wrapper v0.10.1 remains the independently versioned infrastructure release. Roll back by reverting the migration commit.

.evozeus-wrapper/docs/migrations/2026-07-20-v0.10.0-to-v0.10.1.md

@@ -0,0 +1,26 @@
+# EvoZeus-wrapper Harness Refresh：v0.10.0 -> v0.10.1
+
+- 日期：2026-07-20
+- Wrapper 版本：v0.10.0 -> v0.10.1
+- 新事实源：`.evozeus-wrapper/wrapper.json`
+- 目标：修复 consolidated-v2 harness 并刷新 wrapper-managed contract。
+
+## 移动记录
+
+- 无文件移动；刷新 consolidated-v2 managed files。
+
+## 保留的宿主接点
+
+- `.codex/hooks.json`
+- `.github/ISSUE_TEMPLATE/`
+- `.github/pull_request_template.md`
+- `.github/workflows/evozeus-wrapper-preflight.yml`
+
+## 验证
+
+- `python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py structure`
+- `python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py runtime`
+
+## 回滚
+
+- 回滚包含本次迁移的 Git commit。

.evozeus-wrapper/wrapper.json

@@ -1,6 +1,6 @@
 {
   "wrapper_repo": "MetaInFLow/EvoZeus-wrapper",
-  "wrapper_version": "v0.10.0",
+  "wrapper_version": "v0.10.1",
   "applied_at": "2026-07-20",
   "layout_version": 2,
   "target_wrapper_dir": ".evozeus-wrapper",

SKILL.md

@@ -17,7 +17,7 @@ description: 通过 lark-cli/LarkSuite CLI 处理「源子技术部管理系统
    - 如果 GitHub latest release 更新：先更新 canonical repo，并确认 runtime install 仍指向 canonical repo。
    - 如果本地版本领先 GitHub release：先完成 changelog、验证和 `vMAJOR.MINOR.PATCH` release，再把它当作稳定运行版本。
 2. Wrapper harness 状态
-   - 当前 wrapper 版本：`v0.10.0`
+   - 当前 wrapper 版本：`v0.10.1`
    - 事实源：`.evozeus-wrapper/wrapper.json`
    - 检查命令：在 EvoZeus-wrapper repo 运行 `python3 scripts/evozeus_wrapper.py harness upgrade-check --target <this-skill-repo> --json`
    - 如果 wrapper 落后：先运行 `harness upgrade --dry-run` 生成迁移方案，再按状态检查前置、其他 wrapper 内容 append-only 的规则迁移。
@@ -196,7 +196,7 @@ description: 通过 lark-cli/LarkSuite CLI 处理「源子技术部管理系统
 Target repo: `MetaInFLow/metainflow-dev-tasks`
 Visibility: `public`
 Current Skill version: `v0.1.0`
-Wrapper harness version: `v0.10.0`
+Wrapper harness version: `v0.10.1`
 ## EvoZeus-wrapper
 
 本区由 EvoZeus-wrapper 追加，用来说明本 Skill 的 wrapper harness 路由、版本记录和迁移规则。它不覆盖原 Skill 的业务规则；涉及业务行为变化时，仍必须走 Issue、design doc、PR、CHANGELOG 和 release。
@@ -224,7 +224,7 @@ Append-only 迁移规则：
 - 每次 wrapper 升级必须记录 from/to wrapper version、planned files、验证命令、回滚方案和是否需要人工 merge review。
 - wrapper version 事实源是 `.evozeus-wrapper/wrapper.json` 的 `wrapper_version`；Skill release 仍以 GitHub release / `.evozeus-wrapper/CHANGELOG.md` 为准。
 
-Wrapper harness version: `v0.10.0`
+Wrapper harness version: `v0.10.1`
 Wrapper manifest: `.evozeus-wrapper/wrapper.json`
 Feedback audit policy: `.evozeus-wrapper/policies/feedback-policy.json`
 Feedback audit rule: `.evozeus-wrapper/policies/audit-rule.md`
@@ -243,3 +243,10 @@ Runtime integration modes:
 - Layout: `consolidated-v2 -> consolidated-v2` (version refresh only)
 - Host hook registration, status prelude, manifest integration, and managed links were refreshed.
 - Target business rules were preserved.
+
+## EvoZeus-wrapper Version Refresh Note: v0.10.0 -> v0.10.1
+
+- Wrapper harness: `v0.10.0 -> v0.10.1`
+- Layout: `consolidated-v2 -> consolidated-v2`
+- Host hook registration, status prelude, manifest integration, and managed links were refreshed.
+- Target business rules were preserved.