chore: upgrade EvoZeus harness to v0.10.0

[HaodiFan]

Summary

• upgrade the embedded EvoZeus-wrapper harness from v0.9.1 to v0.10.0
• classify the project hook as a canonical-repository maintenance hook and the Skill entry check as prompt-enforced fallback
• refresh the target preflight, onboarding, hook adapter, manifest, and migration record
• preserve the target Skill's business rules and heading structure

Verification

• python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py structure
• python3 .evozeus-wrapper/scripts/evozeus_wrapper_preflight.py doctor --repo MetaInFLow/metainflow-dev-tasks
• python3 /Users/anthonyf/.codex/skills/.system/skill-creator/scripts/quick_validate.py .
• repository hook adapter smoke test returned continue: true and wrapper current
• git diff --check

Migration Note

The v0.10.0 migrator initially removed the target H1 and emitted an incorrect layout label. This target PR restores the H1 and records the actual consolidated-v2 version refresh. The reusable wrapper regression is tracked in MetaInFLow/EvoZeus-CoEvolve#14; broad upgrade-all was not applied.

Design doc: .evozeus-wrapper/docs/designs/2026-07-20-upgrade-wrapper-v0.10.0.md

Changelog updated: .evozeus-wrapper/CHANGELOG.md

Data Boundary

No private configuration, customer data, chats, Feishu records, internal document links, or credentials are included.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 78055abf42

ℹ️ 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".

[chatgpt-codex-connector]

Reject cache timestamps that are in the future

When the system clock moves backward or the shared dispatcher cache contains a future checked_at_epoch, max(0, now_epoch - cached_at) treats the entry as zero seconds old. A sufficiently future timestamp can therefore keep a stale wrapper version valid far beyond the one-hour TTL, preventing this startup check from discovering newer releases. Require the computed age to be nonnegative as well as within the TTL.

Useful? React with 👍 / 👎.