feat: add ecc2 legacy migration audit

This commit is contained in:
Affaan Mustafa
2026-04-10 10:50:17 -07:00
parent feee17ad02
commit 0f028f38f6
3 changed files with 557 additions and 2 deletions

View File

@@ -183,6 +183,12 @@ It is mostly:
- clarifying public docs
- continuing the ECC 2.0 operator/control-plane buildout
ECC 2.0 now ships a bounded migration audit entrypoint:
- `ecc migrate audit --source ~/.hermes`
Use that first to inventory the legacy workspace and map detected surfaces onto the current ECC2 scheduler, remote dispatch, memory graph, templates, and manual-translation lanes.
## What Still Belongs In Backlog
The remaining large migration themes are already tracked:

View File

@@ -82,6 +82,7 @@ These stay local and should be configured per operator:
## Suggested Bring-Up Order
0. Run `ecc migrate audit --source ~/.hermes` first to inventory the legacy workspace and see which parts already map onto ECC2.
1. Install ECC and verify the baseline harness setup.
2. Install Hermes and point it at ECC-imported skills.
3. Register the MCP servers you actually use every day.