chore: upgrade EvoZeus harness to v0.12.1 - #9
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0783af475d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ], | ||
| "authorization": { | ||
| "capture": "no_external_write", | ||
| "issue_submission": "explicit_confirmation_required", |
There was a problem hiding this comment.
When a dissatisfied user has not authorized an external write, this new policy requires explicit confirmation, but the active instruction surface in SKILL.md:235 still 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 👍 / 👎.
| 4. 调用身份头 | ||
| - 检查命令：`python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py identity --json` | ||
| - 读取 `runtime_identity.display_line`，并将其原样放在本次 Skill invocation 第一条用户可见输出的第一行。 | ||
| - 身份头固定以 `🧙🏻♂️` 开始；禁止使用 HTML、自定义图片或 shortcode 替代。 | ||
| - 同一次 invocation 的后续 commentary 和 final 不重复；下一次 invocation 再展示一次。 |
There was a problem hiding this comment.
These lines introduce a user-visible header on every Skill invocation, but .evozeus-wrapper/CHANGELOG.md still says No unreleased changes. That changelog explicitly requires harness migrations to be recorded when they change Skill behavior, and the PR preflight rejects an empty Unreleased section, so this behavior change cannot pass the repository's release-readiness check or be accurately represented in the next Skill release.
Useful? React with 👍 / 👎.
1 participant
Summary\n- upgrade the managed EvoZeus-CoEvolve Harness to v0.12.1\n- add one runtime identity header per wrapped Skill invocation\n- add development/UAT/stable channel reporting and staged feedback authorization\n- record the reversible Harness migration\n\n## Verification\n- [x] upgrade-all prevalidation passed with no conflicts\n- [x] post-migration structure preflight passed\n- [x] identity --json returned Harness v0.12.1\n- [x] git diff --check passed\n\n## Release\n- https://github.com/MetaInFLow/EvoZeus-CoEvolve/releases/tag/v0.12.1