Adopt EvoZeus-CoEvolve harness as a Skillware feasibility target

[HaodiFan]

Context

Engineering Everything is a plugin-first Skillware library with 12 runtime Skill entries and an existing legacy EvoZeus harness. The Collaborative Evolution paper needs one non-project feasibility target with a public, governed, reversible attachment case.

Current gap

• The legacy harness uses the scattered .evozeus/wrapper.json layout at v0.3.0.
• The recommended runtime entry is skills/using-engineering-everything/SKILL.md; there is no root SKILL.md.
• Fresh scripts/install.py --target both currently creates copied runtime directories even though the documented contract describes links.
• The legacy layout lacks two v2 policy files.

Expected result

• Migrate wrapper-owned assets to .evozeus-wrapper/ and EvoZeus-CoEvolve v0.11.2.
• Preserve all Engineering Everything routes, references, scenarios, and direct sub-Skill entrypoints.
• Keep the recommended bootloader as the prompt-enforced preflight surface without claiming native per-Skill invocation.
• Maintain canonical sub-Skill symlinks for Codex and Agents, including a fresh-client installation test.
• Publish v0.13.0 with migration, validation, release, and rollback evidence.

Evidence boundary

Only public repository structure, synthetic local HOME paths, test outcomes, release metadata, and redacted aggregate evidence may enter the paper artifact. No private session or customer content.

Acceptance

• Native Engineering Everything gates pass.
• CoEvolve structure, doctor, version, and release checks pass.
• Fresh Codex + Agents install yields 24 symlinks and 0 copied Skills.
• A release and previous-version recovery rehearsal are publicly auditable.