-
Notifications
You must be signed in to change notification settings - Fork 0
chore: upgrade EvoZeus harness to v0.12.1 #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| # EvoZeus-CoEvolve Harness Refresh:v0.11.4 -> v0.12.1 | ||
|
|
||
| - 日期:2026-07-27 | ||
| - Wrapper 版本:v0.11.4 -> v0.12.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。 |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -17,15 +17,21 @@ 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.11.4` | ||
| - 当前 wrapper 版本:`v0.12.1` | ||
| - 事实源:`.evozeus-wrapper/wrapper.json` | ||
| - 检查命令:在 EvoZeus-CoEvolve repo 运行 `python3 scripts/evozeus_wrapper.py harness upgrade-check --target <this-skill-repo> --json` | ||
| - 如果 wrapper 落后:先运行 `harness upgrade --dry-run` 生成迁移方案,再按状态检查前置、其他 wrapper 内容 append-only 的规则迁移。 | ||
| - 如果 wrapper 落后且 `upgrade-check` 未发现冲突或不兼容:报告当前与最新版本;兼容的旧 wrapper 只作为维护提醒,不阻塞业务主链路。 | ||
| - 普通 Skill 调用不授权 Harness 升级或其他维护写入。只有用户明确请求 Harness 维护或升级后,才运行 `harness upgrade --dry-run` 生成方案;实际写入仍需单独确认。 | ||
| 3. Source contract 状态 | ||
| - 检查命令:`python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py doctor --repo MetaInFLow/metainflow-dev-tasks` | ||
| - 如果 `~/.evozeus/.projects`、git origin 或 runtime install 不一致:先修复为同一个 canonical repo,再继续。 | ||
| 4. 调用身份头 | ||
| - 检查命令:`python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py identity --json` | ||
| - 读取 `runtime_identity.display_line`,并将其原样放在本次 Skill invocation 第一条用户可见输出的第一行。 | ||
| - 身份头固定以 `🧙🏻♂️` 开始;禁止使用 HTML、自定义图片或 shortcode 替代。 | ||
| - 同一次 invocation 的后续 commentary 和 final 不重复;下一次 invocation 再展示一次。 | ||
|
Comment on lines
+28
to
+32
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
These lines introduce a user-visible header on every Skill invocation, but Useful? React with 👍 / 👎. |
||
|
|
||
| 解决顺序:先修 source contract,再修 wrapper harness,最后处理 Skill release;状态已确认或已记录为 runtime-only fallback 后,再进入主链路。 | ||
| 解决顺序:Source contract 损坏、manifest 无效、迁移冲突或已确认不兼容时停止业务流程并说明原因;其他情况完成只读检查后直接进入主链路。 | ||
|
|
||
| # 源子开发任务 | ||
|
|
||
|
|
@@ -238,7 +244,7 @@ description: 通过 lark-cli/LarkSuite CLI 处理「源子技术部管理系统 | |
| Target repo: `MetaInFLow/metainflow-dev-tasks` | ||
| Visibility: `public` | ||
| Current Skill version: `v0.4.0` | ||
| Wrapper harness version: `v0.11.4` | ||
| Wrapper harness version: `v0.12.1` | ||
| ## EvoZeus-wrapper | ||
|
|
||
| 本区由 EvoZeus-wrapper 追加,用来说明本 Skill 的 wrapper harness 路由、版本记录和迁移规则。它不覆盖原 Skill 的业务规则;涉及业务行为变化时,仍必须走 Issue、design doc、PR、CHANGELOG 和 release。 | ||
|
|
@@ -266,7 +272,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.11.4` | ||
| Wrapper harness version: `v0.12.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` | ||
|
|
@@ -299,3 +305,10 @@ Runtime integration modes: | |
| - Layout: `consolidated-v2 -> consolidated-v2` | ||
| - Host hook registration, status prelude, manifest integration, and managed links were refreshed. | ||
| - Target business rules were preserved. | ||
|
|
||
| ## EvoZeus-CoEvolve Version Refresh Note: v0.11.4 -> v0.12.1 | ||
|
|
||
| - Wrapper harness: `v0.11.4 -> v0.12.1` | ||
| - Layout: `consolidated-v2 -> consolidated-v2` | ||
| - Host hook registration, status prelude, manifest integration, and managed links were refreshed. | ||
| - Target business rules were preserved. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a dissatisfied user has not authorized an external write, this new policy requires explicit confirmation, but the active instruction surface in
SKILL.md:235still directs the agent to submit a Skill Feedback Issue first. An agent following that instruction can create the issue before confirmation, bypassing the staged authorization introduced here; update the Skill flow to capture locally and request confirmation before submission.Useful? React with 👍 / 👎.